![]() Then, I was able to actually play the EAW-Remake mod for the first time. It patched the executable automatically and quickly. Thus, I had to manually go into the EAW game install folder, go inside the Forces of Corruption sub-folder, backup the "swfoc.exe" file by copying it and renaming the copy: "", then I found the folder for "4GB_Patch" that came with the Steam version, but it wasn't actually installed, so I ran the 4GB Patch program and clicked on my "swfoc.exe" file in the install program for the patch. ![]() However, after first starting the EAW-GC Remake mod after I first installed it properly to the Forces of Corruption DLC folder, the game with the mod enabled would crash-to-desktop every time I tried to start a game, since the game executable was trying to load mod assets that are far over 4 GB of data. The 4 GB RAM unlocker patch for the base game's executable file does indeed come standard in both the GOG and Steam versions of the game. The base game engine only runs computations on one, maybe two, CPU cores and can only use <4GB of system RAM to store data. This means, even on a god-tier 64-bit Intel i9-9900KS CPU 5.0 GHz all-core OC, with 64 GB of DDR4 3200 RAM, a Samsung 970 PRO 1TB NVMe SSD, and a GeForce RTX 2080 Ti XC Ultra GPU 2.15 GHz OC with 12 GB GDDR5 VRAM, this game will crawl at less than 20 FPS in medium space battles in the EAW-GC remake mod and drop from 10 FPS to 0 FPS for a few seconds in large space battles. It wasn't until about 2012 that most games took full use of 64-bit processors. The game came out in 2006, and I'm assuming its engine only supports 32-bit processing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |