Litjan

Hi Mooze, we have had some similiar reports, and users "fixed" it by either running OpenGL (which hints it may be a problem with 11.50 beta) or by uninstalling Ultra Weather XP. If that doesn´t help, please follow this: Cheers, Jan

Hi 3rdwatch, thanks for the feedback - exactly the type of stuff we are looking for! And no worries about the Zibo, it is definitely the airplane we get compared to the most, if not only for the close likeness of the aircraft types modeled. I never installed the Zibo myself...just the same as P3D - I guess my idea of making a simulation experience is not trying to mimic or copy something else - but to fashion it after my experience as an airline pilot flying the aircraft. That does not mean that one can´t learn from other implementations and sometimes it is not necessary to reinvent the wheel . I will look at the buttons and switches you mentioned, sometimes it is as easy as adjusting the length of travel for some manipulators or increasing the "hitbox". Cheers, Jan

Thanks for the kind words! We are really sorry for this inconvenience...but as long as you stay away from manually manipulating any waypoints/fixes with those "forbidden" letters you should be fine for now... You can always "manually" make a company route and drop it into the "coroutes" folder, then load it from the RTE page. Just make a simple text file with an editor of your choice and change the filetype to .fpl. Here is an example routing: EDDF ANEKI Y163 HERBI Y164 OLBEN DIRECT MONIN W112 SOSON EDDH Cheers, Jan

Thank you for the report. The problem is known and fixed for the next patch (soon!). You can read all about it here:

Hello lionell88, the bug is known and will be fixed very soon. You can read about it here: I am not sure which field you are talking about, can you post a screenshot for me? Cheers, Jan

Do me a favour: When running with the latest XPUIPC version, open the Dataref Editor (plugins), search for XPUIPC and manually set the dataref ixeg/733/hardware_overrides to 1. Then try if you can move the thrust levers? Cheers, Jan

I will put it on the list of things to look at - I personally have no idea why it doesn´t work, but Tom may, he is into cockpit building and such... Cheers, Jan

Thanks for that report, SUAS! Ben is continuously working on Gizmo and it certainly is worth exploring the latest betas he posts! Not sure what is going on with your FlyWithLua - I run it on my installation (with the smartWinch script for soaring) and it seems to work flawless...however I don´t use SkyMaxx. Cheers, Jan

We kow that VNAV responese can become wrong. But your post shows me that you do not know how to fly the 737 in other modes. Please follow the tutorials on autopilot and autothrottle use and you will see that is totally wrong. needs some more explanation. Which airport, which approach? Can you provide a screenshot? We would like to see the case where the autopilot in LNAV is not following the magenta line, so we can fix it.

Can´t really say none taken. I fly the plane many hours daily (1.31) and the autopilot behaves completely predictable for me. VNAV is still not working as it should - we never said that it does. I don´t think it has become worse. I am all for freedom of speech, but getting on here and making unsubstantiated claims of "unflyable", "unpredictable", "terrible" etc. is borderline slander. If you can´t get things to work I am sorry for you - we are ready to help you if you provide details of what is going wrong - but if you just feel the need to vent, let of steam and rage, please take it elsewhere. Jan

When using the nosewheel there is an effect that is similar to a "stall" of a wing. The wheel will put out force corresponding to it´s "slippage" - until you pass the critical angle and it starts "gliding". This effect is real - try driving a car on ice or snow and see how gentle movements of the wheel help in keeping in control - once the car starts sliding, it is very hard to get it back under control. The problem in X-Plane is that the force put out by the wheel under a certain "slippage angle" is way too low. So people tend to naturally increase the steering angle to compensate, entering the range of free gliding (stall) where the actual angle becomes irrevalent. Try to use small movements, like jaguado points out. Try to steer smoothly and deliberately and control your speed to be less than 10kts in turns. I will keep pushing Laminar to make this more realistic. Cheers, Jan

This really surprised me - because there was no change to the VNAV calculation at all in 1.3 or 1.31. But hey, if you say so...

Yes, that is unfortunately happening - we will have a fix for this shortly. You can read about how it happened here: Cheers, Jan

I know, otherwise I would not have offered that

If you can post a picture of an in-service Lufthansa 737-300 with the yellow welcome panel on it - I will personally start making that livery for you. Cheers, Jan

I think so - because there is an option to get Navigraph data in the XP1100 format, which forces to have different names for the "same" STAR, if it serves multiple runways (and has a different lateral path for each one). Cheers, Jan

