NVSE Extender (aka NX)

[EmiSaka]

8 hours ago, johnhenry18 said:

Will v18 work with the newest version of ttw?

 

As far as I know, it should. They fixed the problems that were causing incompatibility with TTW 3.2

 

I've linked forum posts which suggest this (although since this is my first reply/comment, I don't know if they'll get through.

 

 

https://taleoftwowastelands.com/viewtopic.php?t=7024

 

[_brandi_]

In MO2 NX 18 is getting a warning of being incompatible during query in the warning tab.  Looking at the log for the mo_interface I'm seeing this repeated a few times:

 

22:58:05 [D] passed mod id: 0, guessed id: -1
22:58:05 [D] using mod name "NVSE Extender" (id 0) -> E:/Downloads/NVSE Extender v18.fomod
22:58:05 [D] Opened  "E:/Downloads/NVSE Extender v18.fomod"  using  "7z"  (from signature)
22:58:05 [W] WARNING: The extension of this file did not match the expected extensions for this format! You may want to inform the mod author.
22:58:05 [D] trying encoding utf-16
22:58:05 [D] not utf-16: Start tag expected. in line 1
22:58:05 [D] trying encoding utf-8
22:58:05 [D] interpreting as utf-8
22:58:05 [D] module name :  "NVSE Extender v18"
22:58:09 [D] installing to "C:\Users\User1\AppData\Local\ModOrganizer\FNV NC\mods\NVSE Extender"
22:58:09 [D] Installation successful
22:58:09 None of the selected mods can be updated.

 

Trying to run FNV with New California on a new install with MO2, and everything looked good on install, the game hangs on the start screen before giving the menus for the game.  Probably just missing something real simple on my end since I know it can work, but did it with Vortex which isn't working out for me for so much else.

 

Edit: Cleared up this part of it by putting a nvse_config.ini file:

[Logging]
EnableGameErrorLog=1
[RELEASE]
LogLevel=1

 

Hasn't solved the problem but NX isn't part of it that I can see. Sorry to take up your time!

[jaam]

Hy are you using MO2 with a 32bit game ? Use MO.

[RitualClarity]

1 hour ago, jaam said:

Hy are you using MO2 with a 32bit game ? Use MO.

I thought that issue was supposed to be fixed. Guess not.

[Amilyn]

MO is reporting an incompatibility with nvse_extender_ng.dll

 

I am assuming because of version differences and that some small update needs to be done for NVSE stable version 5.1b4 

 

But from what I could see, everything in game works well

[_brandi_]

I've been using the Fallout New California setup instructions for MO2, which is helping out.  They report that MO2 works and is stable with FNC.  Also the STEP Wiki is a help as that is where I found the .ini file instructions for use with NVSE that got rid of the error I was having with NX.

[_brandi_]

9 hours ago, Anisei said:

MO is reporting an incompatibility with nvse_extender_ng.dll

 

I am assuming because of version differences and that some small update needs to be done for NVSE stable version 5.1b4 

 

But from what I could see, everything in game works well

Oh!  Had to double check and that is what I'm using, but always good to double check!  Started over with a new profile, and working out just what the problem actually is, but at this point it is nothing from LL, so time to hit up the STEP wiki for more.  I'm sure that it is just a problem on my end on installing...it is so close...no errors that I can see in the logs, so it has to be something I totally overlooked.

[jaam]

Unless you are using the German censored version, you can ignore anything regarding _ng.dll

Do you have any error or warning reported for nvse_extender.dll ?

 

[theguy3]

I'm confused what brandi did to fix that specific problem. I'm using MO2 but had the .dll files manually extracted to the plugins folder.
What occurs after is


Even though it said failed, it allowed sexout to work properly. Removing those .dll files from the plugin, in-game notifications would tell me that the sexout module is no longer functioning.


Another mod I'm using somehow conflict with the extenders. The CASM_NV mod. Essentially it's an autosave mod. For some reason, when the extenders and this autosave mod are both active, the autosave mod will put save files in the overwrite folder in the MO2. I have to manually delete the overwrite folder every session. It's pretty annoying. May have been a cause for one instability crash due to the many save files.

If someone got any ideas how to fix this and/or the complications with NVSE extender and CASM_NV... i'd like your assistance. Thanks in advance.

[theguy3]

