yes NPC chatter worked for me
Help needed with fixing
-
- Request:
- SWAT_OP-R8R
- Thread is marked as Resolved.
-
-
@OP: i've sent you a PM
and yes, i've managed to finish the mission.
try this (read: very unlikely, but maybe it helps) : use all your batteries for the shield up, and before the strike carrier gets destroyed and you get the "Well done" message, your shield must NOT be 100% full capacity. try it with 30% like me.
-
Strike Carrier prob:
it is weird... I did some pretty detailed tests on that mission and the created autosavesthe autosave that i received for tests crashes during that mission... so far so good
I have let my game create a new autosave from that mission .... that one does not crashtaking a closer look at both files reveiled that the bad autosave (the one that does crash) for that mission contains 18 sections data more than my savegame
removing these 18 sections (from the previously bad autosave) and playing the game again prevents the crash
long story short ... ive found the area where the crash is causedproblem is that i dont know where that false code comes from as its not generated in my own autosave
possible explanation would be that i tried patching that mission a few days ago with a command that should in theory disable certain unused commands from previous missions
maybe thats the reason for it.... but i cant say for sure (and personally i doubt it)
Edit byyes - indeed
removing the changes ive done a few days ago also have lead to no other results so the source of the problem is still unknown
Edit by 2ok i noticed that the autosave writes data into the file while the mission is played
dunno why it does it that way as it would actually be more than enough writing the date into it from the point of time that where the ship position is stored
well... a few things i simply dont have to understand (the miracles of digital anvil)
I can not prevent that the autosave stores useless crap but i found out that it created a conflict between 2 objects of 2 different missions this way (a conflict which under normal conditions would never occour)
this is meanwhile fixed and the previously crashing savegames are now working without any probs
problem solved, case closed -
Ahmen
Glad you found a solution for this! -
Sincere Thanks to Swat_OP-R8R & CF Team - the update patch did the trick on the old Win XP game machine!!
Another great weekend of Blazin' new trails in CF space. Crossfire is 2nd to none! -
In last vanilla mission (going to dyson sphere) I encountered problem with trigger to continue mission
right when "jumping" from outer dyson sphere to the "inner" one.I got a little graphical bug while passing through the wall, then I reached the nomad city however there
were no generators to destroy nor surrounding facilities (looking as in MP or Open SP system). Mission
objectives were not updated and I was just hanging in the zone.I passed the point by reloading several times previous save.
Attaching my complete save file in case you can reproduce the "bug".
-
Maybe just a bug from my PC... Just mentioning it for records in case other players may encounter same thing.
