Litjan

It is only on our aircraft - we are still working on making the VNAV work better with multiple altitude restrictions. Jan

Yes, thanks for sharing - I will see if I can find out what happens there... Jan

Hi Martheson, thank you very much for the work you did for the previous version! I know it has been a godsend for the VR users of our aircraft - in absence of us providing the necessary files ourselves. I will certainly look for your input and assistance down the road when tweaking the VRconfig.txt for this aircraft, and hopefully we can implement this in the very near future for everyone out of the box. Thanks again to you and Joe (and whoever helped make the previous version VR compatible), Jan

Scroll wheel is fixed for next patch - what about the speed brake? It comes up for me when I pull the lever "up", just like in the real plane? It also extends when I trigger the command "Speedbrake extend one" and it retracts when I trigger "Speedbrake retract one". Is this different for you? Cheers, Jan PS: Sorry for my ridiculous quality control and lame excuse on that!

Hi again, a (very) brief google search netted this: http://www.b737.org.uk/flightcontrols.htm Searching with google again, netted this: https://www.youtube.com/watch?v=AXr0PExNqBA Posted November 2014, I will help you with the math: ca. 5.5 years ago The purpose of this system is much the same as the new MCAS system - it was required for certification, because at high thrust levels you could get into the situation where the plane would slow down - but the nose won´t drop (fast enough), as the lessening elevator forces are not able to compensate the (more or less static) pitch up moment from thrust in underwing mounted engines. So they put in a system that "amplified" the natural pitch stability that you would want in any aircraft (plane gets faster -> nose goes up, plane gets slower -> nose goes down). You are not alone - it confused the heck out of many real pilots (that did not read and understand the book word for word). In the real plane you trim almost all the time - so the effect of this system would only really show when someone has poor piloting technique (prolonged flight with constant yoke input needed). Cheers, Jan

I think this would be a question you need to put to Laminar Research (X-Plane), not here. It looks like your new nav database is getting read by our FMS, but not by Laminar? Cheers, Jan

The question is rather - why did XPUIPC stop working with our plane? We didn´t change anything. Every cheap joystick can interact with our throttles, XPUIPC can´t (anymore). Cheers, Jan

Mmerelles is helping us put this into the plane for everyone. Right now we are clarifying with Laminar Research why the cockpit.obj file we exported from Blender chokes up the VRconfig.txt - there is one extra word in there ("none") that we need to support our new way to define our manipulators, but Laminar´s VR code does not handle it well (as you all found out). So while it is absolutely fine to enjoy what mmerelles is coming up with right now, we will try to solidify this with his help and then include it for everyone by default. Cheers, Jan

Found the bug and fixed it. Thanks again for reporting, Jan

You are seeing the left spoiler "float" a bit - this happens when there is no hydraulic pressue on system B and can happen on the real aircraft as well (the pressure holds the spoiler down). The graphics anomalies you see are mismatched UV maps - we have them on our list. The two graphic "issues" you circled in your last picture are scuff marks that are present in a lot of aircrafts - where the shoes of the pilots scratch up the plastic covers. Jan

Yeah, the real one isn´t backlit I think...so we didn´t make this one be backlit, either, it is just painted white. I agree its hard to see at night. Maybe we can make it a bit fluorescent at least. Cheers, jan

No, just checked, works fine, even from turnaround state. Checked EDDH runway 05. Set NAV 1 to 110,50 and it showed the ILS for 05 with indication. Tuned NAV 2 to 113.10 and it showed indication to HAM VOR. Cheers, Jan

Weird! Ok, I will do some checks myself from the turnaround state. Thanks, Jan

What was the FMS input? And how did you set the flaps (with a dedicated axis possibly?) Cheers, Jan

Yes - I see the problem on my computer as well - the computed N1 is correct, but autothrust does not set it... I will investigate! Thanks for the report, Jan

I understand that for testing/dev...and/or if you really know what you are doing...

You can also doublecheck if you have the option "turn downwind ILS off" enabled in X-Plane. If that is on, the ILS will be "switched off" if there is a tailwind on the runway... Cheers, Jan

Good morning Seamaster, while we have some VNAV problems, often the problem you report is due to the MCP altitude not being lowered prior to reaching the TOD. Once you are past the TOD the plane will switch to ALT HOLD and will not descend by itself anymore, even if the MCP altitude is lowered then. Cheers, Jan

Thanks for the report! Not sure about the takeoff config - it doesn´t sound for me. The thing most people forget is to set the trim, so it is not in the green band, which triggers the warning. Could you doublecheck if that is the problem? Cheers, Jan

Good to hear that. Yes, you will need electrical power for the navigational radios to work. Cheers, Jan

Hello Faisal, can you see the ILS on the X-Plane map (m key)? Can you click on it and choose "tune on Nav1"? Maybe you can load the plane at an airport with an ILS serving that runway you are on, then tuning it to NAV1 and then send me two screenshots (of the Nav Radio and the artificial horizon)? Thanks, Jan

Hi everyone, we are happy with the renewed interest in our beloved 737 and while we would of course prefer you to not have any problems with it - the next best thing is you reporting your problems so we can fix them and hopefully one day (unlikely!) get to the point of no one having any problems with it anymore . If you encounter what you think is a bug or observe a problem: 1.) Do a search in this website (IXEG section) to see if anyone else reported it and what the status on it is. We want to try and avoid having 27 threads of "oh, it looks like the mousewheel scroll direction is wrong, has anyone else seen this?" 2.) If you report a bug, it almost always pays to attach the LOG.txt file (found in your X-Plane main directory) to the post (attach, don´t copy the contents of it to create a wall-of-text). 3.) If you encounter a crash of X-Plane, the culprit is usually an incompatibility with a plugin or memory exhaustion (RAM or Lua). To troubleshoot, please remove all plugins except for the Plugin Admin and Gizmo, then try to run the IXEG 737. If that works, add your plugins back one by one or in batches to isolate the problematic plugin. Often you will find that this plugin has been updated and you can get a more recent and hopefully compatible version. Let us know - even if you succeeded, other users may benefit from your findings. 4.) The same applies if a weird bug or unexplainable behavior is exhibited by the IXEG 737. We need to rule out third-party interaction, so to troubleshoot, please remove all plugins except for the Plugin Admin and Gizmo, then try to run the IXEG 737. If that works, add your plugins back one by one or in batches to isolate the problematic plugin. Often you will find that this plugin has been updated and you can get a more recent and hopefully compatible version. Let us know - even if you succeeded, other users may benefit from your findings. Thanks for all your continued support to help us improve the IXEG 737. Jan

Oh, wow - I really don´t know what went wrong there... Initially you moved your controls (with the mouse) so the autopilot reverted to CWS pitch. I assume you tried to re-engage VNAV which did not work because probably your controls were still deflected. I have no idea why VNAV calculated these high speeds, though. I think I would like to add that some of the more serious problems we have seen are with users that fly with a mouse or trackball. I would even go as far as saying that if you are serious enough about flightsimulation to buy and fly the IXEG 737, you should really buy a joystick first before spending 75$ on an add-on aircraft like this one. Even if that means that no money is left for the IXEG 737 and we loose a sale . Cheers, Jan

Thanks for the report - both known - the flap will be fixed, for the seat we have to see how we can improve the "fuzzy" looking of the edges without killing framerate. Cheers, Jan