jimbim

Happy to hear that you got it running! Greetings, Sebastian

Hello idm54, I have no idea what's going on with your setup. On my side, I am only flying the IXEG and always together with WT3. When looking at your LOG-file, I can tell you which plugins I do not use that you are using... maybe try without them... plugins/NavigraphSimlink_64.xpl (Navigraph Simlink for X-Plane). plugins/xpInsider64.xpl (fspp.xpinsider). plugins/ASXPConnect/64/win.xpl (HiFi). plugins/MoveVR/win_x64/MoveVR.xpl (org.solhost.folko.movevr). plugins/SlewMode/64/win.xpl (vitazenisek.plugins.SlewMode). plugins/TerrainRadar/64/win.xpl (drgluck.plugins.terrain_radar). plugins/X-RAAS2/64/win.xpl (skiselkov.xraas2). plugins/Xchecklist/win_x64/Xchecklist.xpl (Michal_Bill.Example.Xchecklist). plugins/projectFLY/win_x64/projectFLY.xpl (mettar.projectfly.bridge). plugins/xgs/64/win.xpl (babichev.landspeed). if you are still getting CTDs I would install a fresh, second copy of xp11 and only add the IXEG and wt3 and check if it works. Then adding plugin by plugin and try to identify the one that is causing the CTD in combination with WT3 and IXEG. Greetings, Sebastian

Hello, I think that Pilot2atc does not support the IXEG .fpl format. However, it is very easy to create it using notepad... You just have to enter you route in following format: DEP_ICAO WAYPOINT WAYPOINT WAYPOINT ... ARR_ICAO Save it as .fpl in coroutes folder and you are done. Greetings, Sebastian

Any chance for a fictional new Lufthansa livery? Greetings, Sebastian

Hello, I don't know if E46 is somehow a famous Airport or a point of interest but it is on top 3 of the new Airport usage data pusblished on developer.x-plane.com (https://developer.x-plane.com/2017/11/x-plane-11-airport-usage-data/#more-8021). If it is just a boring airfield somewhere in Texas it could indicate a true bug. Just saw that and wanted to inform you about it. I personally never had the problem. Sebastian

Ok, I can confirm now that any button on my yoke which is set to "do nothing" in XP11 will disable the autobrake immediately. It's strange that a button that should not send anything to the sim can change the behaviour of the IXEG. For me, it looks like it is a Laminar Bug but I am not sure. At least we know that there is something going wrong here. Sebastian

Great to hear that! I will try tonight if a simple button on my yoke that is set to "Nothing" will disarm the autobreak as well... Sebastian

Hello Mike, I had quite the same issue with my Saitek Throttle Quadrant till yesterday. I did some more testing and found some strange behaviour of XP11/IXEG. My setup: Left lever: Speedbrake, Mittle Lever: Thrust Engine 1, Right Lever: Thrust Engine 2. The Saitek has 3 integrated buttons that are active when you push a lever below 0 (Marked in red circle). for these buttons my setup is: Left: "do nothing", Middle: Toggle Reversers, Right: "do nothing". After Landing, I push the two thrust levers beyond 0 to enable toggle thrust reverse and at that point, the autobrake was every time disarmed automatically. Quite strange as I never had this issue on X-Plane 10 with the previous versions of the IXEG. So I did some tests! When I just push the middle lever below 0 it toggles the reversers and autobrake keeps active. If I just push the right lever below 0 to activate the button that is configured in XP11 as "do nothing", the autobrake disarms immediately! THIS IS STRANGE! I tell X-Plane that NOTHING should happen if this button gets active but it disables the autobrake! So I repeated the same test for the left lever. It was also configured to "do nothing". If that button gets active it disables the autobreak as well! I found a way to work around that issue by creating a small FlyWithLua script that creates a command that really does nothing. function do_nothing() -- This function is needed because thrust revers buttons on saitek throttle quadrant -- will disable autobreak if Xp11 "do nothing" is set on them. end create_command("MyStuff/IXEG733/DoNothing", "Do really nothing","do_nothing()","","") After assigning my "DoNothing" command to the two buttons the autobreak works as it should. I do not know If that might help you but maybe you have the same kind of problem with your go flight tq6 throttle. I also cannot tell if that is a bug of XP11 or IXEG... Greetings, Sebastian

Found the related post: http://forums.x-pilot.com/forums/topic/8430-gizmo737-linux-compatibility/?do=findComment&comment=89126 Sebastian

