2019, nvse still hates me

[KotaGhost]

So i have nvse downloaded, and everything set up like i had literally a day ago before i did a clean install of the game onto my new ssd. had a bunch of other issues that took me the last few hours to fix. and now, even though i have it installed, nvse just refuses to work for me. when i type in "getnvseversion" it tells me "version 5" but when i get into the game it tells me i do not have nvse and (specifically CASM) tells me i am on version -1

i have been searching the web for the last two hours.

i have validated my files

i have reinstalled nvse

i have reinstalled the mods giving me issues

i have nvse in the same folder as falloutnv.exe, not in the data folder.

nvse is being run as administrator, as well as falloutnv.exe and falloutnvlauncher.exe

 

 

 

if anyone knows where im going wrong please leave a comment (if this forum has any life in it still that is.)

[dubiousintent]

* Did you install Steam to it's default location? (You shouldn't need to run with Admin privileges if not.) If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. (And yes, it will affect NVSE as well.) This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you launching NVSE from a "desktop shortcut" or a mod manager? If a mod manager, check for specific instructions in it's documentation for implementing "script extenders".

 

-Dubious-

[KotaGhost]

so i read the articals, and did as told, but it still did not work

 

i have steam on my (D;) drive, new Vegas is on my (E;) ssd, they both have user permissions

 

i do use a shortcut, but i also have tried to use the actual exe both nvse loader and just the regular fnv launcher

maybe i have missed something? if you need other information that would assist, please do let me know

[KotaGhost]

i just tried moving the file to the same drive as my steam instalation (d drive) but it still does not seem to work

[KotaGhost]

SO i found out what my issue was. for those that are dumb like me. install JIP LN NVSE like the mods tell you too. and archiveinvalidation invalidated didnt hurt either

[dubiousintent]

Just to be clear: "archiveinvalidation invalidated" is a specific (older) "ArchiveInvalidation" (AI) method.

 

Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation (AI)" off-and-then-on again after installing or removing one of them so it recognizes that there are loose files (added by the mod) which have to be used in place of the vanilla files in the BSA files or are no longer there and the BSA files should be used instead. That failure to toggle is the most common reason behind most "texture problems". This is usually evidenced by red "!" icon for missing meshes, and solid colors for missing textures, or "messed up" textures. This "ArchiveInvalidation" mechanism is incorporated in all the currently used mod managers, so there is no need to (and problems arise if you do) install older mods to provide that capability. ONLY USE ONE METHOD of AI, especially if you have multiple mod managers installed. Otherwise they will conflict, as they use their own "arbitrarily chosen" names for the AI BSA files. (There is not a standardized name used among them all.) Please see the 'ArchiveInvalidation (by Manager)' section and also see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

-Dubious-