v2.0.1 - many more bugs

[Bulva]

EDIT:

1) broken "Prop Locks" simulation - described here: 

 

2) using the "xscenery / mu2b60 / lift_power_levers" button works very badly - a little longer pressing the button causes the throttle levers to go crazy. In Ch.Cole's lua script, this worked very well.

3) Taxi lights cannot be turned off at all now

 

4) When using Bravo, there is no visualization of the PROP 1 and 2 lever jump (when switching to the TAXI position). Works OK without hardware.

 

I am not checking more for now, because the plane is currently unsuitable for pleasant flights.
I became a beta tester again for my own money  ;-)

Until the bugs are truly fixed, it may be wise to roll back to 2.0.0

 

 

Edited July 26, 2022 by Bulva

[Kimo]

Landing lights work fine put to the RET position to retract. 

[Bulva]

7 minutes ago, Kimo said:

Landing lights work fine put to the RET position to retract. 

... but why is one hidden and the other not? ;-)

[tkyler]

33 minutes ago, Bulva said:

setting the "Hardware Power Detent Ratio" parameter in GUI Preferences when using axes 3 and 4 do not give anything 

When using the hardware power detent ratio, then the bullet item below, given in the instructions given in my docs.  Your screenshot clearly shows that yours IS checked....which supercedes / ignores the Power lever detent ratio.  Previously I had "hid" certain options based on what users selected to try and avoid this confusion,  but a "dynamically changing GUI screen" really put off some people as confusing so I kept it in.  Its always a compromise between customer prefs.

• In the GUI prefs, make sure the option Auto-stop power levers at detent is UNCHECKED.  

 

The MU2 throttle behavior is very unique and requires a careful set of configuration options to be set, in order to accomodate all the hardware configurations people may want to use.  As I just mentioned, above, you're configurations are not correct for the way you want to operate your hardware and when this happens, the levers get conflicting signals and input and yes, could probably go haywire.  

Quote

... but why is one hidden and the other not? ;-)

No clue.  Not enough information from just that screenshot on how you ended up there.... they work great on my end.  You flip both to EXT, then one back to RET, then both to OFF...that will result in what your screenshot shows...and is correct.  I have NO clue what you're doing leading up to that screenshot.  But that config IS possible depending on how you manipulate your switches.

 

I will continue to refine the docs as much as is required to be more clear and folks understand the setup options

 

 

Edited July 25, 2022 by tkyler

[tkyler]

FYI, this is typical...many times, all I have to go on.  Notice it doesn't say what happens when you move from RET to OFF?  So the behavior is unknown unless you test it on a real MU2...which is not as easy as it seems sometimes.  Many owners don't respond to requests for you to "go play with all their switches" and so you  have to do the best you can.  In this case, I surmized the behavior and programmed it in.  Maybe it'll be different when this owner lets me play with his switches tomorrow.

 

[Bulva]

Thank you very much for your additional explanations. Of course, I have studied the manual several times, but I am still doing something wrong or there is a mistake.
What am I doing:
As I wrote - I use Honeycomb Bravo (1,2 throttle axes; 3,4 prop axes; 5 nothing; 6 flaps)

I assigned throttle # 3 for the left engine and throttle # 4 for the right one.
I would like to use the "Auto-stop power levers at detent" option, so I marked it in GUI Preferences.
Should the "Manips with Hardware" option be checked or unchecked in my case? (I tried both selections, which makes no difference).

When I was using the lua by Ch.Cole script, after pressing the assigned button ("Lifts the power levers"), the throttle value always remained the same no matter how long the "Lifts the power levers" button was held. Now it is so that the longer I hold down the "lifts both power levers" button, the throttle moves down by itself.
Sorry for my English if it's gibberish ;-)

What about the PROP LOCKS issue ??? 

 

 

[manguras]

57 minutes ago, Bulva said:

)

1) broken "Prop Locks" simulation - described here: 

 

2) using the "xscenery / mu2b60 / lift_power_levers" button works very badly - a little longer pressing the button causes the throttle levers to go crazy. In Ch.Cole's lua script, this worked very well.

3) setting the "Hardware Power Detent Ratio" parameter in GUI Preferences when using axes 3 and 4 do not give anything 

4) Taxi lights cannot be turned off at all now
5) landing lights logic totally broken:

 

 

 

 

6) When using Bravo, there is no visualization of the PROP 1 and 2 lever jump (when switching to the TAXI position). Works OK without hardware.

 

I am not checking more for now, because the plane is currently unsuitable for pleasant flights.
I became a beta tester again for my own money  ;-)

Until the bugs are truly fixed, it may be wise to roll back to 2.0.0

 

 

Landing light work fine for me.

Taxi lights totally broken.. for me also.

Cannot steering anymore...

[tkyler]

27 minutes ago, Bulva said:

What about the PROP LOCKS issue ??? 

That behavior assumes the correct hardware setup, so we'll start there and hopefully the prop locks will fall into line after.

Quote

 assigned throttle # 3 for the left engine and throttle # 4 for the right one.
I would like to use the "Auto-stop power levers at detent" option, so I marked it in GUI Preferences.
Should the "Manips with Hardware" option be checked or unchecked in my case? (I tried both selections, which makes no difference).

For dual lever "auto-stop at detent" behavior ..and I know you've set some of this up already from above...but just to make sure we're on the same page.....

