mokny

@Tom Stian Nice script - You're the guy who brings us Online-Pilots into big trouble with the ATC And that's what I really like :-) So, from the software engineer's point of view, I have some small suggestions for your script. You're declaring a bunch of global variables in your script (Max_Failures, FailFactor, Cycles,... etc). That may cause problems with other LUA scripts. So it's either a good way to declare these vars locally in a function or prefix them with something like IXEG_Failuers_Cycles [...] to make sure that no other script will accidently produce sideeffects. Especially "Cycles" is a var that'll be used quiet often. 2nd: By adding these 2 lines behind line 16, you can Enable/Disable the script via the Macros-Menu. add_macro( "IXEG Failures DISABLE", "Max_Failures = 0" ) add_macro( "IXEG Failures ENABLE", "Max_Failures = 2" ) Cheers and happy checklist running

The new 1.1 Installer does not create the directory "coroutes" inside the Aircraft-Folder. So if you are wondering why you can't export from whatever program to the IXEG, just create the folder <X-Plane>\Aircraft\X-Aviation\IXEG 737 Classic\coroutes

As the IXEG is not a standalone process, it makes sense to exclude the X-Plane.exe, or the complete X-Plane folder.

Dependant on where EFASS got the route from (route cloud for example), there may be no DCTs inside. But following the rules, the DCTs should be present. I won't update the plugin anymore, as the new EFASS-Version is on the way and it will be more strict on route formatting. Looking forward to this (The export plugin for the IXEG is already included)...

In case you're not using airways, the route in EFASS itself should always look like WPT DCT WPT DCT WPT ...

Who knows? Maybe you'll find Mordor. Sorry could not resist.

In case you are using Windows, exclude the X-Plane path from Windows-Defender.

This fix changes nothing (even on IVAO). It works with other planes (it's not a fix, only a kind of Light-Styling), but here's sthg different causing the problem.

Same on IVAO. The issue is known.

Ok, conclusion: What I did: Plugged in the additional SSD Moved the X-Plane folder from the old drive to the new SSD Renamed the old folder, to make sure nothing gets loaded from the old location What's not working: Jar-Products must be re-activated Aerosoft-Products (EHAM/EDDL) must be reinstalled What is working: The IXEG 737 SkyMaxx Pro Real Weather Connector So, good job X-Aviation! Works like a charm.

Ok thank you all. I will give it a try and report back!

Thanks for your reply It's not a different system, it's just that I'll run Xplane and the addons from a different drive, that will definitely have a different HDD serial, no matter if I'll clone or not.

Cheers, tomorrow I will switch X-Plane to a new SSD-Drive (the old one became to small), so some questions... The Operating-System-Drive and the old SSD will stay in place, only X-Plane will move to the new, dedicated one. Do I have to reactivate the 737 (and maybe other X-Aviation products? SkyMaxxPro, RWC installed) Will there be problems regarding the Hardware-ID? I don't want to purchase another copy just because I changed my hardware General question - Moving XP from one disk to another is still possible (movin the folder)? Did it with some older version and there were no problems. Is that still correct? Thanks in advance for reading/replies. Cosmo

@Litjan You can grab the latest magnetic declination model here as a database (csv exportable): http://www.ngdc.noaa.gov/geomag-web/#igrfgrid

Hm strange, I got a script for my Warthog running and that did the trick. But what I also do, is to check if the value that I want to set, is already set, because that way the script doesn't fire dataref changes all the time to Gizmo. Maybe that helps you out.

Same Airac Cycle in IXEG as in EFASS? Legs on airways that only consist of 2 points are interpretet as Direct by the IXEG, the airwayname won't appear in the FMC Why don't you post the complete route here? Or better the file? It's hard to find out without details..

Change "do_every_frame" to "do_often" and the stack-overflows are gone.

Ha, I wondered why they are blinking and now I see this topic. Just tried to disable the WX, and the blinking stopped. Nice find!

Sometimes writing in bold makes the text less visible than writing in regular letters Move the mouse to the left to open the menu. You'll find the version at the bottom of the window.

You did not read the topic. 3 posts above you..

There are no "real" GPS approaches in the 733 as in the NG. Use LNAV and VNAV/VS/FLCH to fly the vertical app according the charts. Remember that you can not set the GA Altitude in that case.

Ah, in that case you are using different Airac-Cycles for EFASS and the IXEG. Use the same cycle + the same publisher (Navigraph/Aerosoft)

well, that's exactly the way it works.

Nope. http://ticket-system.org/efasswiki/index.php/Exporting_Flightplans#IXEG_737:

Hi, i have a 3 way switch. Up: Gear lever up Down: Gear lever down Middle: Gear lefer off Works, but as soon as I address the dataref ixeg/733/gear/gear_handle_act with write access with FlyWithLua (without setting any value) I get a constant sound of the lever. Is there a different solution? This line is enough to get a constant sound loop (of course the line itself is not placed in a loop...): dataref("GEAR", "ixeg/733/gear/gear_handle_act", "writable") Thanks for reading and suggestions!