Unfortunately the quality of the video is too bad to really see what is going on. I can see the pitching moment, but can´t even guess why that happens. It looks like you are in VOR/LOC for the roll mode - you should not be in VNAV at that point at all. Cheers, Jan

You run the packs on HIGH when you need maximum cooling. On the ground with the APU feeding them, the HIGH setting gets an extra boost (ca. 20% more flow). The APU can´t be "overtaxed" - it will reduce the bleed automatically to stay within EGT limits. To start engines you will always turn both packs OFF - it is possible to run one pack and start, but it is not allowed. You need a minimum of 30psi pressure to start an engine. You can (we called it Sommerschaltung) close the Isolation Valve once the right engine is running and use that engine to power pack 2 - while starting engine one. The 737 is notoriously bad at cooling in the summer, so every extra second cooling flow helps. Cheers, Jan

Ok, that is the newest one. I would try (just to rule stuff out) to run with just the IXEG and SkyMaxx (no flywithlua, no xpjets, no Navigraph Simlink) to really see if it just this combination. Let us know how that goes? Cheers, Jan

Well, first we need to make sure that it really is SkyMaxx. We have not heard widespread reports of an incompatibility, so if it is only incompatible on YOUR computer, chances are that something else is up that is unique to your setup. It could be an interaction with FlyWithLua, for example, some script you are running, etc. Here is the support forum for SkyMaxxPro: https://forums.x-pilot.com/forums/forum/165-skymaxx-pro/ I can not see which version of SkyMaxx you are running (it just says 4) - maybe there was an update? Cheers, Jan

Well, then it looks like you have your candidate. Try to run a bit longer (like 30 minutes or so) to make sure it is stable. Cheers, Jan

When the battery drains to 0, the temperature indication of the APU becomes dead (stops at last value). The APU will shut down as well (like when you switch of the battery). The generator breakers need electricity to work - so with a totally depleted battery, you can not close the APU, GPU or engine generator breakers to connect them. In this case in real life the following things happen: 1.) The Captain that allowed the battery to drain gets chewed out. 2.) The maintenance brings a mobile battery or connects a cable to the DC external connector 3.) A GPU is connected and brought on-bus (now there is electrical DC power) to charge up the battery through the ground service bus. 4.) The APU can only be started once there is enough charge in the battery - it can not be started on GPU power, for example (too much current). In the IXEG case you can do three things: Either reload the aircraft or reboot gizmo - or use the "failures" window to recharge the battery. Cheers, Jan

That is correct. Unfortunately all waypoints that begin with "N" or "S" and end with "E" and "W" are going to cause this... unfortunate fallout from the "user created waypoint" addition. It will be fixed very soon. Workaround for now: Either avoid manually entering these points (automatically loading them in a STAR or SID is no problem), or make a route (without them), save it, then edit the .fpl (in coroutes folder) with a simple text editor to include them. Then you can load them via the "company route" function. Cheers, Jan

