one of the worst glitches ive experienced so far

[HBEggspert]

i experienced 2 glitches in rapid succession. I'm playing on insane so i save frequently.

I set up trebuchets inside of tempest and once they received 5 tempest debuffs they were unable to drop out of siege mode and ended up just slowly rotting into the tempest with no way to move them or do much about it.
fine ok.
learned my lesson
i reload my game and the load was about 10 minutes ago while the trebuchets were driving through a different tempest field on the map.
the game loads with 1 trebuchet instantly blowing up and the other having 5 tempest debuffs on it, but when i saved both trebuchets were full health, no tempest debuffs.

so now the only save i have is from over a hour ago where i can load and not have units instantly lock down to die or just explode.

i'm assuming something about loading a game with vehicles in tempest give them a automatic debuff, but i got no idea.

I'm a chicken farmer, not a programmer.

I assume balancing issues since its a new release and playing on insane is my own fault, but this one has really dug deep into me. No fault of my own the game altered saved data or failed to save data appropriately and now i got to restart.

you can make the argument to keep units out of tempest, but it was a strategic decision to be able to drop arty on units id otherwise have to fight, i was monitoring the tempest debuff extremely closely which is how i know the save state is completely wrong and had no idea you cant drop siege mode once it hits 5 tempest debuff and your unit just burns with no options, which i assume is a unintended glitch.

TLDR:
the saved game i load isnt how i saved the game and is killing key units before i can move the camera to the unit forcing me to either load a autosave from over a hour ago, or restart the mission through no bad decision or fault of my own.


Just annoyed about it all and had to get it off my chest.

[Solomon Kane]

Not sure what you expected, it is not really the games fault for you to place vehicles inside tempest fields, command and conquer had it with tiberium fields and infantry.

[PhamTrinli]

Originally posted by HBEggspert:

i experienced 2 glitches in rapid succession. I'm playing on insane so i save frequently.

I set up trebuchets inside of tempest and once they received 5 tempest debuffs they were unable to drop out of siege mode and ended up just slowly rotting into the tempest with no way to move them or do much about it.
fine ok.
learned my lesson
i reload my game and the load was about 10 minutes ago while the trebuchets were driving through a different tempest field on the map.
the game loads with 1 trebuchet instantly blowing up and the other having 5 tempest debuffs on it, but when i saved both trebuchets were full health, no tempest debuffs.

so now the only save i have is from over a hour ago where i can load and not have units instantly lock down to die or just explode.

i'm assuming something about loading a game with vehicles in tempest give them a automatic debuff, but i got no idea.

I'm a chicken farmer, not a programmer.

I assume balancing issues since its a new release and playing on insane is my own fault, but this one has really dug deep into me. No fault of my own the game altered saved data or failed to save data appropriately and now i got to restart.

you can make the argument to keep units out of tempest, but it was a strategic decision to be able to drop arty on units id otherwise have to fight, i was monitoring the tempest debuff extremely closely which is how i know the save state is completely wrong and had no idea you cant drop siege mode once it hits 5 tempest debuff and your unit just burns with no options, which i assume is a unintended glitch.

TLDR:
the saved game i load isnt how i saved the game and is killing key units before i can move the camera to the unit forcing me to either load a autosave from over a hour ago, or restart the mission through no bad decision or fault of my own.


Just annoyed about it all and had to get it off my chest.

Seems like not everything is getting saved/reset in the game state when loading saved games.

[HBEggspert]

Originally posted by PhamTrinli:

Originally posted by HBEggspert:

i experienced 2 glitches in rapid succession. I'm playing on insane so i save frequently.

I set up trebuchets inside of tempest and once they received 5 tempest debuffs they were unable to drop out of siege mode and ended up just slowly rotting into the tempest with no way to move them or do much about it.
fine ok.
learned my lesson
i reload my game and the load was about 10 minutes ago while the trebuchets were driving through a different tempest field on the map.
the game loads with 1 trebuchet instantly blowing up and the other having 5 tempest debuffs on it, but when i saved both trebuchets were full health, no tempest debuffs.

so now the only save i have is from over a hour ago where i can load and not have units instantly lock down to die or just explode.

i'm assuming something about loading a game with vehicles in tempest give them a automatic debuff, but i got no idea.

I'm a chicken farmer, not a programmer.

I assume balancing issues since its a new release and playing on insane is my own fault, but this one has really dug deep into me. No fault of my own the game altered saved data or failed to save data appropriately and now i got to restart.

