Killstreak Camera Lock

[Phantom139]

Come of the killstreaks in the game will lock the camera when you take it over preventing you from moving the camera around. I've explored numerous fix possibilities in the past with none of them working, maybe someone else can figure this one out.

[Phantom139]

And just today I stumble upon this function...

I may be onto a fix for this issue, running some tests right now, but according to the client side of the game, the client is supposed to wait for the server to send a control update function to the client on turret instances, which is done via:

commandToClient(%client, 'ControlObjectResponse', true, getControlObjectType(%obj,%client.player));

I'm going to add this and a few other lines to the killstreak summon function and give it a go.

[Phantom139]

Nope.

[Ragora]

Generally just using %client.setControlObject(%camera) should be enough. I have no idea what that clientCmd above is, unless it's some TWM2 specific item you added but I can't see how that can relate to the problem you're seeing.

I would guess you're triggering problems with the key mapper (you have several maps and if you can trigger the client to use the wrong ones which causes behavior like this). You could verify this by triggering the bug and running moveforward(true) to see if you begin to move.

[Phantom139]

I'll give this a shot the next time I run the server.

As for the above command, it's present in serverCommandMap.cs in the serverCmd that is actually called by T2 when a player tries to control an object trough the commander map.

[Ragora]

It's not necessary for the controls to work. I'm not really sure what it actually does, but all that's ultimately necessary is just setControlObject. The game handles control mapping correctly if that's what you do.

Also, as a thing aside, it's been a while since I've had some T2 in my life. Is the test server ever online or?

[Phantom139]

Which is what makes this bug extremely odd, the original code from way back when I first introduced the Harbinger's Wrath killstreak only employed setControlObject, and sure enough it did the movement lock on the turret when you would take control. I've tried so many different things all with no luck or fixing of the bug.

As for the test server, I've been bringing it up a bit more as of recently and a more long term solution will come into play in about a month or two when my linux box finishes my research modelling work such that I can host Tribes 2 again.