MissionVarriables are not reset

Post by **Eric Walch** » Sun Aug 16, 2009 2:59 pm

When a player dies, the MissionVarriables are not reset. Only on loading a old game the variables are reset, but when going further with a new Jameson, it inherits all mission variables of the dead commander.

Svengali · Post by **Svengali** » Sun Aug 16, 2009 6:18 pm

Same on my machine - SVN2289

Post by **another_commander** » Sun Aug 16, 2009 6:52 pm

Guys, can you provide a way to reproduce? I loaded a commander, checked that missionVariables.nova is NOVA_HERO, then launched, did 180 and crashed back at the station. When the new Jameson was started, executing missionVariables.nova on the console came back with null, which is what I would expect for a new Jameson. This with latest trunk (2290).

Svengali · Post by **Svengali** » Sun Aug 16, 2009 7:14 pm

another_commander wrote:
Guys, can you provide a way to reproduce? I loaded a commander, checked that missionVariables.nova is NOVA_HERO, then launched, did 180 and crashed back at the station. When the new Jameson was started, executing missionVariables.nova on the console came back with null, which is what I would expect for a new Jameson. This with latest trunk (2290).

testreset.oxp (912Byte)

Post by **Eric Walch** » Sun Aug 16, 2009 7:42 pm

another_commander wrote:
Guys, can you provide a way to reproduce? I loaded a commander, checked that missionVariables.nova is NOVA_HERO, then launched, did 180 and crashed back at the station. When the new Jameson was started, executing missionVariables.nova on the console came back with null, which is what I would expect for a new Jameson. This with latest trunk (2290).

My mistake. I crashed myself and noticed some missionVariables had a value. But on second look I saved Jameson before launching and looked at their values. There were about 20 but all were proper starting values for missions. Nothing wrong. I have been sitting in the sun to long this weekend.

Svengali · Post by **Svengali** » Sun Aug 16, 2009 7:58 pm

Hihi, I think we've made the same mistake then :-) guiScreenChanged is fired before reset and when you set something there...

Edit: Changed the file above. It's not simple, but handles all 4 cases very well.

Frame · Post by **Frame** » Tue Aug 18, 2009 1:39 pm

a double classic number 50 then