New Version 1.2: - Attempt to fix the pathing issues that caused the tool to not insert the mods.
New Version 1.1: - It's now much more robust and when an NMS update hits or you need to reinsert mods it will take the backup original file again - Just run ENABLE-MODS.bat again. - backups are now created in a more robust way - tried to fix pathing issues - improved some other minor things
It's not needed anymore. But it's still usefull to avoid the mod warning screen since we still can't skip it with VR controls and need to use the keyboard to press a key once.
Is there a possibility to disable the console output? It causes additional pause, so disabling it may speed up the process. Do you have the source code of the programs?
Have RIft S - VR working nicely, albeit with the flipping mods nag. Anyone got the 5mb Mod limit working. I have almost 20mb of MODs - one of them alone is 11mb. So I would rather not them.
Looks like Hello Games fixed the soft lock when using mods in VR. You can go back to doing it the normal way. Delete the nomods text file and create a MODS folder and drop it all in there. I did have to hit a key on my keyboard to get past the warning screen. Hopefully they patch a fix in for it to be based on controller click.
Thanks for much for this interim fix. The game wouldn't have been any near as enjoyable without the mods I was able to run with the 5 meg limit.
try using a mod merger. - removes incompatibilities and reduces mod size as it combines the changes into a single mod instead of each mod overwriting all the lines of the previous one
Oh I hadn't looked into that. Educated myself and combined a bunch of mods thanks. One mod was a sound replacement mod that was just too big (the visor sound silencer mod). Was so happy to be able to use that one. No more digital farting when using the visor. With headphones on it was a nightmare.
Great mod, Mjjstral! I have been using it since release. However, it seems to have stopped working with the latest experimental branch. It crashes when loading. Won't even show the menu. Switching to release NMS fixes this issue and the game loads and plays fine. This is with 1.30 and 1.31. I hope you can work your magic and make it work again since most of the improvements hit the beta first. Thanks again for your hard work and support.
Looks like you are correct, sir. The one thing I didn't try was launching the exp. branch in flat mode. It does the same thing. Crash after black screen. I will now start the process of trying to eliminate/update the mods that are causing it. Thanks again for all your hard work. Update: the responsible mod was a launch cost reducer. Everything else worked fine.
Be aware the update today changed the NMSARC.FE28D146.pak file so if it has not been updated your game will come up with Corrupt file message in 2d or just blackscreen and music if in VR.
I just reran the .bat file and it updated the file appropriately. Hopping they didn't stick anything important in there haha. So far my 11 or so mods are up and running just fine.
That's what I will do in future just run the Enable.bat and not run Disable first or at least check the date stamp of the file before doing that. The new pak file has had some stuff added to it, the update did not effect the Mods I am using either.
Noticed today while looking at pak file that is created that the tool does not add back in a couple of folders added in last update even though it extracts them.
Don't think it bothers the game as it still works apart from a couple of issues with VR controllers now, but playing Vanilla has same issues after last update. So it is not the Mods or this Tool.
The tool will always stick to the most current pak. Updated pak has priority over the old backup for ENABLE as well as for DISABLE so don't worry. After an update just run ENABLE again and you're fine. Also @DelDredd the tools should now include all JSON files again (1.31) . Thank you for noticing me.
Fixed it by disabling the mods with the bat file. Then verified files in Steam. It downloaded the file which couldnt be verified. And I confirmed then that the game loaded without any messages. Re ran the enable bat file and its working ok now.
Doesn't work for me, the Enable-mods open a console window, but that's all. Nothing happend after. I have insert the correct folder path into the text file, tried to run the file in C/ and root folder of NMS, still the same...
You did follow the command prompt and hit Enter to start??. Putting tool Files in the Root of C:\ or the Drive where NMS is installed seems to get it to work for most people.
Did you use the Symlink method (posted below) originally from trevix.
Some systems might have problems with paths with blank spaces. To go around this, create a symlink on your root folder and point the NMS_PCBANKS_FOLDER.txt to it. To create the symlink, use this on your CMD Line: mklink /D "c:/NoMan'sSky" "C:\Program Files (x86)\Steam\steamapps\common\No Man's Sky\GAMEDATA\PCBANKS" (or where your game is)
Then point NMS_PCBANKS_FOLDER.txt to c:/NoMan'sSky
This worked for me with Tool on C:\ drive, game on another
so is mklink /D "c:/NoMan'sSky" "C:\Program Files (x86)\Steam\steamapps\common\No Man's Sky\GAMEDATA\PCBANKS" copied and pasted into the CMD window i can open up by using CMD in the windows search?
or do i copy and paste it into the cmd window that opens with the ENABLE MODS file?
what does it mean when i have to "point" it to another folder?
140 comments
- Attempt to fix the pathing issues that caused the tool to not insert the mods.
New Version 1.1:
- It's now much more robust and when an NMS update hits or you need to reinsert mods it will take the backup original file again - Just run ENABLE-MODS.bat again.
- backups are now created in a more robust way
- tried to fix pathing issues
- improved some other minor things
"NMS_PCBANKS_FOLDER.txt?" .... I found the folder but .txt
Thanks for much for this interim fix. The game wouldn't have been any near as enjoyable without the mods I was able to run with the 5 meg limit.
Thanks again for your hard work and support.
I will now start the process of trying to eliminate/update the mods that are causing it.
Thanks again for all your hard work.
Update: the responsible mod was a launch cost reducer. Everything else worked fine.
The new pak file has had some stuff added to it, the update did not effect the Mods I am using either.
Extracting: INPUT/ACTIONS.JSON (320913 bytes)
Extracting: INPUT/GAMEPAD.JSON (326 bytes)
Extracting: INPUT/KNUCKLES.JSON (59272 bytes)
Extracting: INPUT/TOUCH.JSON (52771 bytes)
Extracting: INPUT/VIVE.JSON (47721 bytes)
Extracting: PLAYTOGETHER/SESSION_JPG (110076 bytes)
Don't think it bothers the game as it still works apart from a couple of issues with VR controllers now, but playing Vanilla has same issues after last update. So it is not the Mods or this Tool.
Also @DelDredd the tools should now include all JSON files again (1.31) . Thank you for noticing me.
Putting tool Files in the Root of C:\ or the Drive where NMS is installed seems to get it to work for most people.
Did you use the Symlink method (posted below) originally from trevix.
Some systems might have problems with paths with blank spaces. To go around this, create a symlink on your root folder and point the NMS_PCBANKS_FOLDER.txt to it.
To create the symlink, use this on your CMD Line:
mklink /D "c:/NoMan'sSky" "C:\Program Files (x86)\Steam\steamapps\common\No Man's Sky\GAMEDATA\PCBANKS"
(or where your game is)
Then point NMS_PCBANKS_FOLDER.txt to c:/NoMan'sSky
This worked for me with Tool on C:\ drive, game on another
or do i copy and paste it into the cmd window that opens with the ENABLE MODS file?
what does it mean when i have to "point" it to another folder?