FNV - 4GB patcher refrains from starting game(?)

[Matallana0316]

The problem:

After downloading the 4GB Patcher and following the steps, when attempting to play NVSE from Mod Organizer it would then crash immediately without the game even opening.

To Reproduce:

Steps to reproduce the behavior:

1. Go to 'https://www.nexusmods.com/newvegas/mods/62552?tab=files'
2. Click on the 'Version that does not require the VC++ redist' file
3. Follow the steps like normal: go to every .ini file and mark them as "read only"
4. When trying to mark the first .ini file to "Read Only", it gave me the option to "apply this change to this folder only, or do you want to apply it to all subfolders and files as well?" I chose yes, since I couldn't apply the change to the file without doing so.
5. Either the .esms of the DLCs or mods will be denied accessed to, or the game will refrain from playing.

Environment:

• Mod Organizer Version that exhibits the issue: v2.5.0
• Last Mod Organizer Version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Mod Organizer: Windows 11

Details:

When trying to open NVSE (after successfully downloading the 4GB Patcher, marking .ini files as 'Read only",

and running the .exe as administrator): it first gave me the pop up saying: (Access To CaravanPack.esm Denied). I tried going to the DLC's .esm and marking it as "Read Only" from properties, the same way i did with the .ini files. It worked, but now Mod Organizer began telling me of other .esms and .esps of other DLC and even mods that were denied accessed to.

NOTE: I presumed I needed to make all of the .ini files in the Fallout New Vegas folder, not the Data folder, "Read Only". Not the just .ini's in Documents and the "fallout_default.ini".

After marking them all as "read only" the game, Fallout New Vegas, wouldn't even play at all. Frustrated, I uninstalled Fallout New Vegas from Steam and redownloaded its files. (I copied & pasted the older Fallout New Vegas files on a separate folder as a record for any mistakes to look at. Dunno if this helps). Even afterwards it wouldn't play.

EDIT: I've uninstalled Nahimic after I was told it was "known to cause issues with Mod Organizer, such as freezing or blank windows," but it still wont open Fallout New Vegas with NVSE or even the other launchers.

Now I've even tried opening it through steam, and now it wont open it from there and gives the message "failed to initialize renderer. Unknown error creating gamebryo renderer" before closing. I've read that its because I've tinkered too much with the files. Am I screwed?

Link to Mod Organizer logs:

I'm afraid I can't find the log window, nor do I know what it looks like.

USVFS:

I don't think I've ever used or seen a USVFS log. I only recently created this account to report the problem.

MO Interface:

My new interface after uninstalling Nahimic (also known as SonicSuite, SonicRadar, SteelSeries, A-Volute, etc.) because the program was "known to cause issues with Mod Organizer, such as freezing or blank windows"

[2024-03-29 12:43:20.035 D] command line: '"D:\ModOrganizer\ModOrganizer.exe" '
[2024-03-29 12:43:20.038 I] starting Mod Organizer version 2.5.0 revision 22714e5 in D:/ModOrganizer, usvfs: 0.5.5.1
[2024-03-29 12:43:20.038 I] data path: C:/Users/USERNAME/AppData/Local/ModOrganizer/New Vegas
[2024-03-29 12:43:20.038 I] working directory: D:/ModOrganizer
[2024-03-29 12:43:20.038 D] timing: MOApplication setup() 24 ms
[2024-03-29 12:43:24.516 I] using game plugin 'New Vegas' ('FalloutNV', variant Steam, steam id '22380') at D:/SteamLibrary/steamapps/common/Fallout New Vegas

If you need my full mod list, let me know.

[Liderate]

MO2 needs to be able to write the file date of the game plugins. So, being marked as read only will cause the error in the first image. The "Failed to initialize renderer" error is caused by having the game set to open at a resolution that is not supported by your monitor if I remember correctly.