Litjan

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

Yeah - had the same thing happen to me a few times - glad that fixed it for you! Cheers, Jan

Please try to run with all other plugins disabled and let me know if that helps (also post the log.txt) so I can take a look at what may be interfering Cheers, Jan

Thats the way the DRM works, and there is a warning about that when you get asked to type FREEZE. You can try to file a ticket with the support at X-Aviation and if you can really explain why you froze a computer that you still intend to use the product on - they may possibly even reinstate it. But there is nothing I can do about it. Cheers, Jan

I would try the stable gizmo - unless you somehow clicked the preference to "disable the popout menu". In that case you must assign a button or key to toggle it - or open the ixeg_user_prefs.txt and set the preference there. Jan

After some consultation with Shifty we determined that the only runway related waypoints that can be entered in the FIX page are from the actual flight plan (i.e. what you can also find on the LEGS page). So if you fly to Frankfurt (EDDF) and you have the ILS approach to runway 07C in your FMS, there will be a RW07C waypoint on your LEGS page. You can enter this one into the FIX page as any other fix. You can NOT just enter RW07L at that point - only after you changed the approach in the FMS to ILS07L. So we are going to implement it like that - only waypoints that you find in your LEGS page. Cheers, Jan

Hi Leeroy, I steer your attention to this post, there is a link at the bottom to the latest Beta of Gizmo as published by Ben Russel, the developer. Always pays to try those... You can just swap out versions all you like, the credentials are stored elsewhere so you won´t be asked to enter them again. Unfortunately some systems can´t run the newest version...yet. Cheers, Jan

I believe that the temperature indication is working like this: https://de.wikipedia.org/wiki/Wheatstonesche_Messbrücke So if power gets removed, it simply stays where it is at. In other words - it needs power to "move" the indication to the correct value. Cheers, Jan

Also check the IXEG_user_prefs.txt file, it contains the coordinates to display the window at. Hope this helps, Jan

You have locked your computer (typed FREEZE on the confirmation screen). Most likely because you installed the product on another computer. You can only install it on three different computers.