On 8/4/2019 at 3:38 AM, jaam said:

Unless you are using the German censored version, you can ignore anything regarding _ng.dll

Do you have any error or warning reported for nvse_extender.dll ?

 

So the last post i made (didn't read your post carefully...) ng.dll is a useless file for non-german censored version?

[jaam]

Yes. ng stands for No Gore.

[theguy3]

Okay removed it. that part of the issue is done.

But the overwrite folder of MO2 is still filling using the extender with the auto-save mod. Deleting the saves in the overwrite folder doesnt affect the save files on the game when loading. Not sure why... specifically why the extender has an effect on the auto-save which relies on the NVSE to work.

[RitualClarity]

The extender has a copy of the saves created when it does its thing. I usually just pack it up into a profile-save mod and ignore it otherwise. A few seconds. I usually pack up the random files created in MO's overwrite from various effects of playing into a single profile - mod. I do the same for Skyrim etc. etc. Keeps the Overwrite folder clean for other profiles and makes my search for causes of problems easier to resolve.

[mikepanda07]

what do with this old info? do i just instal from fomm now or do i gotta do some other changes? been awhile since you said something. 

[Fineness]

Can i use it with my MO 1.3.11 ? Because fallout nv sex mods only depends on FOMM ?

[dborg2]

3 hours ago, Fineness said:

Can i use it with my MO 1.3.11 ? Because fallout nv sex mods only depends on FOMM ?

You can use almost every mod manager. I personally had no issues with MO. Some older mod managers might get issues because of the type of files in NX ((like NMM and OLD FOMM),

[RitualClarity]

The most current FOMM that is available here shouldn't have any issues with NVSE extender. Pride was working on NVSE and the most recent FOMM edition available here. (along with others)  I have used it from time to time and even now it works as advertised.

[Fineness]

7 hours ago, dborg2 said:

You can use almost every mod manager. I personally had no issues with MO. Some older mod managers might get issues because of the type of files in NX ((like NMM and OLD FOMM),

Ok thanks !

[RitualClarity]

13 hours ago, Fineness said:

Ok thanks !

That issue was early on when NVSE and other tools were new. Now it all works.

[FlamingNinja]

On 10/13/2019 at 5:12 AM, dborg2 said:

You can use almost every mod manager. I personally had no issues with MO. Some older mod managers might get issues because of the type of files in NX ((like NMM and OLD FOMM),

well that just saved me a LOT of time. lol
glad to see people are still modding the fuck out of this game.

[yetti3145]

How in the world do I use MO2 with this? I'm very new to PC gaming as a whole and just recently got into modding so I'm having some real trouble. I figured out some things so far, like how to use the Data Files in FNVLauncher to get .esm mods, but this Extender is really confusing me. I've put it in the Data folder, in the FNV folder, in the MO2 folder. I saw that it's supposed to go into an NVSE folder? But I don't have such a folder, I mostly just put NVSE mods like JIP and Johnny Guitar just somewhere in the FNV folder? Idk what to do here. Everything else seems to be working. Nude bodies look fine, I had the masturbation and the vibrator animations work for a short while before everything went to hell. I'm also trying to use SexoutLite, btw. Trying to test it with my other mods, like Prject Nevada and AWOP and stuff. I'm going for a survival realistic playthrough.

[RitualClarity]

simply install it like any other mod. The scripts should engage and install the files properly.

 

Inside a spoiler ... there is instructions for a manual install if you desire to try that.

[yetti3145]

I've tried installing it normally but for some reason the game isn't picking up on NX...when I use MO2 to install from archive, it won't work. Tons of error messages, no game data. When I do it manually and put it into the FNV folder, or the Data Folder, it still doesn't get picked up. I've used 7zip to extract the files and place it all in every imaginable folder, I took the Nv18 FOMOD thing unzipped and tried putting it in therem still doesn't pick up on it...

[yetti3145]

NEVERMIND, I finally found it out, I had to compress it into a zip file and go from the install from archive. Sorry for my ignorance lol.

[RitualClarity]

10 hours ago, yetti3145 said:

NEVERMIND, I finally found it out, I had to compress it into a zip file and go from the install from archive. Sorry for my ignorance lol.

There is an FMOD version that wouldn't require such steps... however, it is great that you figured out how to get it to work for you.