Recent Problems (Save Crashes) image - Awakening of the Rebellion 2.8 mod for Star Wars: Empire at War: Forces of Corruption
Links to the steam workshop download and our discord can be found in the description! Awakening of the Rebellion is a total overhaul of Forces of Corruption. Inspired by the old RTS Star Wars: Rebellion, AotR brings many features from this game and other titles such as a more in-depth mission system, tech system, and many new units! Immerse yourself in the Galactic Civil War era as the fledgling Rebellion, the oppressive Empire, or the criminal Black Sun pirates. This mod is not for the feint of heart and will test your RTS skills with a completely overhauled AI and difficulty. Versions newer than 2.6 can be found on the steam workshop only (due to issues with the non-steam versions)
I wanted to give a little update on the lack of content recently for our mod. Unfortunately the last month has been a horrendous adventure trying to solve the mystery of why our saves keep crashing. We have released several alphas to our internal tester pool, each with less and less features to try and pinpoint the bug, but so far there has been little success. Because of this, mod development has stalled out for the short term until we can get this problem resolved again. This has been some of the most trying times for the mod team, with most of us either having life problems step in, or just being overall unenthusiastic to continue onward. Please bear with us for the time being. We refuse to release any version of this mod if it can not be smoothly played and save crashes are currently our top priority to fix. Hopefully we can come back with good news soon. If you have any leads on the main causes of save crashing, we would love to hear them and investigate.
Has anyone ever found where the logfile.txt and _except.txt files are located?
I can't begin to count how many times I have come across this frustrating white box of death nor the number of fruitless searches both local and online that I have made trying to locate them...
It used to exist when I played the game on Win-XP, but it stopped creating on newer windows versions. Even if you did have the two files you'd need a computer genius to understand it.
I even looked for it back when I used my XP regularly and still couldn't find it. Lol...
I use Notepad++ (an excellent program by the way) to view the XML files and to find broken tags, -etc. and was hoping (if I could ever find those two blasted files) to open them in that and look through to find where the errors were located.
I used to regularly mod George Moromisato's space game "Transcendence" and Notepad++ helped me to find the errors in the mods which I created it back in its older versions of .98-.99c.
Most of the time, the errors were a missing < or /> tag, but there were times when the problem lay in corrupted identifier codes.
Welcome to the club, Cause I see this a lot too.(Then again what modder doesn't) Well I used to, now instead I just get the EAWFOC has stopped working error instead. I had the same problem that involves saves crashing when loading. And never figured out what it was!
I think I figured a fix for one version of the glitch, but it came back later. If you've edited the GameConstants file, try removing it, get a new GameConstants and add whatever changes you made and put into the mod. Tiny chance that might work.
Is it general save crashes, or during one game type specifically? Like only during GC/Skirmish or is it with any save file?
Every time that I have seen the white box of death, it has been in during the gameplay and often before I take the opportunity to save anything.
It usually happens at those times when I have modified an XML file and given a unit a different ability than it normally has, or sought to add a new unit.
Sometimes it has occurred after I install a new mod that hasn't had all of the importnat bugs removed.
From what I can tell from past modding experience, there is a set syntax that the game engine checks all xml files against as it is loading them.
If there is an error in the syntax then the game will crash, but without being able to find and read the logfile and _exception.txt files, I have never been able except through trial and error to find out what file is causing the problem so I can repair it.
Mostly GC save crashes. That's what is giving the devs the most trouble.
Other mods, like the Foc Alliance mod, the EAW:Remake or Phoenix Rising mod, also ran into this problem.
The last time I encountered it was when I was playing the EAW:Remake Beta IV, though that Exception!-screen never popped up for me. Whenever I tried to load a corrupted save, I just had a CTD.
At that time the only solution to keep the save-files from being corrupted was to save every 10 galactic days, quit to the main-menu and then load the save again.
From what I know nobody found a real solution for this problem, but certain factors like the size of the GC(EAW:RE's main GC used to have 134 planets) or the size of the mod's .xml-folder seemingly influence the probability of it's appearance.
But the Beta III runs absolutely fine on the same GC and I don’t think there have been that many XML-changes between the two versions.
So you might want to ask some other mod author. I think Ghostrider from the Phoenix Rising mod knows a little more about how to avoid the issue: forums.revora.net/topic/87949-crashing-on-save-and-auto-save-game-somewhat-unplayable/ (with https... in front of that link)
The newest version of RaW also had this problem for me and some people but not everyone and that's weird
Beta III had the same save crash problems.
I did quite a lot of experimenting with it, to see what the cause could be.
Eventually lowered the planet count from 134 to something like 80, but the problems persisted. Eventually i discovered that saving every 10 days/cycles, then quitting and starting allowed me to play a lot longer. But this didn't always work either.
Strangly i only had these problems with the Empire, and could play the Rebellion no problem. But others did have the crash with the Rebellion, so eventually i stopped bothering to try and figure it out.
Now for Remake we recommend saving often, and always create a new file, instead of overwriting. Something to do with texture memory and saving sometimes corrupts the save or something. So if you create a new file, you could still go back and try again, instead of losing everything. This is prob why the save/quit every 10 days had some succes.
I've seen this occurrence with several mods including Battlefront Commander, Old Republic at War, very rarely Republic at War and even the vanilla game.
In my case (with Windows 10 64 bit) it most interestingly happens most often when either starting a battle (that way the autosave gets destroyed due to the crash happening at the loading screen) both land and space or during a battle when one has extreme amounts of fighters present like i.e. in Battlefront Commander when the Rebels have multiple Blue Diver Calamari Carriers present or Mandalorians with several Lucrehulks all spamming their fighters and then those masses engaging each other.
The Empire can get the same effect by spamming Escort Carriers or Secutor SDs.
Venators interestingly don't have the problem despite also having many fighters.
In Republic at War, the only time I had a crash so far was after playing more than three hours at once and doing several battles in quick succession where the crash happens again at the battle loading screen.
On the flip side, I never had any crash so far with Thrawn's Revenge 2.1 nor with the 2.2 Demo.
What disc do you need to install this mod? Is it empire at war gold pack?
You can install it on the steam and GOG versions. But if you mean a physical disk, then the gold pack disk is where you'd install it.
is this bug fixed?