solrac1979 Posted March 11, 2010 Share Posted March 11, 2010 :thumbsup: SOLVING THE PROBLEM OF THE SAVE GAME-------------------------------------------------- -------------------------------------------------- ----- Hello everybody! For those not getting saved!I had this same problem and managed to solve. I made a few changes to the 'FalloutPrefs.ini'. 1. Open the file and find the following command line: 'QuickSave =' and 'Quickload ='; 2. Use Notepad: 3. Delete the values that are after the "="; 4. It has to be equal to that exeter below: ...Hotkey1 = 0002FFFFHotkey2 = 0003FFFFHotkey3 = 0004FFFFHotkey4 = 0005FFFFHotkey5 = 0006FFFFHotkey6 = 0007FFFFHotkey7 = 0008FFFFHotkey8 = 0009FFFF QuickSave = Quickload = ... 5. Then save the file; 6. Finally, leave the files 'FALLOUT.INI' and 'FalloutPrefs.ini' read-only; 7. You are done. These changes have worked with me. :rolleyes: I hope I have helped. Ha! sorry for my English is not my native language. ------------------------------------------------------------------------------------------------------Processor: Pentium® Dual-Core CPU E5300 @ 2.60GHz (2612 MHz)Operating System: Windows 7 Ultimate, 64-bitDirectX version: 11.0 GPU processor: GeForce GTS 250Driver version: 196.21CUDA Cores: 128 Memory interface: 256-bit Total available graphics memory: 1791 MBDedicated video memory: 512 MBSystem video memory: 0 MBShared system memory: 1279 MBVideo BIOS version: 62.92.7E.00.00IRQ: 24Bus: PCI Express x16 [Components] nvCplUI.exe 2.8.290.13 NVIDIA Control PanelnvWSS.dll 6.14.11.9621 NVIDIA Workstation ServernvViTvS.dll 6.14.11.9621 NVIDIA Video ServernvMoblS.dll 6.14.11.9621 NVIDIA Mobile ServerNVSTVIEW.EXE 7.17.11.9621 NVIDIA GeForce 3D VisionNVSTTEST.EXE 7.17.11.9621 NVIDIA 3D Vision Test ApplicationNVSTRES.DLL 7.17.11.9621 NVIDIA 3D Vision Module (0)NVMCTRAY.DLL 8.17.11.9621 NVIDIA Media Center LibrarynvDispS.dll 6.14.11.9621 NVIDIA Display ServerNVCPL.DLL 8.17.11.9621 NVIDIA Compatible Windows7 Display driver, Version 196.21 PhysX 09.09.1112 NVIDIA PhysXNVCUDA.DLL 8.17.11.9621 NVIDIA CUDA 3.0.1 drivernvGameS.dll 6.14.11.9621 NVIDIA 3D Settings Server------------------------------------------------------------------------------------------------------ Link to comment Share on other sites More sharing options...
Fonger Posted March 11, 2010 Share Posted March 11, 2010 you do know that quicksaves are notoriously dangerous always use hard FORMAL saves and ALWAYS create a new save NEVER save over an existing save The game you save Will be your own. Link to comment Share on other sites More sharing options...
solrac1979 Posted March 11, 2010 Author Share Posted March 11, 2010 :whistling: Friend this error occurs in the 'quicksave' as in 'save' in many different computer configurations. Just put this topic because I noticed many people on the 'Net' with the same problem I had. If you have not had that good! But I leave the topic for anyone in need. Later. Goodbye! :thumbsup: Link to comment Share on other sites More sharing options...
nosisab Posted March 11, 2010 Share Posted March 11, 2010 :whistling: Friend this error occurs in the 'quicksave' as in 'save' in many different computer configurations. Just put this topic because I noticed many people on the 'Net' with the same problem I had. If you have not had that good! But I leave the topic for anyone in need. Later. Goodbye! :thumbsup:I'm lost here, what error are you telling about? removing the key bindings just prevent the quicksave and quickload Link to comment Share on other sites More sharing options...
nosisab Posted March 11, 2010 Share Posted March 11, 2010 moved by curiosity I removed the values as in the first post (after saving the ini) and as I thought I could not quick save/reload anymore. So I used the ingame options to use F5 and F9 to do it and... I think I understand the OP now, the values are placed incorrectly by the ingame option, with zeroes in the end instead hex Fs and that mess with several things, I could not shot without it being took by a quicksave/load, the same with activating the pipboy... So you were right solrac1979, at least in part. But making the ini files readonly is bad idea, a better solution is changing the wrongly created (by the ingame keybinding option) tailing zeroes with Fs and the issue is gone... and the saves and loads performs as expected. Link to comment Share on other sites More sharing options...
olafreinhardweyer Posted March 12, 2010 Share Posted March 12, 2010 Hi folks, All you need to clean a corrupt savegame is to load it and kill yourself in an explosion. Stuck Animation info is stored in the save and brought to the memory buffer, the blowwill clear the buffer again and after autoloading the save again then you can make a clean save. You don't believe, you visit Crash To Desktop Begone http://www.fallout3nexus.com/downloads/file.php?id=10236 Olaf moved by curiosity I removed the values as in the first post (after saving the ini) and as I thought I could not quick save/reload anymore. So I used the ingame options to use F5 and F9 to do it and... I think I understand the OP now, the values are placed incorrectly by the ingame option, with zeroes in the end instead hex Fs and that mess with several things, I could not shot without it being took by a quicksave/load, the same with activating the pipboy... So you were right solrac1979, at least in part. But making the ini files readonly is bad idea, a better solution is changing the wrongly created (by the ingame keybinding option) tailing zeroes with Fs and the issue is gone... and the saves and loads performs as expected. Link to comment Share on other sites More sharing options...
Recommended Posts