ModOrganizer v1.3.4 4Gb.exe -laaexe .\FalloutnvMO.exe

[GSDFan]

It looks like the 4gb executable now works properly in MO 1.3.4 now and the -laaexe .\FalloutnvMO.exe argument is no longer needed. The execuatble now shows up in the exes folder and all of the messages no longer there.

[Matriga]

While the argument isn't needed anymore, it won't find the enb .ini files. My pallettes are working properly, however I am not getting effects such as DOF and SSAO. 

[raw3868]

I had to add an additional argument, -extradll d3d9.dll, to get ENB to load at all. This was with MO 1.3.6...

[GSDFan]

I have pinned this topic to be the central discussion thread for the 4GB launcher.

[Rileymac4]

I have a completely vanilla Fallout NV except for having installed NVSE and the 4GB version. However, using MO v1.3.8 (with or without all BSA's checked), the 4GB launcher won't start the game, even with "-laaexe .\FalloutnvMO.exe" or "-laaexe .\FalloutMO.exe" in the arguments. Does anyone know what I should do to fix this? Thanks!

[Matriga]

I have a completely vanilla Fallout NV except for having installed NVSE and the 4GB version. However, using MO v1.3.8 (with or without all BSA's checked), the 4GB launcher won't start the game, even with "-laaexe .\FalloutnvMO.exe" or "-laaexe .\FalloutMO.exe" in the arguments. Does anyone know what I should do to fix this? Thanks!

As stated above, those arguments are no longer needed. I can verify this. I am using MO v1.3.8, DO NOT have the arguments in place, and I launch every time with no issues.

[Rileymac4]

As stated above, those arguments are no longer needed. I can verify this. I am using MO v1.3.8, DO NOT have the arguments in place, and I launch every time with no issues.

I know, that's what I thought was supposed to happen, but even when I don't have the arguments in place, which is what I originally did, and have tried since, it still says that Fallout has stopped working. :(

[GrantSP]

If you are still having issues we will need to see the logs from the attempts to start and your INIs for the settings you have in place.

[Matriga]

Also exact details of what's happening when you try to start it would be awesome, too. 

[Rileymac4]

If you are still having issues we will need to see the logs from the attempts to start and your INIs for the settings you have in place.

 

 

Also exact details of what's happening when you try to start it would be awesome, too. 

The game is an entirely brand new install from Steam with the exception of NVSE and the 4GB as I mentioned earlier. Everything launches properly until I try to do so through MO. When I launch 4GB through MO I get a really quick little bar saying loading game, then a window starts to pop up in the top left corner, but then I get Windows saying "Fallout NV has stopped working." Looking at my MO logs:

 

INFO (14:36:09.0344): Windows Exception (c0000005). Origin: "C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas\FalloutMO.exe" (a087e5). Last hooked call: unsigned long __stdcall GetFileAttributesW_rep(const wchar_t *)

DEBUG (14:36:26.0863): hooks removed

That seems to be the problem. My fallout.ini is still vanilla. If I go into the FNV folder and try to launch the "FalloutMO.exe" I get  Application load error 3:0000065432.

Edited August 24, 2015 by Rileymac4

[GSDFan]

 

That seems to be the problem. My fallout.ini is still vanilla. If I go into the FNV folder and try to launch the "FalloutMO.exe" I get  Application load error 3:0000065432.

That is because that file is the modified file and Steam will throw that error because it is not the original.

 

Someone else used this argument and it worked for them, "-laaexe \FalloutnvMO.exe" Notice that the dot is gone and don't use the quotation marks.

[Rileymac4]

That is because that file is the modified file and Steam will throw that error because it is not the original.

 

Someone else used this argument and it worked for them, "-laaexe \FalloutnvMO.exe" Notice that the dot is gone and don't use the quotation marks.

I just tried that and the same thing happened as well. =/ I'm quite perplexed by this and I'm debating downgrading to an older version of MO where people have confirmed they're able to launch the 4GB. 

[Matriga]

My guide is written off of 1.3.8. It works fine. Either there's a problem with your .ini files, or something else is awrye.

My personal guess is that the 4gb Launcher hasn't been installed properly, that your .exe files are in the wrong location, or that you're trying to launch from the one in the folder not with MO. 

I'm fairly certain this is an execution problem, and not a problem with 4gb Launcher, Mod Organizer, or NVSE (all are required for this to work properly). 

Edited August 25, 2015 by Matriga

[Matriga]

 

If my directions don't help solve your problem, Idk what to tell you. It works fine with 1.3.8, though.

 

Though I did just notice that 4GB Launcher is before NVSE in my guide, and I have people check to make sure NVSE is working in the 4gb Launcher portion. I think perhaps I should change that.... lmfao

Edited August 25, 2015 by Matriga

[Rileymac4]

My guide is written off of 1.3.8. It works fine. Either there's a problem with your .ini files, or something else is awrye.

 

My personal guess is that the 4gb Launcher hasn't been installed properly, that your .exe files are in the wrong location, or that you're trying to launch from the one in the folder not with MO. 

 

I'm fairly certain this is an execution problem, and not a problem with 4gb Launcher, Mod Organizer, or NVSE (all are required for this to work properly). 

4GB launcher is fine, also shows the proper version of NVSE when I check it from the 4GB launcher when not launched through MO. And yes, of course my .exe files are with the rest of them. -.- And if I was launching from the one in the folder, then I would be thinking it was all hunky dory since that loads perfectly with NVSE and everything, it just no longer loads when put as an executable in MO. 

 

I also see no feasible way my .ini files could be a problem since this is the first time I've had Fallout installed on this computer and  I haven't gotten further modding it on this machine than NVSE and the 4GB. 

 

 

If my directions don't help solve your problem, Idk what to tell you. It works fine with 1.3.8, though.

 

Though I did just notice that 4GB Launcher is before NVSE in my guide, and I have people check to make sure NVSE is working in the 4gb Launcher portion. I think perhaps I should change that.... lmfao

I don't know what to tell myself either. There doesn't seem to be an explanation that makes any sense as to why MO isn't loading the 4GB but besides that it's all perfect. Thanks for trying to help though, I really appreciate it. 

[GrantSP]

Try invoking the 4GBFNV patcher with just "-laaexe" as the argument. I have used this method since MO version 1.3.4 and it works just fine for me.

All this is doing is removing the explicit placement of the patched exe and allowing the patcher to place it where it wants to. If you check with explorer afterwards you should find it in the 'exes' folder.

 

I doubt you will see any difference if you downgrade your MO to any version before this as there is nothing significant that has changed in the code used to call the executables. If you are having issues with 1.3.8 you will have them with 1.3.x.

 

I would still like to see your logs, not just snippets. Clear out the logs folder and start the game via the patcher in MO and either post them to a service like PasteBin or put spoiler tags around them and post them here.