Bulva

Thank you very much for clarifying this issue. The support and help is just as great as the whole MU2 plane Thx

1) Should these lights come on when the GPU is plugged in even though the Battery is in the OFF position (key not even inserted) ??? The hands on the %TORQUE gauge come to life: 2) I am asking you to assign a command for GPU support (on / off), so that you do not have to expand the upper XP menu (I fly VR). A great plane. I haven't flown it for a long time, and now this love has revived PS. still no sound of opening/closing the locker (in which there is a key)

That's true. Both the MU2 and the IXEG B733 are perfectly optimized models for performance. They should be a model and example for other developers on how to create excellent, complex aircraft models with their advanced systems, while at the same time being FPS-friendly and smooth simulation. This was the case in XP11, and now I see that in XP12 as well. ;-)

Total surprise ;-) After all, it was still said that the first one to be completed would be the IXEG 733 ... ;-)

I don't know if this will help you as I haven't tried this solution. I use a knobster in VR. But in general, you can experiment with these entries in the B733_vrconfig.txt file Of course, make a copy of the original file before making changes ;-) :

I am very excited about the upcoming version of the B733. My only anxiety (apart from optimizing VR ), concerns all these "bells and whistles" for the eye. The IXEG 737 version for XP11 was largely a huge success due to the very good optimization and "playability" of this model. Despite the enormous sophistication of the simulated systems and flight model, and the beautiful cockpit graphics, the FPS in the IXEG were (and still are) unbeatable by any other aircraft of this caliber. I hope it won't be another plane in which we will admire flushing water in the toilet and opening luggage boxes at the expense of FPS

I'm afraid this will again be very inconvenient for VR users. And wouldn't it be possible to put all these functions in the iPad (as in other planes) ???

Everything is beautiful and wonderful, but .... .. what about VR users ??? Will the ground service windows, fuel, scales, etc. still only be available in 2D mode ??? I hope someone will dispel my fears, because although I love this plane very much, taking off the VR goggles several times completely kills the immersion. Anyway, there are probably no currently created planes that would not be "supported" by integrated tablets (also in VR, of course) ;-)

Yes, I checked my lua script. I had a problem with too datatref and using "writable ". Only with regard to this: "xscenery/mu2b60/manips/ap_pitch_trim_wheel" But the symptoms are similar. I gave up on "writable " and replaced it with "set" in lua as well.

Sorry to butt in and probably not help, but I remember having this type of problem some time ago as well. I don't remember the details anymore, but if I remember correctly, the problem was the incorrect assignment of commands to the hardware used - I use honeycomb alpha and bravo. This caused conflicts and resulted in similar "abnormal" AP behavior. Maybe this problem also applies to your situation ? [edit] ... it seems to me that the problem was with the: AP PITCH TRIM WHEEL and the commands assigned: xscenery/mu2b60/ap_pitch_wheel_nose_down xscenery/mu2b60/ap_pitch_wheel_nose_up (???)

I think (but I may be wrong) that it performs a similar function as well as a similar lever on the right. This one on the right blocks the PROP levers. So by analogy, I'm assuming that the one on the left is blocking the Throlle levers. ;-)

... please don't forget about VR support (ground menu support, loading etc)

Oh thank you very much. I haven't seen the ready command "Control wheel steering mode" before - I'm an idiot. I've been struggling with this for 2 hours - I tried with CWS A and CWS B, but they are completely different commands. I was already starting to sculpt with lua scripts. And also without success. Thanks again

Question as in the title. I would like to assign the TCS button to my button on the yoke.

The situation seems to be under control The lua script works and worked fine with the knobster encoder. My stupid mistake was with incorrectly assigning a command to the AP disconnect button - "Disco servos, yaw damp, and trim any side". This meant that once the trimmer was turned off, it would never be activated in AP mode again. Even after the flight is reset. Only restarting XP helped. Now I assigned the command "Disco servos, fit dir" and everything is probably OK.

And this is a fragment of the lua script that I tried to activate these commands with (for knobster encoder): The script works fine up to a point. Ie, I can start the ap pitch wheel nose down or up mode (in knobster encoder), but the autopilot then "is stupid" - does not align hight selected ALT SEL (AP mode switches from V/S to ALT, but the plane continues to ascend). I am sure you can execute these commands using a Knobster encoder, but I don't know how to do it ...

Thx. Of course, if I use predefined assignment in Yoke settings everything works fine: My problem is that I need to assign these commands to Knobster. When I assign the commands: "xscenery / mu2b60 / ap_pitch_wheel_nose_down" and "xscenery / mu2b60 / ap_pitch_wheel_nose_up" to a Knobster rotary encoder, it does not work.

Próbuję bezskutecznie używać tych dwóch poleceń, aby przypisać je do przycisków na moim własnym kontrolerze: ---- AP PITCH TRIM KOŁO ---- xscenery / mu2b60 / ap_pitch_wheel_nose_down xscenery / mu2b60 / ap_pitch_wheel_nose_up Próbowałem skryptu lua, ale też bez skutku. Co ja robię źle ???

Thank you. Is it possible to switch SAT to TAT in hardware, as it is in the "steam gauge" engine instrument version ???

I'm ashamed to admit, but I don't know where to find information about the OAT temperature ??? Of course there is TAT. I searched on FMC sites (like in 737-800) but can't see OAT ...

Exactly. IXEG733 has a problem (bug) with resetting the parameter: "sim / flightmodel2 / controls / speedbrake_ratio" even with the Speedbrake lever fully retracted. It is also very annoying when using the XPRealistic add-on - if onces you use the speedbrake, the cockpit will never stop shaking again ;-) My simple and tiny lua script eliminates this inconvenience: TB_IXEG_Speedbrake_off.zip I think it will also solve HeliMaf's problem

Everything I am writing is about the XP11 version. PS I checked several more times. Sometimes the Horn Cutoff button works correctly (usually on the ground), but more often its operation is ineffective (especially in flight)

4) It seems to me that the "Horn Cutoff" button does not work (the animation works, you can press it, but it does not silence the beep).

The problem as in the title: [EDIT] If you press any button on the top AP panel (ALT / HDG / NAV ... etc) before then the AP Pitch Trim knob does not turn on the AP. (Of course, AVION 1,2 is armed beforehand)