It only happens if I start the either the normal or the 4GB exe through Mod Organizer.
This issue does not happen if I start the 4GB exe on its own. This issue does not happen if I start the game on its own with the normal exe. I can only navigate the main menu by memory, the ingame popups regarding the DLC is missing the text as well. The problem is that all of the text has disappeared or is invisible. The game starts, I can load a save and 'play'. Right now I can launch the 4GB exe through Mod Organizer. I'm trying to get Mod Organizer and the 4GB exe to work together, but despite following all of the advice, tips and workarounds it's still not happening. I'm running Windows 8.1 and a fresh install of Fallout New Vegas with no mods so far. I've stumbled upon a weird issue that I haven't encountered or read about before. You are absolutely correct, of course! I read that section yesterday but for some reason it didn't "click" in my brain that it was my solution.įollow up question though: You said "if you wish to have the original Update.ESM restored." Does this mean that there isn't a need to have the Update.ESM in the data directory as long as I have the Update - Clean activated in MO? Thank you for your time, it is appreciated!Įdit: To be clear, the guide says specifically to do it (I did go back and read it), however based on what you stated I just want to make sure I don't mess things up. Search your MO 'Mods' folder for a backup of Update.ESM, it will have a timestamp added to it like this: .2016_06_24_14_08_29Īll of this is also explained in the STEP guide just 2 sections before the step you are currently on.Simply do a cache verification using Steam and ALL original files will be restored.If you wish to have the original Update.ESM restored to 'Data' there are two methods at your disposal. Having said that, you have done nothing wrong, everything will work exactly as expected.
Some users never see this issue and some do, we haven't been able to pinpoint exactly what are the parameters on each system to trigger this behaviour. There is an oddity with how 圎dit saves files when run from inside MO.
0 kommentar(er)
