Butiksside
STAR WARS™ Empire at War: Gold Pack
Alt Diskussioner Skærmbilleder Broadcasts Videoer Værksted Nyheder Guider Anmeldelser

STAR WARS™ Empire at War: Gold Pack

Butiksside
STAR WARS™ Empire at War: Gold Pack >  Værksted > Corey Losess værksted > EaWX: Thrawn's Revenge 3.4 (Updated April 2nd) > Diskussioner
EaWX: Thrawn's Revenge 3.4 (Updated April 2nd)
Beskrivelse Diskussioner1624 Kommentarer13877 Ændringsbemærkninger
 Denne tråd er blevet fastgjort, så den er sikkert vigtig
Corey Loses  [udvikler] 24. aug. 2018 kl. 13:46
Making a mod backup to continue saves
Making a mod backup to continue saves:
Once a mod is updated for Eaw, it generally does not remain compatible with older saves. You also cannotgo back to old versions manually. However, if you want to ensure you can finish a game, you can create a backup copy while you're still on a given patch. In order to do this go to the following folder:
C:\Program Files (x86)\Steam\steamapps\workshop\content\32470
and copy the 1125571106 folder. Then paste it into:
C:\Program Files (x86)\Steam\steamapps\common\Star Wars Empire at War\corruption\Mods
Create the mods fodler if you do not have it.
Now, you'll have a backup of the mod. In order to run that backup instead of the auto-updating workshop copy, put Modpath=Mods\1125571106 in your launch options. Make sure to go back to the original method once done or you won't be playing with updates.
< >
Viser 1-11 af 11 kommentarer
chrisma 22. aug. 2019 kl. 14:50 
I assumed that compatibility is granted within major versions, i.e. '2.2' , '2.3' with major updates anounced in the 'credit' screen.
Now, it appears that campaigns can't be finished anymore - unless mod versions are archived as described above - since the more frequent minor updates are not backwards compatible any longer ?
#1
Corey Loses  [udvikler] 22. aug. 2019 kl. 21:40 
We do our best to make updates compatible whenever possible. With some, like 2.3.2, we hoped it would be, but it can *never* be guaranteed because there's any number of things which can make it not be compatible.Changing the name of a unit in the code will make a save not be comaptible for anyone who has that unit being built somewhere by one of the factions in their game, for example. With some, we know for sure it won't be, like we've already said 2.3.3 won't be. This is why we repeatedly put the warnings about upcoming versions wherever we can, and these instructions wherever we can, so if people want to be sure about keeping their save the onus is on them to make a copy.
#2
chrisma 23. aug. 2019 kl. 6:50 
Thanks for the reply, Corey.

I understand that creating a total conversion is a lot of data to keep track of.

I would say version 2.3 is worth broken campaigns since it improved graphics (models, textures, star map), gameplay (enhanced rosters) and performance (i.e. saving files) noticeably, bringing the 'expanded universe' 'Galactic Civil War' to life.

Nevertheless, since this thread is pinned, can You link the major place to look for "warnings about upcoming versions" ?
#3
Corey Loses  [udvikler] 23. aug. 2019 kl. 7:27 
The major, most obvious place where they are displayed is ingame, on the save and load screen, as well as occaisionally in the holocrons in GC and sometimes even on the main menu (that's only when we're confident it'll break it. On top of that, I try to leave comments on the workshop, and news posts on Discord.
#4
Sexy Ace™ 23. aug. 2019 kl. 9:48 
What if you failed to do this before the update? any way to restore the old version?
#5
Wastydest 25. sep. 2019 kl. 4:41 
Ok I finally found all the folders. They were not under C:\Program Files (x86)\Steam\... , but under D:\(user)\SteamLibrary\steamapps\...
Sidst redigeret af Wastydest; 25. sep. 2019 kl. 5:11
#6
PewPewProfessional 2. apr. 2024 kl. 18:26 
Does this work if I download a copy of 3.3 from MOD DB or do I have to catch it before the update?
#7
Koreom 4. apr. 2024 kl. 13:08 
@PewPewProfessional it should work with the copy from MOD DB.

However, I am currently trying to launch the old version. I copied it into a folder "ThrawnsRevenge33", Previously tried it also with the Mod number. I launch it with "Modpath=Mods\ThrawnsRevenge33". But it still seems to load the 3.4 version that says that there was an update.

Anybode knows why this could be?
#8
chrisma 5. apr. 2024 kl. 6:13 
'Anybode knows why this could be?'

There was a recent port by the developer Petroglyph from 32bit to 64bit.

Not sure if this answers Your question, but it is a major change to all prior mods - no old save file will work with the current executable.
#9
Koreom 5. apr. 2024 kl. 13:19 
Nah that patch was out last year as far as I can see ...
3.2 works like it should, it also says in the title screen it is 3.2.
When loading 3.3 from ModDB it still says "this version updated to 3.4 on 2nd April"
#10
chrisma 6. apr. 2024 kl. 7:57 
I never tried downgrading via Mod DB, so I can't tell.

3.3. made the mod 'artistically complete' and the scripting framework finally stable for me.

EDIT: 3.4. does crash to desktop from the menu 'demo scene' with my current setup (PROTON 7).
Sidst redigeret af chrisma; 6. apr. 2024 kl. 10:45
#11
< >
Viser 1-11 af 11 kommentarer
Per side: 1530 50