1)  Assign power levers to throttles 3/4, not 1/2.  Makes sure you have no response curves assigned to the power levers. Delete them if you had them previously.

2) Assign the prop levers to Props 1/2, not 3/4.  Set a response curve for the prop levers to the values shown here (in  the CONDITION LEVER section)

3) Check the box "auto stop power levers at detent".   (FYI, the "detent ratio" value is ignored if this box is checked, so does not matter whats in it)

4) Use the "lift power levers" command to lift the power levers.

5) Use the new "EMER" commands to move the prop levers to EMER.  Note that the prop/condition leveres must be near the TAXI position for this command to do its job and move the levers to EMER STOP.

 

Quote

When I was using the lua by Ch.Cole script, after pressing the assigned button ("Lifts the power levers"), the throttle value always remained the same no matter how long the "Lifts the power levers" button was held. Now it is so that the longer I hold down the "lifts both power levers" button, the throttle moves down by itself.

The behavior is as intended (assuming youre power lever is in the BETA region at the time you hit the command.  There IS a bit of a paradigm question here as to what kind of behavior is desired.  For example, one option is to "lift power levers" and if your hardware lever is in the BETA region, then you have to move your hardware to go "recapture" at flight idle before you can move the levers into reverse...and thd other option (which I implemented) says, "if you move your lever into reverse...and then use the "lift power levers" command, then the power levers move to where your hardware is..which is in reverse, so they do animate down to meet your hardware position.  I can see how this may have some fans on one side, but not the other.  Puting yet ANOTHER hardware option in....I'll have to think on how my trouble that would be without breaking someone elses' preference.

-TomK
 

Edited July 25, 2022 by tkyler

[tkyler]

A bit of words I hope may be encouraging.  The fact that I'm at Oshkosh isn't helpful atm I know.  Once back though, I will be taking all these inputs and quickly implementing them.  If it takes a few rounds to iron out the bugs, it still should not take too long.  There are many differing preferences with regards to users hardware and getting them all accomodating without breaking each others preference and still fighting with X-Plane is a challenge and requires careful approach.  But I will get there and it will be swiftly and quickly.  I can't help but notice that a good 85% of users issues here with Version 2.0.1 is related to harware....no surprise considering the magnitude of the change. The MU2 quadrant operation is critical to a smooth simulation and until that's right for everybody, I agree the operation will feel clunky.

-TomK

[Bulva]

21 minutes ago, tkyler said:

That behavior assumes the correct hardware setup, so we'll start there and hopefully the prop locks will fall into line after.

Believe me, I do everything like this from the beginning.
So hence my surprise that something is not as it should be.
Now I have noticed another ailment:
if I use the command: "lifts left power lever" or "lifts right power lever" then my throttle levers behave correctly - ie they do not go crazy when the button is held down longer.
If I use the "ifts both power lever" command then my throttle levers go crazy. ;-)
I have never had problems with PROPs axles.
Except that now (in v2.0.1) I do not have the PROP lever raising animation when switching to TAXI mode (when I disconnect the Honeycomb Bravo and use F3 and F4 on the keyboard, the animation of lifting the lever is visible ).

And still, after starting the engines, I always have the shaft speed right away ... PROP LOCKS does not work for me ... ;-)

 

PS when the computer is turned on again, the landing lights are working properly.

Edited July 25, 2022 by Bulva

[tkyler]

I can't speak to all of these atm Bulva, with my being away from my development computer this week. I'm sorry you're seeing the issues you're seeing atm.  And for the record, what is "go crazy"?   spinning round and round forever is one form of crazy....moving and stopping somewhere you didn't expect is another form of crazy etc, but an accurate description of each helps us a bit further down the road.

Is anyone else seeing improper prop-lock behavior after a cold and dark start?  (not overspeed governing, that is a known bug for 2.01)

-TomK

 

Edited July 25, 2022 by tkyler

[Bulva]

In the attachment there is a short video showing what I mean, that throttles go crazy when I use the command "lifts both power levers": ;-)

 

xsMU2B60_4B_GNS - 2022-07-26 00.17.37.zip

[demontraitor]

I have got the Power Levers, and Condition Levers working on the BRAVO, using the Emergency Stop/Taxi commands in the detent (Press and Release events) etc.

The only problem I have now, using Throttle 3/4 in the settings, is that my Bravo power levers are at about 50% when the Power Levers reach Ground Idle. Not a major problem, just a brain ache. Then I am using the "xscenery/mu2b60/lift_power_levers" on the Reverser Levers but this is thrown the Power levers into reverse... I was expecting it to just allow me to move my Bravo levers into the Ground Idle and beyond zone....

Demon

[Bulva]

... you can check my temporary solution:

https://forums.x-pilot.com/forums/topic/24929-my-temporarily-solution-for-the-throtlle-axle-honeycomb-bravo/#comment-182612

 

[Marcodu68]

Hello,

• The power levers problem is solved : Good news ! It is really more comfortable and progressive.
• The engine sound when they are turning off is a little bit more realistic

But after two flight with this new version I noticed some old and not solved problems :

• It is always impossible to use the nose wheel chocks on parking if we want to be able to turn on the taxiways during taxi (I thought it was easy to solve)
• When the passenger cabin is lighted during a night flight, it is completely dark with the outside views.
• The three markers (white, red and blue) are not at their correct place : they are placed on the speed indicator (see picture joined)

Sometimes I have the impression to fly with a beta version, don't you ?

Marc