Ok, this is a weird one that might already be known, I'm not sure. I've been working on a 2 person vehicle, one person drives and uses the left mouse button to fire a fixed forward weapon and the other operates a mouselook aimed turret also fired by their left mouse button. This all works fine except for the turret doing barrel rolls as it rotates to match the gunner's rotation but that's another story entirely... Anyway, it all works fine for the driver in and out of mouselook as long as the gunner's seat is empty. However, if there's someone sitting in the gunner's seat and the driver goes into mouselook and holds down their left mouse button a control event is triggered as expected but instead of a series of additional control events firing as the button is held down, only 1 additional control event fires which indicates the button has been released. Only, of course, it hasn't. Here's what the debug output from the control event looks like:
Key2Name: Talon Brown level: 1073741824 edge: 1073741824
Key2Name: Talon Brown level: 0 edge: 1073741824
As you can see the id is right, I am the driver and the initial event is right, but for the life of me I cannot figure out why the next event, which should indicate I'm holding down the button, instead indicates I've released the button when I haven't. This only happens with the driver's script in the root prim, the control script in the gunner's seat works in the exact same manner...only it works properly in and out of mouselook when the driver's seat is also occupied. Now, I could just ignore this, after all driving in mouselook is optional and the weapon control works fine otherwise, but that this is happening at all keeps chewing at me because there's no logical reason for it. So has anyone else encountered anything like this before?
ETA: I guess the answer to my question is "no." Thanks for reading anyway.