I suppose this might be a compatibility issue related to motherboard or RAM memory, but I'm just an intermediate Windows user and I'd never seen those WER messages before. \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\Įsses arquivos podem estar disponíveis em: \\?\C:\Users\Lucas\AppData\Local\Temp\RDR8C7.tmp\empty.txt I checked dxdiag and it shows some strange WER error about Fallout 4 (the language of my windows 10 is pt-br, dx v12):. It seems a lot of people are having trouble with this game on Windows PC. I searched the internet for similar problems, I tried all advices, such as running steam and fallout as administrator, verifying data files, running in windowed mode, not using mods, deleting ini files in my documents folder, running in borderless windowed mode, updating nvidia drivers, disabling nvidia streaming service, etc etc. I've waited for 20+ minutes for the new game to load but it hasn't. Obviously there's no load existing game option because I've never played it before. The screen doesn't freeze, it just doesn't load. The game launches successfully, but when I select new game the loading gets stuck there. Apparently the save games are getting corrupted.
After that go back and fine the saved games and move them over with the exception of the last one or two. It should come up just like when you started for the first time. Find Fallout 4 save file and rename it to backup. I have also created the same texture archive using BSArch, but the result was exactly the same, the game simply stays in an infinite loading screen and also won't load the objects usually rotating on screen (not black loading screen though!).I recently bought a copy of Fallout 4 via Steam. Go to windows explorer users/(your user)/saved games/. Then I simply drag and drop the "textures" folder into archive2.exe and save the BA2 with the proper name (espname - Textures.ba2). My settings for a texture archive would thus look like the attached screenshot. My procedure to generate uncompressed archives is as follows: unpack BA2 archive (either texture or main) from mod into empty folder with archive2.exe -> go to "file" -> "new" in archive2.exe and select either "general" or "DDS" as format (depending on whether I wanna archive textures or meshes/materials/scripts etc.) and select "none" for compression and click ok. This happens 100% of the time and also on a new game with only 1 texture mod enabled which contains an uncompressed BA2 texture archive. Thus I wanted to create uncompressed BA2 archives to make better use of my m.2 PCIe SSD and started unpacking and repacking my texture mods with no compression selected in archive2.exe, but when I booted up the game and tried to load a savegame, I got into an endless loading screen and I had to kill the game via Task Manager. After reading about the slow decompression throughput of BSA archives (except SSE ones) due to the use of zlib in a comment by Zilav made over on the STEP forum's xLODGen beta thread I did some searching and found out that Fallout 4 also still uses zlib and therefore somewhat negates the benefits of having a fast SSD + CPU for loading times.
0 kommentar(er)
