Unit Possession crash

[Maelstrom]

Was playing a game with a team mate, sharing a comm. I build a unit to go attack with, and we both accidentally possess the unit at the same time. Spring then crashes. I tried again with another map, and a different person, with me hosting this time, and it crashed again.

[munch]

Was playing a game with a team mate, sharing a comm. I build a unit to go attack with, and we both accidentally possess the unit at the same time. Spring then crashes. I tried again with another map, and a different person, with me hosting this time, and it crashed again.

Just to clarify, when you say "possess" do you mean "select"? Were you both on a LAN or playing over the internet? I'm guessing that there's a race condition here somewhere.

Munch

[Maelstrom]

Sorry, I mean the FPS mode. Where you go in and control the unit. Its called Possessing in the wiki, so thats what I called it.

I was playing a game with someone sharing a comm with me. He went in the FPS mode on a tank to have a drive round. Just to see what happened, I jumped in the tank FPS mode as well. Spring crashed.

Playing online game, XTA, Core, possessed a lvl1 tank.
Ive also had it happen with a Core lvl1 kbot and an Immolator.

Just a boolean in the units variables, CurrentlyPossessed or something, that stops people from taking control of a unit if its currently being driven.

[munch]

Ah OK now I know what you mean. I don't think a boolean flag will solve it (though it will help) unless you have a single central flag on the server - you'll get a race condition: if you both try to jump in at the same time on your separate machines, they'll both send each other messages saying that you've jumped in and that the flag needs setting, and you'll end up with the same problem. Still it's far less likely to happen since you'd have to press C at exactly the same time to make it happen.

Cheers

Munch