Vehicle controls not clickable until physically moved in edit mode?

[Icon Allen]

Hello first time posting here,

I have a unique problem that I can't get my head around and I have no clue if this is just a thing or if a piece of script is doing this(which I doubt but could be wrong.)

I have an aircraft that I built from scratch and all the controls in the cockpit are clickable from mouse look. But immediately after rezzing, if I hop in and start moving...... I can't click any of the controls. I stop moving... I CAN click on everything. It's not until I go into edit mode and physically move the aircraft myself that this issue stops. After I do that I can the click on things as the aircraft is moving. 

Also, crossing a sim border seems to have the same effect as "edit moving" the aircraft. Not clickable before crossing....clickable after crossing. To note, it's not just in mouse look. Even if I cam in on the controls that same phenomena happens. And yes the aircraft is physical.

Has anyone come across this or am I the only one seeing the black cat twice?

[Wulfie Reanimator]

Could you show the script that handles the controls?

[animats]

14 hours ago, Icon Allen said:

all the controls in the cockpit are clickable from mouse look.

Is this a problem with getting a touch event, or reading cursor position after the touch event?

There's a known bug in that area related to reading the cursor position while in mouselook. Kelly Shergood discovered it. Her aircraft have realistic controls which you touch and drag.

[Icon Allen]

I'm pretty sure this is the issue but it's not constrained to Mouslook. Even if I regular cam in while the vehicle is moving slow, I still cant click on anything untill I either stop, edit move the vehicle, or cross sims.

changed(integer change)
    {
        if (change & CHANGED_LINK)
        {
            agent = llAvatarOnSitTarget(); 
            if (agent == llGetOwner())
            {
                llRequestPermissions(agent, PERMISSION_TAKE_CONTROLS | PERMISSION_TRIGGER_ANIMATION | PERMISSION_CONTROL_CAMERA);
            }

run_time_permissions(integer perm)
    {
        if (perm) 
        {
            llStopAnimation("sit");
            llStartAnimation(sit_anim);
            
            llClearCameraParams();
            llSetCameraParams([
                                CAMERA_ACTIVE, 1, // 1 is active, 0 is inactive
                                CAMERA_BEHINDNESS_ANGLE, 0.0, // (0 to 180) degrees
                                CAMERA_BEHINDNESS_LAG, 0.0, // (0 to 3) seconds
                                CAMERA_DISTANCE, 3.0, // ( 0.5 to 10) meters
                                //CAMERA_FOCUS, <0,0,5>, // region relative position
                                CAMERA_FOCUS_LAG, 0.0 , // (0 to 3) seconds
                                CAMERA_FOCUS_LOCKED, FALSE, // (TRUE or FALSE)
                                CAMERA_FOCUS_THRESHOLD, 0.0, // (0 to 4) meters
                                CAMERA_PITCH, 7.0, // (-45 to 80) degrees
                                //CAMERA_POSITION, <0,0,0>, // region relative position
                                CAMERA_POSITION_LAG, 0.0, // (0 to 3) seconds
                                CAMERA_POSITION_LOCKED, FALSE, // (TRUE or FALSE)
                                CAMERA_POSITION_THRESHOLD, 0.0, // (0 to 4) meters
                                CAMERA_FOCUS_OFFSET, <1.0, -.6, 0.1> // <-10,-10,-10> to <10,10,10> meters was 2
                                ]);
            llTakeControls(CONTROL_FWD | CONTROL_BACK | CONTROL_RIGHT | CONTROL_LEFT | CONTROL_ROT_RIGHT | CONTROL_ROT_LEFT | CONTROL_UP | CONTROL_DOWN, TRUE,FALSE);
            //llWhisper(0,"You have ctrl");
        }
    }   

So as you can see I'm not grabbing mouse buttons for anything, but I'm glad i'm not the only one that had this issue. I wish there was a way to move the plane in script to "shake it out" of that issue but even that didn't work. There is something unique about edit moving it or crossing a border that fixes it.