Bulva

I mentioned it in passing in another thread, but I will remind you in a this thread so that the topic does not escape from the new update. If I am using the mouse to move the PROP lever then everything is OK - i.e. below the TAXI value, you hear a sound and you can see the lever go up. If I use the assigned PROP axes (to my Bravo), the levers only shift - i.e. they go below the TAXI value, but without the visual animation and the sound of lifting the lever. This is what it looks like when I use the mouse: MU2_PROP_mysz.avi ... and this is what it looks like when using Bravo: MU2_PROP_bravo.avi

It is not such a unique solution. If I remember correctly, the popular Saitek Pro Flight Throttle also has a button in the bottom position:

I don't have this problem in v2.0.1

I just wrote back in that thread. I think you understood that exactly. I also added a link to the video ...

I think you understood that exactly. Just in case, in this thread again, step by step I tried to accurately describe the behavior of my solution. I have also included a link to download a video that shows the MU2 throttle lever behavior with this solution:

So one by one (as long as it allows me to translate the google translator well ). I will describe it for one of the throttle Bravo axes (the other one behaves identically): 1) upper range: from 100% to 50% of throttle range - axis Bravo works normally for throttle Alpha range. 2) going down - to a value of about 50% (here my lua script checks if Bravo axes are between 47-53% of the power range by checking the parameter - "xscenery / mu2b60 / manips / L_power_lever_rotate" (lines 16 and 24 in lua script) 3) when I move the Bravo throttles down (without pressing the button) nothing happens -> the power remains at 50% - which prevents accidental entering the Beta range during the flight 4) when you are between 47-53% power ("xscenery / mu2b60 / manips / L_power_lever_rotate") and you press the "MU2_LIFT_BOOTH" button then: 4a) if you are outside the range of 47-53% - pressing and releasing the button and "MU2_LIFT_BOOTH" does not change anything 4b) when you are between 47 and 53% of power and press and release the "MU2_LIFT_BOOTH" button, then the lever is raised (dataref ("PULL_L", "xscenery / mu2b60 / manips / L_power_lever_pull", "writable") -> PULL_L = 0.013 - line 18 of lua script) and it will move to the Beta range (THR_L = 0.50 -- lines 19 and 27 in lua script). 5a) If you move the Bravo lever back up, you will return to the Alpha range again 5b) if you move the Bravo levers down, you will decrease the power in the Beta range. 6) in the Bravo profile (THROLTTLE 3 (4) AXIS RESPONSE CURVE)) there is a horizontal line between 40 and 50 set to a value of 49 to provide a margin of "inertia" when you move the Bravo lever. In other words, you have "more space" to effectively use the "MU2_LIFT_BOOTH" button. 7) on the left, extreme side of the THROLTTLE 3 (4) AXIS RESPONSE CURVE profile, I have set the minimum value to 10, it prevents entering the maximum reverse range. The value "10" is my individual setting, in which you smoothly (being in the Beta range) control the low power of the reverse, which is convenient during a taxi. 8) At the very bottom position of the Bravo lever there is a hidden switch (no. 9 and 10) that activates when you slide the Bravo levers all the way down. I assigned the command "MU2_REV_L" (and similarly MU2_REV_R) to this switch. When the Bravo throttle is still down (the button is still pressed), then the reverse thrust power increases continuously (if (THR_L> 0.0) then THR_L = THR_L - 0.002 ----> lines 47 and 58 in lua script), until the maximum reverse thrust is reached. 9) When you flip the Bravo levers back up (the button is released) and the power is controlled again the Bravo axis in the Beta range I'm sorry I can't describe it better. There are a few people who have tried my solution and are happy with it, so perhaps someone with a good command of English can do a better description of these steps. At this link there is a short video for download, that shows how the throttles MU2 behave with my solution: https://mega.nz/file/Q7pCwZIR#CDOniuNOnzDj7V0EHWF1yq756G0FAmWpWalIaI0APKg

The first time it happened to me, I thought it was a coincidence. But today I had this situation for the second time so I am signaling a problem. When I remove the props "manually", ie in the external view, by clicking on: intake covers and pitot covers, the speed meter no longer works (the pointer remains stationary at "0"). When removing props directly from the GUI window, the flight speed indicator was working normally.

Very small and small important detail , but it would be nice if it appeared - the sound of the opening cupboard (where the keys and headphones are). Since the opening and closing of drawers makes sounds, I thought that the sounds of opening / closing cupboard doors would be pleasing to the ear. I use this cupboard on every flight, but never use drawers

