EssArrBee

Looks like we may need to look over the new smelter: Version 1.71-SMIM'd the Smelter finally. Real 3D stonework, smoother dome, better textures, new inside charcoal model, grate on top to match the collision, and other stuff. Six new textures require 36MB VRAM, but it's worth it. -Dwemer animated observatory meshes edited to fix bad UV mapping on the green chiseled circles (dweobservatorychamber01.nif, dweobservatoryarmillary01.nif, dweobservatorydome01.nif, dweobservatorydome02.nif, dweobservatorydome03.nif). -Dwemer focus mesh (focusingcrystal01.nif) improved to fix bad UV mapping on the green chiseled circles and to add a much better rock texture since the original reused the iron ore texture in a very sloppy way. Bad devs! -Dwemer armillary (dweobservatoryarmillary01.nif) updated to use new focus mesh as well.36MB of VRAM? That better be one pretty smelter.

Didn't know that was the case for that mod. Didn't read the installer, but the Robert's plugin is merged to bashed patch and doesn't get used during load either way. The FCO Roberts plugin is also merged and is later in the load order so it would overwrite anything that bashed patch merges from the roberts plugin.

Sorry phone did something weird and I can't edit posts with Tapatalk. Might be an issue we need to look into.

Hhouup

Then you still have worry about the meshes.

I like fine detail from far away but that doesn't mean I like it to be jagged. There is a disconnect between the size of features on the textures and the size they up as in game. Limestone smooth, sandstone smooth, granite choppy, dyorite choppy. Geology learned.

I think mine is write able because I do some much with tes5edit, ck and enb.

The FOMOD posted above worked for me. I just installed it with internal installer of MO 1.2.2.

I have mine as write able so MO's virtual filing system can do whatever it needs.

Is it the only mod that is doing this? There are other texture mods and if they aren't working then it is the program that is having a problem we haven't identified yet. Otherwise it's something to do with the mods and the privileges. Make sure the INIs and game directory aren't read only.

Have you checked the privileges? Is it run as an admin. I had some problems with files changing their privileges for no reason other than, it's Windows.

Untick and tick the archive invalidation check box again, make sure the mod checkbox is ticked too. I forget to tick them sometimes when messing around with stuff and then I wonder why there is nothing in the Conflicts tab.

Beth does have good 2D artists, but their meshes can be hit or miss. When the meshes are correct, the vanilla texture look very good. I'm bias toward the textures with bigger features, so they look smoother in game. That is what I would expect from that type of wet region like Skyrim. Also, I tend to like them on the lighter side of the grey scale. It reminds me more of Limestone. I am very picky about my mountains though since I've lived in the mountains most my life.

What do your roads look like? If they look like the one on the left than make sure the Archive Invalidation box is ticked in the profile editor. The ones on the right are 2k poco bueno. You can go up to 4k with the UHQ version if you want. I believe that the HQ version of Ojo Bueno is 2k, so yes they are the same. Don't know why it done that way, but there you go.

I just looked at the Poco Bueno textures and they are 2k for the main road textures and 1k for the details. The UHQ are the only ones that are going to be higher resolution than those.

Look at the file tree in your mod's info pop up. Also, make sure that nothing is overwriting the mod in the conflicts tab in the info pop up. It seems like you may have something overwriting that you are unaware of or the mod didn't install correctly. If the file tree is messed up then you may just have to change the .fomod to .zip and install it manually.

I have 4 files in mine, so you may have a corrupt download.

How are you installing the FOMODs with Ojo Bueno? I noticed that there are 4 FOMODs in one package. Did you extract the FOMODs first? Maybe also try to install one of the FOMODs with FOMM and untick all your other mods in the left pane first though. Then just tick them again after moving everything from the overwrite folder into a mod folder. You can right select all or disable all.

Yes.

I'm not having DY's problem, but I did load up Fallout New Vegas and it seemed to work well for that game too. I have a bunch of mods that I have to install right to the DATA folder because I couldn't get the GECK to launch with MO and it detected all those mods and put them into folders at the top of mod list. The one weird thing was that there was also a folder called FalloutNV, so it may be detecting some of the game files as DLC or something.

Good chance it's the fomod installer. MO v1.2.1 has some issues, so you can use the NCC downgrade in the optional files on the MO page.

Make sure you uninstall Audio Overhaul for Skyrim - Patches. His patches say AOS-<other mod> Patch.esp and the new ones are AOS2-<other mod> Patch.esp. I looked at mine and they all seem good, the impact data set seemed alright. I'll have to reinstall to double check though, since I every time I hear something like this it drives me crazy me until I double or triple check.

Okay, so a few things before I get to BSAs. The little drop down on next to profiles bar is cool.The fix mod order function is nice, but didn't work 100%. Still had to move a couple things manually.All my mods were reset and unchecked after install.MO starts up faster and Skyrim loads up faster than 1.2.0 or 1.2.1.The lightbulb Flag is much easier to read than before.So the BSA handling: When I started MO Hearthfire was detected and put at priority 0, but Dragonborn and Dawnguard were at the bottom of my install list.When I moved Dawnguard to the top, I couldn't put USKP or my Optimized textures before Dawnguard using drag and drop. All three files just had priority 0, so I had to manually type in the priority, but after that everything was fine.I guess if we have the check box on the archive tab ticked that all BSAs are greyed out unless they are loaded with a dummy plugin. That seems like a good idea to me, tie loading to install order not plugin order.The bug where BSAs would retick themselves after swithcing tabs is gone.

I'll cehck it out right now. Is it only an update to the BSA handling or is there anything else we should look at?

Flashlight NVSE has been the mod that required mod focus than any other single mod and I have gone back and forth about emoving it and just waiting till the NCC installer is better. For some reason it is just such a pain in the butt. And, if you use it with ENB, it can really decrease performance for some reason. The way I laid it out in the guide is the way that gave me the best results, also, those install order and the directions I listed are extremely important because of the FOMM and MO file overwrites. FOMM will actually overwrite files that you have installed with MO even though MO itself was made so things like that can't happen. It is just a weird thing we have to deal with until Tannin finishes making the NNC installer 100% compatible. I recommend v1.1.1 in the guide or v1.1.2 with the NCC downgrade because that is the only way I tested it to work. I took a long break from F&L for real life and my other STEP duties, but now that I'm back I'll keep testing beta version of MO to get the guide up to date. That is going to take some serious effort on my part and will probably not happen for a couple weeks. Plus, a new version of MO is around the corner, so I might weight till Tannin is done with new BSA management system.