Strange problem with MO and FNV 4GB Updated

[Audley]

I had this really strange problem occure while using MO and FNV 4GB. When I launche FNV 4GB unmodded, default .ini's no Nvidia CP tweaks, no ENB's, I get this weird texture shimmer on some objects. Like it's affecting the AA or Transparency Multisampling for some reason. I tried messing with every setting I could in the Nvididia CP and .ini files. However, if I launch FNV 4GB outside of MO its fine. If I launch FOSE or just the regular fallout NV .exe in MO it's fine. I can't for the life of me figure out what is wrong. I am going to take a picture and then I will update this post.

 

Edit: I tried to take a picture but it really only happens when your character moves. It only appears on a couple objects like fences and trailers. Its really annyoing and any help would be appriciated. Thanks.

 

Edit: I found a fix! After about an hour of troubleshooting I found one. What you need to do is change -laaexe .FalloutMO.exe to -laaexe FalloutNV4GB. I just removed the . and the .exe so you could keep it FalloutMO. It still starts up with MO and works just fine. If you are having this problem.

 

It seems to make some random file. I have no way of telling if this still has it so it is using 4GB. If someone could help me confirm or deny this that would be great.

 

Edit: I did some more testing and it seems on my end that the .FalloutMO.exe (or any) that FNV4gb creates can cause some texture glitches when launched through MO. I changed it to -laaexe FalloutNV4GB.dll and then looked at with Task Manager and CFF explorer. The >2 flag was set so I am somewhat positive that it is working properly.

Edited August 30, 2014 by Audley

[EssArrBee]

4GB Loader already that has those directions. Devil is in the details. https://wiki.step-project.com/User:EssArrBee/FalloutNewVegas#4GB_Fallout_New_Vegas_Updated

 

You are probably seeing something from the AA you are using, try going to regular old MSAA and see if it persists.

[Audley]

I thought this too. However, I am only using the in game AA and not forcing anything with the Nvidia control panel. The 4GB loader has the directions of using Fallout4GB.exe but the .exe is the problem. Changing the command line to Fallout4GB or in this case FalloutMO.dll will solve this problem for me while not making a lot of since as to why. 

 

If I run NVSE through MO I don't have this problem at all. Or, if I run Fallout4GB through the regular .exe and not through MO it is fine. 

 

Of course it has to be a problem with AA right? 

 

If I disable AA I have the same problem, I even double checked in the Control Panel to make sure I was not running any kind of AA or AF on any of the fallout .exe's.

[EssArrBee]

Okay, turn AA off everywhere. ENB, Fallout INIs, and Nvidia/AMD driver AA. Turn the game on with MO. Then turn on one AA at time seeing which doesn't give you flickering. Do not use the Launcher. Turn the Fallout AA on off in the INIs through MO, using the INI Editor.

[Audley]

Alright I did what you said and found out is indeed the games implemented AA. I tried forcing AA through the control panel but the game looks horrible. Either that or I am doing it wrong.

[EssArrBee]

Control Panel? Do you mean Nvidia Inspector or Catalyst Control Center?

[Audley]

Nvidia Control Panel. I don't use Inspector or really know what that is. I have a GTX 760. 

[EssArrBee]

Okay Nvidia Inspector is allows you to access the profiles for each application that Nvidia provides. Control Panel is kind of clunky, while Inspector is quite lightweight. It is portable and you can pretty much delete it at any time without issue. https://wiki.step-project.com/Guide:NVIDIA_Inspector

[Audley]

Oh My Gosh I fixed it! Thanks so much EssArrBee! What I did was loaded up FalloutMO.exe in Inspector and changed the AA compatibility mode to New Vegas. 

[EssArrBee]

Usually you can just go to the profile view and go to the Fallout New Vegas profile. There is a couple dropdowns for different AA types. They list like 20 or so different AA methods you can force through drivers. SGSSAA will be the best, but will cripple your framerate, especially in Freeside/Strip. You can play around with the different methods and see what works the best.