I downloaded your Log.txt and you are still running all those plugins. Here is the relevant section from your Log.txt: Fetching plugins for C:\X-Plane 11/Resources/plugins Loaded: C:\X-Plane 11/Resources/plugins/PluginAdmin/64/win.xpl (xpsdk.examples.pluginadmin). Loaded: C:\X-Plane 11/Resources/plugins/NavigraphSimlink_64.xpl (Navigraph Simlink for X-Plane). Loaded: C:\X-Plane 11/Resources/plugins/ASXPConnect/64/win.xpl (HiFi). Loaded: C:\X-Plane 11/Resources/plugins/AVS/64/win.xpl (ru.ffsts.airportvs). JARDesign 3D Sound Engine v310320 Loaded: C:\X-Plane 11/Resources/plugins/BSS/win.xpl (jardesign.sound3d). 2020-06-10 19:04:23 BetterPushback[xplane.c:539]: This is BetterPushback-v0.48 libacfutils-0e818a4 Loaded: C:\X-Plane 11/Resources/plugins/BetterPushback/64/win.xpl (skiselkov.BetterPushback). Loaded: C:\X-Plane 11/Resources/plugins/CEF/64/win.xpl (FlightFactor.CefLoader). FlyWithLua: Your system path is C:\X-Plane 11/ FlyWithLua: System Dir: C:\X-Plane 11/ FlyWithLua: Plugin Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua FlyWithLua: Plugin Scripts Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Scripts FlyWithLua: Plugin Internals Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Internals/ FlyWithLua: Plugin Modules Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Modules/ FlyWithLua: Plugin Scripts Quarantine Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Scripts (Quarantine)/ FlyWithLua: Plugin Version: 2.7.22 build Dec 9 2019 14:41:43 Loaded: C:\X-Plane 11/Resources/plugins/FlyWithLua/64/win.xpl (CarstenLynker.FlyWithLua.NG). G64: 0.000: Gizmo64 Script Engine v18.02.27.0200 Windows G64: 0.000: built: Feb 27 2018, 02:00:08 Loaded: C:\X-Plane 11/Resources/plugins/Gizmo64.plugin/64/win.xpl (gizmo.x-plugins.com). [REALVIEW INFO]: Starting X-Plane SASL plugin v3.2.7+0b9658f [Commercial Edition] [REALVIEW INFO]: RealView | Global | Start Full Loaded: C:\X-Plane 11/Resources/plugins/RealView/64/win.xpl (1-sim RealView). Loaded: C:\X-Plane 11/Resources/plugins/SilverLining/64/win.xpl (SilverLiningV4.Clouds). [SKUNKCRAFTS UPDATER INFO]: Starting X-Plane SASL plugin v3.6.5+8783e05 [Commercial Edition] [SKUNKCRAFTS UPDATER INFO]: SkunkCrafts Updater | Global | Start Full [SKUNKCRAFTS UPDATER INFO]: Loading cursors... Loaded: C:\X-Plane 11/Resources/plugins/SkunkCraftsUpdater/64/win.xpl (1-sim SkunkCrafts Updater). TGXP: Traffic Global V1.0.9113 TGXP: Unable to identify DataRef sim/graphics/view/using_modern_driver TGXP: 19 TCAS (multiplayer) aircraft enabled. TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/MisterX_Library/Earth nav data/apt.dat' doesn't exist, skipping. Loaded: C:\X-Plane 11/Resources/plugins/Traffic Global/win_x64/Traffic Global.xpl (jkcc.trafficglobal). WebFMC: Plugin version 1.5.3 WebFMC: WebFMC Pro starting up WebFMC: Expecting backend binary in "C:\X-Plane 11/Resources\plugins\WebFMC\webfmc-win.bin" TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/HD Forests/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: IO Thread run WebFMC: WebFMC started Loaded: C:\X-Plane 11/Resources/plugins/WebFMC/win_x64/WebFMC.xpl (com.greenarcstudios.webfmc). TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/Airport Environment HD/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\yOrtho4XP_Overlays/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: Server version 1.5.3 TGXP: Scenery path 'E:\Custom Scenery\Ortho_Washington_2017/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\z_ortho_New_England/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: WebFMC network address(es): 192.168.1.15:9090 TGXP: Scenery path 'E:\Custom Scenery\z_ortho_MidAtlantic/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\z_ortho_California_v5/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\Hawaii/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\Ortho_Oregon_2017/Earth nav data/apt.dat' doesn't exist, skipping. Loaded: C:\X-Plane 11/Resources/plugins/XSaitekProFlight/64/win.xpl (XPlane Plugin.1.2.6.0). [RealityXP.GTN][INFO ] [RealityXP.GTN][- ] # win.xpl version 2.5.25.0 Loaded: C:\X-Plane 11/Resources/plugins/rxpGTN/64/win.xpl (RealityXP.GTN). [XJet] Init properties. [XJet] Plugin path: C:\X-Plane 11\Resources\plugins\xjet [XJet] Props path:C:\X-Plane 11\Resources\plugins\xjet\jvmplugin.properties [XJet] Init JVM. [XJet] Plugin path: C:\X-Plane 11\Resources\plugins\xjet [XJet] Plugin started. Loaded: C:\X-Plane 11/Resources/plugins/xjet/64/win.xpl (com.airfoillabs.xjet). "Iffy" means "it is unsure IF they will run well with the IXEG737" - they are all great plugins and such, but people have reported compatibility problems before and often there are updates for those plugins that fix those - or the plugins are very old and made at a time when certain coding conventions were more "lax" and did not cause conflicts. So - if "unticking" the plugins in the disable menu doesn´t (seem) to work for you, you need to manually clear them out of your plugin folder (just move them somewhere else for now). Then run the 737 and see if it runs stable. If it does, move your plugins back into the plugin folder one by one. As soon as the 737 starts CTD again, remove the last plugin you added, start adding the remaining ones one by one. Once you have all plugins loaded that will let the 737 run with CTD please report which plugin is not compatible and we will see if we can do something about that. Cheers, Jan

Yep, it is noted and we will see how we can implement it. In the regular 3D cockpit we move the viewpoint (pilots head) slightly - obviously that doesn´t work in VR, so we need to figure out some other method. For now get your wife to shake your chair slightly when rolling down the runway . Cheers, Jan