Hello Ryan, From your Log I can see that your Disk ist Case Sensitive formatted. It might be that I am wrong but I am thinking that I read somewhere that Gizmo does not support that! Maybe you get in contact with Ben Russell and verify that. Greetings, Sebastian

Hello Sloboda, First: Without any logfiles it is nearly impossible to help you with your problem. Second: If you have Tugmaster from Jardesign (itow) then remove it from your plugins folder and try it again. Greetings, Sebastian

As far as I know, the spoiler will deploy automatically if reverse thrust is toggled. Maybe I am wrong... I'm sure someone will know it :-) Sebastian

I heard that too I thought it is intended and is caused by gusting wind... But maybe that's wrong... Sebastian

I did a nice flight from LPPT to EDDN on VATSIM on Wednesday and the Collouts worked. Markers I am not sure... Can not remember :-) What I am still missing somehow is the minimums callout... Sebastian

I would try following: 1. Grab you X-Plane DVDs and make a fresh install to C:\X-Plane 10 with just a small part of global Scenery. 2. Download the latest X-Plane Installer/Updater from http://www.x-plane.com/downloads 3. Update X-Plane to the latest stable release 4. Start that fresh installed X-Plane version and check that it loads correctly with a default plane. 5. Quit X-Plane 6. Add an Exception for C:\X-Plane 10 in Windows Defender and/or your Anti-Virus Software. 7. Redownload the IXEG Installer (without using any download manager) from X-Aviation 8. Install the IXEG with that Installer into the fresh C:\X-Plane 10. 9. Start X-Plane as administrator and check if you can activate the IXEG. 10. Do not add any plugins or custom scenery until you have verified if the activation works. That's how I would try to get that topic solved. Greetings, Sebastian

That's what I thought as well. Sebastian

Hello Shawn, I am using the IXEG on two computers. One is my Desktop Computer with a dedicated graphics card and the other is my laptop which I am using to test and develop some stuff in X-Plane. This Laptop has an On Chip Intel HD Grapics card. On my Desktop everything looks fine... On my Laptop however, I have the same issue as you have. I have the feeling that it is somehow linked to that (poor) Intel HD Graphics card. Some techical Information for IXEG Team: My Graphic Card Details from X-Plane Log: Shawn's Graphic Card Details from X-Plane Log: Maybe it can help you somehow... For me it is pretty clear that an on chip gpu is not the correct approach to run a flight simulator. For testing it is ok but it has pretty poor performance and I would not expect a good experience with it. Greetings, Sebastian

Hey Shawn, Can you Tell me what graphic card you are using? Thanks, Sebastian

I was using this plugin as well without any problems with the CRJ2, B757 and B777. Only the combination with the IXEG is causing problems... And a really weird one :-) A CMD window... How the hell can that happen? :-) In general I do not care too much... The IXEG has it's own push back solution... On the other hand it would be nice to have it back again... it is simply more advanced and you can influence where you get pushed to... Jar does not really react on his forum... Someone started a topic there... Greetings, Sebastian

Great that it works for you! Sebastian

If you are using FlyWithLua, you can script around it. I my self have disabled the Gearlever in xsaitekpanels ini and use this little script to use the lever. require("xsaitekpanels_switch") local prev_gear_dn = SWITCH_GEARDN local prev_gear_up = SWITCH_GEARUP -- GEAR SWITCH function gear_status() if SWITCH_GEARUP == 1 and prev_gear_up == 0 then command_once("sim/flight_controls/landing_gear_up") end prev_gear_up = SWITCH_GEARUP if SWITCH_GEARDN == 1 and prev_gear_dn == 0 then command_once("sim/flight_controls/landing_gear_down") end prev_gear_dn = SWITCH_GEARDN end do_every_frame("gear_status()") Make sure you have implemented the xsaitekpanels modules into FlyWithLua and USE AT OWN RISK! Sebastian

And this is the reason why you cannot put the lever into the off position. If it is up on the saitek panel, then it sends always up! Sebastian

You are absolutely right! If I change the speed to 220 it works fine! I just was not used to change the speeds with other Add-Ons. I will take care of it in the future! Thank you! Sebastian

Hello, There seems to be something wrong in the drawing of DOSIS28 Transition at EDDN. I use the default NavDataPro delivered together with the IXEG. IXEG_debug_01.txt Greetings, Sebastian