admroz

Perfect! Thank you!

Oh, so maybe one more feature request in opposite direction There were several requests from people on the forum to have instrument popups. I came up with a kludgy lua script which slightly but constantly changes display brightness which causes mini-EHSI to stay on. Would you be able to expose proper command to toggle mini-EHSI? Is it to much to ask if it could be a bit bigger? Thanks Adam

I got it!!!! In the yet another thread I found that I could try to remove Output/preferences/gizmo_prefs.txt file. I did it and it started to work! I could even click on Yes/No Flight Recovery buttons! Magic! It looks that when I initially clicked on "console" button in gizmo it somehow corrupted prefs file and then gizmo was unable to start. For your reference I'm attaching my corrupted and working gizmo_prefs files. It looks that gizmo doesn't like 4K or multimonitor setups. Adam gizmo_prefs_corrupted.txt gizmo_prefs_ok.txt

Yes, I did this, too. Before reinstalling TBM I removed gizmo from plugins folder. Then the TBM installer added gizmo to plugins folder, so I assume in current (proper) version. I've found in other threads that I should remove license_db and marker.1 files from X-Plane/X-Aviation folder, but unfortunately I don't have such files.

Goran, thank you for quick answer! I tried again as you suggested, but it doesn't help. I tried it already and even more, please read my original post (I know, it's long ). Currently the most suspicious is Gizmo as I observe the same behavior with other Gizmo aircraft - IXEG and LES Saab, XP just hangs after loading aircraft. Maybe there is a problem with file access rights? Tomorrow I should get new hard drive and I'm going to move my XP installation to D: drive, maybe it will solve this issue... Today I made quick test installing TBM as administrator, temporarily disabled antivirus, still not working. I'm out of ideas...

I've just bought TBM900, started with introduction tutorial, everything perfect. I was listening to the tutorial, moved mouse around, gizmo's sidebar appeard and from unknown reason I clicked on "console" button. Simulator hanged, I had to kill it and I cannot make TBM work again. I read some posts on this forum with similar issue but cannot find working solution. Here is what I did and what happens: After first restart I had "flight recovery" popup. I cannot click neither Yes nor No as XP simply hanged. I had to kill XP again. I read that it might be caused by multimonitor setup. I turned off my second monitor, run XP in fullscreen mode - the same happend. Cannot click. It just hangs! Then I read that it may have something to do with drivers, so I updated nvidia drivers, nothing changed. Still cannot run TBM. I uninstalled TBM, removed "Gizmo64.plugin" from plugins folder, removed "output/TBM900", run installer again. Still cannot run TBM, it hangs on load and what I can see is something like cockpit inside cockpit. I removed all plugins other than gizmo - no success. I tried other aircraft without gizmo - they work. I tried TBM without gizmo and surprise - of course it doesn't work, but it also does not hang simulator, I could click Yes/No on flight recovery popup and there are no glitches and even one instrument started up. I started to suspect that it is gizmo failure, not TBM. So I tried to start IXEG 733 and it also hangs XP! Now I cannot use any aircraft that runs on gizmo? Any ideas? Can I clean anything more to have fresh start with TBM? Kind of gizmo cache or something like that? Attached are my log files. Log.txt TBM900_Log.txt Thanks! Adam

Not sure if it may be anyhow connected (in XP world everything is possible), but for sure you can hear loud bell sound if when you use AutoGate plugin, when the plane disconnects from the gate. I'm not sure what triggers that, maybe parkbrake off. Does it happen on any airport? Can you try to disable AutoGate or try airport which does not have it?

Hello Captains! On behalf of GreenArcStudios team it is my great pleasure to announce that the WebFMC Pro has been released and from day one it supports our beloved IXEG 737-300. With the WebFMC plugin you can access the FMC/CDU from any PC or mobile device in your local network - all you need is a web browser! You can already try out WebFMC Free with Zibo Mod 738 and 739 Ultimate. For more details please visit our web page: www.greenarcstudios.com Check it out!

@737NUT You need to move camera to hide mini-EHSI if the toggle is "off". This is how the mini-EHSI is implemented by IXEG. The idea of my script is just a simple trick to prevent default hiding.

Great idea for my next script! Regarding instrument popups - I see your point, but we have to agree to disagree. Thanks anyway! Adam

C'mon Jan, just give us some hope, I'm sure you can do it before the end of a week!

I'm happy that you like it! It would be perfect if IXEG would add their own command to show/hide mini-EHSI (as it is, we will as for dragging and resizing later ). I'm pretty sure that it is easly doable with probably few "if" statements in the code. My script is just a quick workaround, it constanty and slightly changes the display brightness which triggers the popup. It may have performance impact (however, I didn't observe any). I don't get immersion killing argument for pop-ups. No one is forced to use such feature. I would love to have FMC popup (much more than ND and PFD). We have an idea for external and platform independend FMC (plugin) for IXEG, but it is currently at proof of concept state. Not sure if it will ever materialize. Adam

mini-EHSI popup for IXEG 737 View File This script adds command that toggles IXEG 737 mini-EHSI display: FlyWithLua/ixeg/mini_ehsi_toggle and menu entry to do the same: Plugins > FlyWithLua > FlyWithLua Macros > [IXEG] mini-EHSI toggle Requirements: IXEG 737 FlyWithLua plugin Installation: copy the script to X-Plane 11/Resources/plugins/FlyWithLua/Scripts folder Here is how it works: https://youtu.be/WN9ytrRANj4 https://youtu.be/gSq_X6q3L70 Submitter admroz Submitted 01/12/2018 Category Plugins and Utilities

It looks that I've found a solution to permanently show (and hide) mini-EHSI pop-up window. For me personally it will be very useful when going through LEGS page while planning a flight. Take a look how it works. Here is the script - have fun!

Is anyone willing to create polish government livery (fictional, because it's BBJ2/738 IRL)?

It looks that Jumping to Texas is quite common since E46 is the third on the list of most busiests airports in XP11 https://developer.x-plane.com/2017/11/x-plane-11-airport-usage-data/

I think that mapping keyboard for these dials is the best solution. I have mapped F1/F2 for SPD (sim/autopilot/airspeed_down / *_up), F3/F4 for HDG and F5/F6 for ALT. Works perfect for accurate adjustments and since it uses sim/autopilot/* commands it works with other aircraft too.

This is problably the least important issue you can imagine, but I'm just curious if this is intended behavior of 733, as it differs from NGs When performing window heat PWR TEST, the only way to turn off 'overtheat' lights is to recycle each window heat switch or to be precise going from ON to OFF state. Furthermore, the up position of this switch has no label, shouldn't it be "OVHT"?

You're right, I enabled "Remove flying surfaces when over speed" (disabled by default? I don't know...) and really bad things happened It seems to be not possible to overspeed flaps in VNAV in such scenario (which is good). During CLB there is SPD REST in FMC for flaps and it keeps the limit. Then in CRZ the plane accelerates in FMC SPD mode up to "red tape" and then switches to MCP SPD and slows down, then again FMC SPD, etc.

I was flying BADSO 07 ILS apprach at EDDS and FMC calculated curly path (looks a bit like curly brackets ) Unfortunately, it was not only depicted on ND, but as you can see on next screen the plane was perfectly following this path. In some other cases I've noticed loops in the plan (for loops issue I've alredy opened a ticket).

First and foremost, the problem was caused by my mistake. I forgot to retract flaps and in CRZ the plane started to switch between FMC SPD and MCP SPD (probably caused by flaps speed limits). The problem is that while in MCP SPD mode it shows really huge speed value. I am also not sure what should be the proper plane reaction for such a pilot error.