JIP LN and MO no longer working

[Migck]

Greetings, sorry that I just post to barge in with my problems, but after trying stuff for hours on end I'm left with no options.
 
I'll try to describe my situation. Until recently I was playing Fallout New vegas through Mod Organizer 1.3.11 without a hitch, and even loading all NVSE plugins, including the JIP LN plugin version 53.40, through it with no trouble.
 
The only thing I can think of that could have changed that is updating the nVidia driver to version 390.77, I play on a laptop with a GTX 860M. Afterwards, MO is simply unable to launch the game if JIP LN is installed.

I've tested trying to launch it with nothing but JIP LN installed. No matter if it's installed through MO or manually placed in the real FNV data folder, no matter which workaround method. It's like the game simply fails to load any assets when it is installed. At first I got a pure purple screen with no sound, suggesting that the menu had loaded but that there was complete failure to load any textures in it. Now it's just black screen and CTD for the most part. With NVAC installed, it hangs on the black screen, I'll attach the log if it's any use:

31132438 _ NewVegasAntiCrash FalloutNV.exe
31132438 _ 0FA90000 07050000 nvac.dll
31132438 _ 0F980000 05010040 nvse_1_4.dll
31132438 _ 76FE0000 0A003FAB ntdll.dll
31132444 h 00A087E5 83782800 FalloutNV.exe
31132444 h 00A0886E 8951288B FalloutNV.exe
31132444 h 00A08877 83782800 FalloutNV.exe
31132444 h 00A0CBA2 8B510852 FalloutNV.exe
31132444 h 00A0CBA9 8B480451 FalloutNV.exe
31132444 h 00A0CB03 8B480883 FalloutNV.exe
31132444 h 00A0CD5F 3B480875 FalloutNV.exe
31132444 h 00A0D00F 8B50083B FalloutNV.exe
31132444 h 00A0D012 3B510C75 FalloutNV.exe
31132444 h 00A0D02C 83790C00 FalloutNV.exe
31132444 h 00A0D040 8B108B4D FalloutNV.exe
31132444 h 00A0D045 8B4204FF FalloutNV.exe
31132444 n 00000000 00A0D04A
31132444 r 00A0D04A 00000000 FalloutNV.exe
31132444 h 00A0D04D 8941048B FalloutNV.exe
31132444 h 00A0D056 89420CEB FalloutNV.exe
31132444 h 00A0D0A2 8B480883 FalloutNV.exe
31132444 h 00A0D0AB 894A088B FalloutNV.exe
31132444 h 00A0D0B1 8B400883 FalloutNV.exe
31132444 h 00A0CF2F 8B51048B FalloutNV.exe
31132444 h 00A0CF46 8B51048B FalloutNV.exe
31132444 h 00A0CF51 890C828B FalloutNV.exe
31132444 h 00A09447 8B513081 FalloutNV.exe
31132444 h 00A0CBA2 8B510852 FalloutNV.exe
31132444 h 00A0CBA9 8B480451 FalloutNV.exe
31132444 h 00A0CB03 8B480883 FalloutNV.exe
31132444 h 00A0CD5F 3B480875 FalloutNV.exe
31132444 h 00A0D00F 8B50083B FalloutNV.exe
31132444 h 00A0D012 3B510C75 FalloutNV.exe
31132444 h 00A0D02C 83790C00 FalloutNV.exe
31132444 h 00A0D040 8B108B4D FalloutNV.exe
31132444 h 00A0D045 8B4204FF FalloutNV.exe
31132445 n 00000000 00A0D04A
31132445 r 00A0D04A 00000000 FalloutNV.exe
31132445 h 00A0D04D 8941048B FalloutNV.exe
31132445 h 00A0D056 89420CEB FalloutNV.exe
31132445 h 00A0D0A2 8B480883 FalloutNV.exe
31132445 h 00A0D0AB 894A088B FalloutNV.exe
31132445 h 00A0D0B1 8B400883 FalloutNV.exe
31132445 h 00A0CF2F 8B51048B FalloutNV.exe
31132445 h 00A0CF46 8B51048B FalloutNV.exe
31132445 h 00A0CF51 890C828B FalloutNV.exe
31132445 h 00A09447 8B513081 FalloutNV.exe
31132445 ; MODELS: Unable to load CTL file
31132445 ; DEFAULT: Unknown file type on file 0
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 00884514 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 00884514 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 00884514 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 005ACBB8 00000012 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 005ACBB8 00000012 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 005ACBB8 00000012 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0059BFC6 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0059BFC6 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0059BFC6 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0045562F 00000005 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0060C909 00000003 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0060C909 00000003 FalloutNV.exe
31132449 h 0FD08637 3A480C1B jip_nvse.dll
31132449 ^ 0060C909 00000003 FalloutNV.exe
31132449 h 00867A2A C6401C01 FalloutNV.exe

 

 

The oldest version of JIP LN archived, 36.50, does allow the game to load, but that's not really an option. Anything from 52 onwards suffers the same. If I were to guess, I'd say it has something to do with the xml stuff it includes, but I have no idea about that. And rolling back the graphics driver didn't help.

 

 

So well, MO is kinda vital to how I play NV, so I looked into trying out MO2 of course... to my surprise, this problem does not appear in it. The game can load with JIP LN installed fine. But unfortunately other problems appeared for me.

 

I managed to migrate my profiles and files to it correctly, but alas, every time I try to start the game from MO2, it seems it activates and deactivates esps and esms and shuffles their load order at random, and I'm puzzled as to why. It does the same when trying to launch any application from it, like Wrye Flash. Basically, I can load the game, but I can't play it with my desired load order. But I suppose that's more about MO2 issues than my actual predicament.

 

 

Well, sorry if this is no use. I was suggested by RoyBatty to contact GrantSP about these issues, but I suppose I can make them public in case someone else may also help. I'll keep trying to make MO2 work correctly on my end, since currently it seems whatever I try for MO1 is not going to help.

Edited January 31, 2018 by Migck

[Migck]

Well, indeed it had to be something else in my setup causing the problem. I recently tried relaunching the game through MO1 again, and I can't see any trace of the original problem. There's been a JIP LN update in the meantime, but I doubt that was the cause. I wouldn't mind not encountering such problem ever again anyways.

 

Apologies again, since in retrospect this entire thing was a desperate barging in for a solution.

[Migck]

Well, turns out that my woes with MO2 was due to using the Git beta instead of the stable release 2.1.1 at Nexus... so my grieves have finally ended, I'm migrated over to MO2 well enough that I can play again.

Apparently MO2 doesn't let me handle how BSAs are loaded, but it's a minor issue, I've just unpacked the preorder DLCs and load them as loose files instead.

 

Long live MO, now to wait for Vortex :D . Sorry that this whole thing was pointless, still gotta wonder what the hell has happened on my end for JIP and MO1 to no longer be on good terms, hopefully it won't happen again for at least a while.

[GrantSP]

Regarding the OP, there is something else at play in your setup that is causing you grief. I have maintained a working install of MO and MO2 for FNV and TTW for sometime now and all of them have worked with whatever version of JIP_LN that was installed.

 

As for MO2 not allowing you to handle your BSAs, this is a design choice, not an issue.