Litjan

If you have windows...you do. Check your windows defender settings? Another possibility could be using X-Plane from an external drive, accessing the navdatabase can be slow, depending on how it is connected. Cheers, Jan

Hi Alax, for some odd reason our throttles don´t work with the newer version of XPUIPC, but they work with an older one (not sure which version, I don´t use it)... Cheers, Jan

Try downgrading to the latest stable version of Gizmo (18....) and let us know how it goes?

I specifically tried LSK on my system after reading you had problems with it - and it works fine here. So not sure what is going on with that...is anyone else having a problem with it? Cheers, Jan

And this is from your LOG.txt that you sent when everything wasn´t working... 0:00:00.000 G64: Gizmo64 Script Engine v20.05.29.0708 Windows 0:00:00.000 G64: built: May 29 2020, 07:09:33

Unlikely that those are newer. The 20.05.29 is TADA!!! from the 29th of May 2020. The latest installer was cut over a week ago.

Are you sure? As far as I know this is the very latest beta! Which version did you use that is newer than that one?

Glad to hear its working for you!

Nah, that is fine - happy that it works for you - and hopefully we can get the new Gizmo working for everyone, soon! Cheers, Jan

Yeah, that looks odd. Maybe it is JUST about missing that waypoint so it is turning back to make it? Try to put in a speed of 160 kts for VAXOB and see if that helps? Cheers, Jan

Try to follow this standard troubleshooting and reporting protocol - that way we can possible gain a bit more insight and help you. Cheers, Jan

This could be an OpenGL problem, then. Maybe try to disable other plugins (especially fly with lua)... Also not sure what this does? "Application was launched with the following command line options... '/high"

Maybe a lingering dataref after the automatic extension that doesn´t get reset properly (like a combination of replay, etc) - I will try to investigate myself.

Hrm - this is getting weird... If you are running an unusual monitor configuration it could be that your window is now outside the viewable boundaries? Here are the values from the prefs.txt: mainMenuX = 180 mainMenuY = 284 Thats the only thing I can think of. If all else fails, also delete (or move away) the IXEG_user_prefs.txt to test. Cheers, Jan

Maybe also try the very latest version found here.

No idea...never heard of that before. Try to follow standard troubleshooting protocol:

Hi, the log looks like the problem was with BetterPushback...but if you say it crashes with SMP, it may be due to some memory overflow as well (lua). Maybe Ben R. can shed some light on this. Cheers, Jan

Just uploaded the very latest beta from Ben in this post below...maybe go and try to see if that helps? Cheers, Jan

Yeah, PROGRESS page is WIP - sorry that its not working right yet. :-/ The way a "runway" shows up on the route or legs page is determined by the way it was coded. If you depart from runway 09, you don´t want runway 09 to be your first waypoint, as you would otherwise make a full circle, fly back to the threshhold were you just started your takeoff run and then continue on your route . Every SID will end with a route discontinuity until you finish building and connecting your flight plan. A route discontinuity is the FMC´s way of asking you "and where do you want to go after this?" Cheers, Jan

Hi - the startup situation in the IXEG is not controlled by X-Plane. You need to choose the preferred situation (cold and dark, turnaround, ready to fly) in the PREFLIGHT menu of the IXEG side-pop-out menu. Try to install with the standard stable gizmo if the side-pop out does not work for you. Cheers, Jan

Happy that worked for you. Regarding the buttons - the autopilot system is modeled very realistically - which in turn means it is complex and can be confusing unless you study and understand it first. Often a button will not "work" because the conditions for engaging it are not met. The most common problem is actually the user deflecting the yoke - which prevents engagement (or disengages them) of certain modes or the autopilot as a whole. I have made some tutorials for that. Reinstalling X-Plane or the IXEG is only the cure for a tiny fraction of problems users have. Most of the time it is a "placebo" cure - after reinstallation people do something slightly different and not it works - so the reinstall seems to have been the cure. Cheers, Jan

No - that should not happen! It is the first time I hear about that problem... Cheers, Jan

Hi Leeroy, I am in contact with Ben and he is also reading along these forums. I am sure he will let you know if he needs more info, thanks for the offer! Cheers, Jan

Very nice, thank you, XPJavelin!

Hi and thanks for the nice words and the feedback. I totally agree about the vortices - we are using "default Laminar Research" particle effects for now - I really want to update those, though - and make better vortices (at the right spot and only the right conditions) and also APU heat blur, fire extinguisher bottle effects, better touchdown smoke, etc. I also noticed the flight-altitude problem with the mousewheel, I will enter a ticket for Tom to look at it. I am not sure about the Vspeeds - we may have coded this so that the take-off v-speeds get erazed from the EADI speed tape if you enter the approach speeds. I really don´t remember how the FMS handled this on the real 737-300, I never did that ;-) It is also quite possible that the behaviour was changed, I am sure the Zibo is using a much more modern software standard for their FMS. Cheers, Jan