EssArrBee

I think that the default alpha 3 is the best of the above screens. The vanilla is just too bright and the other two are a little bit too dark. I kinda like the cold look that the default image has. Everyone always goes to the yellow/orange side of lighting, but the bluer look is better for a wintery fantasy world.

The latest Nvidia driver came with a broken Nvidia Experience app. For some reason it can't start SKSE and a D3D plugin like ENB or SweetFX. You can try deleting the Nvidia app or installing an older version.

IMPACT is finally out. Going to try the Micheal Bay edition and see just how much stuttering there is with all those shells and decals.

Tick all BSAs under the archive tab and see if that works.

Beth forums. I've been testing it for a couple weeks.

Disable Import Sound and see if that is it. Also, start with the debug.bat, you can add it as the executable in MO.

It should work for everything except morrowind. You need to install Wrye flash then overwrite with the new one I believe.

Yeah, I know I should be testing it. I started by testing the Skyrim version, but never made it to the FNV version because the current version was working so well and real life just keeps shitting on my free time.

Also, I finally got some time to test the crossbows. I like having them in the game, they add a cool weapon and it's pretty believable that bow technology would be around since arrows are easy to construct. My only gripe is that the special bolts didn't have any description of what they do in the pip boy. I may have to make a patch for that.

Anyone who may be updating MO to version 1.2.13, please be aware that Non-MO mods now have 'Unmanaged:' listed with the mod in the left pane. This means that the first time you start MO it will put all those mods in the top spaces for priority. THey may be out of order, so you will need to doulbe check. Also, if you have optimized vanilla textures then you will need to resort them manually for the correct overwrite priority. This is only a minor annoyance, but one that users should be aware of. MO v1.2.13 seems to work with the latest version of LOOT, v.7 alpha 4. THat is good news for those of us that are using it right now. The UI changes coming to LOOT are going to make it much more user friendly and easy to manage custom load order operations. I still don't recommend the alpha for general users, but beta should be on it's way and will probably be good enough for everyone to try. Just keep an eye out of the beth forums.

Reinstall DarnUI using my directions. Remove ENBoost and see if the screen blur is still there. Enboost is for memory crashes mostly. It will lower performance.

Those mods just look like texture/mesh replacers, so they wouldn't mess anything up. Usually ESPs are what to avoid since textures/meshes only affect performance and not stability. I've never even thought about the Pip boy screen being distorted. I just always chalked it up to what a 50s aesthetic screen would look like. I'm not sure why I didn't have those ITMs in the guide. I'll have to look at it later. I just don't have any time lately. Just when I think time is clearing up, something else pops up. I think everyone I know has gotten sick or injured this year. "No, I won't drive you to the doctor grandma, that's what the bus for."

A bug I have is LOOT v.7 alpha not working with MO v1.2.12. I'll post it to the bug tracker later on when I'm at my computer, but it's something to look into when you can.

Well, the bashed patch is getting big update right now and soon Cells, Graphics, and Sound records will all be included. Just tell everyone to use Wrye Bash and forget about compatibility.

It might be there because someone added it to the masterlist recently. I'll have to remove it from the guide.

The glowing ghouls and bad performance are from FCO -glowing ghouls. Drumber has been working on that but hasn't figured it out yet. You could disable the glowing ghouls plugin and see if that helps.

You want two mods in the left pane. The main Fallout Character Overhaul and then the FCO NVR3 assets. Install the FCO NVR3 assets in a separate mod because they may need to be uninstalled when NVR3 updates. If you install them in the main FCO mod then you'd have to reinstall FCO.

I don't mind what you call me. I'm not picky about usernames since they are just made up anyways.

Tannin actually has to take a break to update something with his servers. Use the new version if you have the Nexus bug, otherwise it doesn't matter.

I don't have any issues with MO and Nexus, but the latest LOOT alpha does not work with MO v1.2.12. That probably doesn't matter to regular users, but I try to help test LOOT as much as possible.

If you only use FCO, then install everything I list in the guide without the NVR3 file. Then skip the FNVEdit instructions.

I changed the FCO instructions last night, so the FNVEdit procedure should be correct. It should be usable with the playable races now, but if not someone will let me know. I won't be able to actually test it until late tonight. I don't trust Zan's. I've worked really hard on making the guide as stable as any heavily modded setup that Fallout New Vegas has ever seen. Using NVAC, NVSR, and ENBoost reduces crashes more than anything. If you still have lots of crashes then try Zan's, but try out the setup I made in the guide first, then drop ENBoost, and if that doesn't work try Zan's.

I don't always add in the new version of every mod. I'll add an explicit note if you should not use the new version. I'll bump up the Willow version today though.

Welcome Falion, the more members I get to come over from the Nexus, the better. DOn't forget to check out our Fallout 3 guide linked at the top of F&L.

Hmm... well, cancel that IHWT/WMX thing, I found an error in the method. The batch file needs the DATA folder.