Hi:

Think I've found 2 possible bugs:

-Using the 2D pop-up autopilot controls, you can see the selected modes are illuminated.  However, the VC lights are off.

-I have the "Air Brake" mapped to a button on my control stick.  When the air brake is "opened", you can see the light is illuminated in the VC, but the handle has not moved.

Thank you.

  

1 hour ago, Dreamflight767 said:

Hi:

Think I've found 2 possible bugs:

-Using the 2D pop-up autopilot controls, you can see the selected modes are illuminated.  However, the VC lights are off.

-I have the "Air Brake" mapped to a button on my control stick.  When the air brake is "opened", you can see the light is illuminated in the VC, but the handle has not moved.

Thank you.

 

 

Aaron,

I can't reproduce either one of those 'possible bugs' in either P3Dv4.5HF3 or P3Dv5HF1 using Falcon50 v2.0b.  What sim are you using, and what assignments are you using for the airbrakes? I assume you are using the mouse for the AP buttons test.

As a quick experiment, suggest you try loading the default F-35 first, then switch to the Falcon50 to see if it makes any difference. Selecting the 'simple' default F-35 first before using a complex a/c like the Falcon50 seems to help with initiating sim variables.

I also noticed in the pictures above  engine N2 values are about 0%, but you are showing a couple hundred pounds/hr of fuel flow and N1 values that look to be at about 32% or so as best as I can see. So something is not right it seems to me.

Al

 

Edited June 6, 20205 yr by ark

50 minutes ago, ark said:

Aaron,

I can't reproduce either one of those 'possible bugs' in either P3Dv4.5HF3 or P3Dv5HF1 using Falcon50 v2.0b.  What sim are you using, and what assignments are you using for the airbrakes? I assume you are using the mouse for the AP buttons test.

As a quick experiment, suggest you try loading the default F-35 first, then switch to the Falcon50 to see if it makes any difference. Selecting the 'simple' default F-35 first before using a complex a/c like the Falcon50 seems to help with initiating sim variables.

Al

 

Thanks.  I was able to fix the autopilot issue with a fresh download but NOT able to fix the air brake.

I'm using P3Dv4.5 HF3.  My joystick is x52 and I'm using this button.  I'm able to use that button successfully as a spoiler/air brake assignment with other payware airplanes.

Thanks!

9 minutes ago, Dreamflight767 said:

Thanks.  I was able to fix the autopilot issue with a fresh download but NOT able to fix the air brake.

I'm using P3Dv4.5 HF3.  My joystick is x52 and I'm using this button.  I'm able to use that button successfully as a spoiler/air brake assignment with other payware airplanes.

Thanks!

What have you assigned that joystick button to? In the Falcon50 manual it says:

"G1000_MFD_SOFTKEY1" = SPOILER / AIRBRAKE EXTEND
"G1000_MFD_SOFTKEY2" = SPOILER / AIRBRAKE RETRACT

Note the airbrake lever has 3 positions, so it is not a simple toggle on - toggle off operation for a single button.

Al

Edited June 6, 20205 yr by ark

5 minutes ago, ark said:

What have you assigned that joystick button to? In the Falcon50 manual it says:

"G1000_MFD_SOFTKEY1" = SPOILER / AIRBRAKE EXTEND
"G1000_MFD_SOFTKEY2" = SPOILER / AIRBRAKE RETRACT

Note the airbrake lever has 3 positions, so it is not a simple toggle on - toggle off operation for a single button.

Al

I just used the button assignment w/ in P3D under the x52 button assignment.  Spoiler "On/Off".

The button works.  When I press it, the spoilers fully deploy and the light comes on but the lever just does not move.

1 minute ago, Dreamflight767 said:

I just used the button assignment w/ in P3D under the x52 button assignment.  Spoiler "On/Off".

The button works.  When I press it, the spoilers fully deploy and the light comes on but the lever just does not move.

But the airbrakes have two ON positions -- partially extended and fully extended, and so FSW has coded them accordingly. The 'standard' FSX/P3D on/off coding will not work correctly.

Al

35 minutes ago, ark said:

I just used the button assignment w/ in P3D under the x52 button assignment.  Spoiler "On/Off".

Suggest you assign a joystick button to Airbrake Extend (G1000_MFD_SOFTKEY1). Then the 1st button push will move the airbrakes to their partial on position, the 2nd push of the button will fully deploy the airbrakes.

Likewise, assign a different joystick button to Airbrake Retract (G1000_MFD_SOFTKEY2). Then each push of that button will move the airbrakes from wherever position they are in back towards fully Off (two pushes to go from fully deployed to fully off).

Or, if you prefer, you can operate the airbrake lever with the mouse (2 right clicks to fully deploy the airbrakes, 2 left clicks to fully retract the airbrakes from fully deployed, or you can use the mouse wheel to move the lever).

Al

Edited June 7, 20205 yr by ark

42 minutes ago, ark said:

Suggest you assign a joystick button to Airbrake Extend (G1000_MFD_SOFTKEY1). Then the 1st button push will move the airbrakes to their partial on position, the 2nd push of the button will fully deploy the airbrakes.

Likewise, assign a different joystick button to Airbrake Retract (G1000_MFD_SOFTKEY2). Then each push of that button will move the airbrakes from wherever position they are in back towards fully Off (two pushes to go from fully deployed to fully off).

Or, if you prefer, you can operate the airbrake lever with the mouse (2 right clicks to fully deploy the airbrakes, 2 left clicks to fully retract the airbrakes from fully deployed, or you can use the mouse wheel to move the lever).

Al

Thanks.  I'll give that a try and report back.

9 minutes ago, Dreamflight767 said:

Thanks.  I'll give that a try and report back.

There is another option (although not a particularly good one) if you feel you are restricted to using a single joystick button (or key) for the airbrakes. We could write a Lua script that would cycle through the airbrake positions, one position at a time, with each button push: From fully retracted - to partially extended - to fully extended - back to partially extended, and then back to fully retracted, etc.  So,for example, worse case would be if the airbrakes had just been partially extended and you then wanted to fully retract them, you would have to push the button 3 times to cycle back to fully retracted.

Al

6 minutes ago, ark said:

There is another option (although not a particularly good one) if you feel you are restricted to using a single joystick button (or key) for the airbrakes. We could write a Lua script that would cycle through the airbrake positions, one position at a time, with each button push: From fully retracted - to partially extended - to fully extended - back to partially extended, and then back to fully retracted, etc.  So,for example, worse case would be if the airbrakes had just been partially extended and you then wanted to fully retract them, you would have to push the button 3 times to cycle back to fully retracted.

Al

So my only reservation about changing the button to G1000...is how it will effect other airplanes.

1 minute ago, Dreamflight767 said:

So my only reservation about changing the button to G1000...is how it will effect other airplanes.

Not sure what you mean here.

If you mean using two buttons with the two G1000_MFD_SOFTKEY assignments for airbrake deployment and retraction, if you make the assignments through FSUIPC you can make them aircraft specific using profiles so they would only apply to the Falcon50.

If you are talking about the Lua script, we would  not be using the G1000_MFD_SOFTKEY assignments.

Al

5 minutes ago, ark said:

Not sure what you mean here.

If you mean using two buttons with the two G1000_MFD_SOFTKEY assignments for airbrake deployment and retraction, if you make the assignments through FSUIPC you can make them aircraft specific using profiles so they would only apply to the Falcon50.

If you are talking about the Lua script, we would  not be using the G1000_MFD_SOFTKEY assignments.

Al

Yes, I mean button assignment.  I'll give it a go with that first and go from there.

Thanks Al!

Talk to you soon,

Aaron