Windows error sound when quick loading

[Hasmith99]

Whenever I quickload I get constant windows error sounds until the game loads. So far the game itself is working fine besides that but something is clearly wrong. Does anyone have any idea why this would happen? It started after I reinstalled ENBoost and changed some values on NVSR I think, not sure if that has anything to do with it.

[dubiousintent]

The "sounds" (audio alerts) could be anything from invalid keystrokes to invalid commands that Windows generates to alert you that something failed (such as a search that failed to locate the desired string).

 

Check for log files in the game root folder (where the FalloutNV.exe" file is found). As you say the game "seems fine", you aren't getting a CTD so the Windows Eventlog shouldn't have anything and most likely such errors are being caught, logged, and ignored by NVAC but other mods might as well. You will have to look through them all, preferably immediately afterwards so you can ignore anything older.

 

Be aware that "quick load" can easily be demonstrated to fail to restore the game to the same condition as it does when you exit completely to the desktop before resuming play. See if exiting the game and restarting doesn't avoid those alerts.

 

-Dubious-

[Hasmith99]

The "sounds" (audio alerts) could be anything from invalid keystrokes to invalid commands that Windows generates to alert you that something failed (such as a search that failed to locate the desired string).

 

Check for log files in the game root folder (where the FalloutNV.exe" file is found). As you say the game "seems fine", you aren't getting a CTD so the Windows Eventlog shouldn't have anything and most likely such errors are being caught, logged, and ignored by NVAC but other mods might as well. You will have to look through them all, preferably immediately afterwards so you can ignore anything older.

 

Be aware that "quick load" can easily be demonstrated to fail to restore the game to the same condition as it does when you exit completely to the desktop before resuming play. See if exiting the game and restarting doesn't avoid those alerts.

 

-Dubious-

The NVAC log says I'm getting "20214305 _ DISABLED _LOD_ERR", which I see you helped someone else with. No matter what I do though it won't go away. I've ran FNVLODgen and XLODgen, with trees unticked since apparently the error means an object with the "Has TreeLOD" flag was disabled, and it's still happening. I even did a full reinstall with a clean, unmodded save, and it still happens even though I didn't even have any lod mods.

[dubiousintent]

Sounds like you are already aware, but for the benefit of any lurkers: If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first.

 

Having identified an error is progress. Just for clarification: "FNVLODGen" (which is actually "xEdit" with the command line parameter of "-lodgen" baked in) renamed for use with FNV. The renaming of the EXE to be game specific is important, as that is how it knows which record format to use. The same applies to Sheson's alternative "xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL".

 

There are LOD files included with the game and some mods not considered explicitly "LOD". While you may not have added any "LOD mods" like NMC, that doesn't mean you can't have related issues. Various aspects are dependent upon your "load order".

 

My suggestion would be to rename the "Objects LOD" and "Trees LOD" folders listed on the mod description page to something else so either FNVLODGen or xLODGen will rebuild everything from scratch. In that instance, I would include the "Trees" option just for completeness as you are rebuilding ALL of the Objects LOD files. By renaming the existing folders you give yourself the option of restoring things if needed.

 

The "STEP" xLODGEN thread offers some insights as well, though most of the discussion is Skyrim related.

 

-Dubious-

[Hasmith99]

Well I feel pretty stupid rn

It was just RadeonPro doing it, not even quickloading, just pressing F9. The LOD error had nothing to do with it.

Just had to uninstall it and it was fixed

Thanks for the help anyway, dubious, appreciate it