you can make the argument to keep units out of tempest, but it was a strategic decision to be able to drop arty on units id otherwise have to fight, i was monitoring the tempest debuff extremely closely which is how i know the save state is completely wrong and had no idea you cant drop siege mode once it hits 5 tempest debuff and your unit just burns with no options, which i assume is a unintended glitch.

TLDR:
the saved game i load isnt how i saved the game and is killing key units before i can move the camera to the unit forcing me to either load a autosave from over a hour ago, or restart the mission through no bad decision or fault of my own.


Just annoyed about it all and had to get it off my chest.

Seems like not everything is getting saved/reset in the game state when loading saved games.

I hope my post either let someone know of save state issue's existence so they dont waste their time with the same mistake i did, or helped one of the devs identify it. Like i said initially, new game, glitches expected, this was the one that frustrated me.

I have started keeping 2-3 saves rather than 1 which prevents me from getting soft locked into dead units since i can reload from 10-15 minutes ago, or 20 minutes ago, rather than restarting a hour long mission.


I also experienced a glitch where it autosaved as missions critical scientists died, so you would just load into a failed missions, but i chopped that up my mistake since i used an air raid and targeted the fence rather than cleared the area.

[Paladestar]

Originally posted by PhamTrinli:

Seems like not everything is getting saved/reset in the game state when loading saved games.

Yeah, not as bad as it was in the demos, but still some things they need to sort out. In the demos destroyed neutral buildings were repaired on reloading, we can see that this has now been fixed in the full game.

The game seems to forget the money you have when saving, e.g. save with 30,000/30,000, or something like that, and load and you'll have 11,000/30,000 or 13,000/30,000 etc.

It's also forgetting cosmetic destruction, like trees that get knocked over. Save and load and the cosmetic damage is reset.

Any units actively carrying out orders when you save will have those orders cancelled on loading that save.

On loading a save turret buildings all reset their facing direction to whatever way they were facing when they were originally placed, not the way they were facing when saved.

Some of these things are a bigger problem than others. I can't believe the credits one is still around as that one just seems too obvious to miss and has been a problem since the demos!

[HBEggspert]

Originally posted by Paladestar:

Originally posted by PhamTrinli:

Seems like not everything is getting saved/reset in the game state when loading saved games.

Yeah, not as bad as it was in the demos, but still some things they need to sort out. In the demos destroyed neutral buildings were repaired on reloading, we can see that this has now been fixed in the full game.

The game seems to forget the money you have when saving, e.g. save with 30,000/30,000, or something like that, and load and you'll have 11,000/30,000 or 13,000/30,000 etc.

It's also forgetting cosmetic destruction, like trees that get knocked over. Save and load and the cosmetic damage is reset.

Any units actively carrying out orders when you save will have those orders cancelled on loading that save.

On loading a save turret buildings all reset their facing direction to whatever way they were facing when they were originally placed, not the way they were facing when saved.

Some of these things are a bigger problem than others. I can't believe the credits one is still around as that one just seems too obvious to miss and has been a problem since the demos!

thank you for this information. I will make sure to try to spend to zero before i save and work around these till corrected.

[aeroth]

Tempest damage is too fast anyway. it needs to build up more slowly

[Cal]

Iv'e had my harvester get stuck in it's building, if you sell the building and then cancel it fixes it

[Cat]

Yeah, that sucks. I remember playing C&C Red alert remastered and saved game with the mission timer being at 3 minutes remaining mark. Loaded the saved file and I immediately lost due to timer hitting zero.

[HBEggspert]

Originally posted by Cat:

Yeah, that sucks. I remember playing C&C Red alert remastered and saved game with the mission timer being at 3 minutes remaining mark. Loaded the saved file and I immediately lost due to timer hitting zero.

you brought up trauma i forgot i had.

Originally posted by aeroth:

Tempest damage is too fast anyway. it needs to build up more slowly

i think it be interesting if they kept the same damage but only let it damage you as you moved through it, so you could roll in the tempest, get a -3 debuff, and just idle, not move, and keep the -3 without dying, then it starts to build again as you move.
I found a few fields where you can straddle the edge of it on a cliff and take no damage.

Originally posted by Cal:

Iv'e had my harvester get stuck in it's building, if you sell the building and then cancel it fixes it

havnt had this one happen, but that sounds like a ♥♥♥♥♥ when your running a timed mission and it just decided to eat some of your time through no fault of your own

[HBEggspert]

Originally posted by Solomon Kane:

Not sure what you expected, it is not really the games fault for you to place vehicles inside tempest fields, command and conquer had it with tiberium fields and infantry.

My original response was removed for hurting your feelings. ill try not to hurt your feelings in the future.