That's what I love VR for. I turn around and turn off the fuse

Sorry, I don't remember if there are any implemented commands for MU2: pitch_trim_wheel_nose_up and pitch_trim_wheel_nose_down. I'm not at the computer with XP now. I did it with dataref:: "xscenery / mu2b60 / manips / ap_pitch_trim_wheel" in the .lua script

I don't know if that's how it should work in real MU2, but now it looks like this: - to use the pitch_trim_wheel_nose up / down mode, you must have VS and ALT modes turned off (main switch AP - turned on) - when you press the VS button while climbing or descending, the VS "remembers" the current climb/descent angle setting. - when you press the ALT button, the plane will fly horizontally at the current altitude.

Of course, it would be great if the commands I had to "create" in the lua script could be accessed directly from within XP / MU2. In my solution it works like this: - Alpha range - it is about 50% of the range of lever movements (upper range) of Bravo - when you withdraw the lever below the Alpha point - the MU2 throttle remains at the lowest Alpha setting (no matter how far you withdraw the Bravo lever - this prevents you from accidentally entering the Beta range during the flight) - when you press the button (MU2_LIFT_BOOTH - I'm assigned to the button "Go Around"), then the throttle MU2 lever rises(pulled) and moves to the maximum BETA setting (THR_R and THR_L = 50) (but only when the Bravo lever is in the near position of the Beta range - "if (THR_L <0.53) and (THR_L> 0.47) then ....") - when you continue to move the Bravo lever down, you smoothly move from Beta to REVERSE. For my own use (because I prefer it ) ) I made that the Bravo axis you can use a small reverse string value (THR_L and THR_R = 10), which allows a safe range power during a taxi. - I get the full Reverse by moving the Bravo levers completely back, where the button to which I assigned the commands: MU2_REV_L and MU2_REV_R is used This solution also allows any individual descent from Alpha to Beta (and REV) for each engine separately. (which may be needed, for example, when one engine fires ;-)). Moreover, as I wrote earlier, it also improves the behavior that after starting the engines (from the C&D state) the "LOCKS PROP" locks remain blocked (although after starting the ENG Torque 1 and 2 indicators show RPM - this is not correct). To release the Prop Lock, the Throttle levers must be moved to the Reverse range.

Please take a look at my current solution with Bravo: I have been using this configuration for a week and I am very happy with this solution. I would not like the new version of MU2 to prevent me from using this solution. ;-)

Find the dataref: sim / operation / override / override_wheel_steer and set to "0" I did a simple command in a .lua script, (until an official fix appears).

http://www.togasim.com/mu2docs/setup/hardware_setup.html

As in Title: By the way, I will ask: should the ENG START buttons not glow orange? (in full sun would be more visible in VR):

... you can check my temporary solution:

... you can check my temporary solution:

... 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

... you can check my temporary solution:

Here is my temporary solution to keep Bravo correct (until the official version is out). 0) Download lua file: TB_MU2_TB_2_01.lua 1) put the lua script in the folder: ..: \ X-Plane 11 \ Resources \ plugins \ FlyWithLua \ Scripts \... 1a) Reload scripts FlyWithLua, or preferably start XP. 2) Assign the commands appropriately as I showed in the screenshot: 3) set the axis curves # 3 and # 4 as shown in the screenshot: Now after pressing button # 14 (originally TOGA), when you are close to the beta range, the Throttle axis will raise and move down slightly (no matter how long you press the button) In positions # 9 and # 10 (i.e. when you move the levers to the bottom button in your Bravo) - then the maximum Reverses will turn on. (You can now (with the press of a button) move any throttle to the Beta and REV ranges) In GUI Performance, check the option: "Auto-stop power levers at detent": It also improves the behavior that after starting the engines (from the C&D state) the "LOCKS PROP" locks remain blocked (although after starting the ENG Torque 1 and 2 indicators show RPM - and I do not know if this is correct). To release the Prop Lock, the Throttle levers must be moved to the Reverse range.

In my opinion, the command "lift both" is broken. The commands "lift left" and "lift right" work fine. We need this behavior for the "lift both" command ;-)

I checked it out. After Chocks are released, the parameter "override_wheel_steer" still remains at "1". So that's why the nosewheel remains dead. For the time being, I did the trick with a simple lua script that sets "override_wheel_steer" to "0" when removing chocks. ;-)

I loved MU2 from the very first time ;-) And I will be patiently waiting for further development ...