Litjan

Hi, you had the "Level 2" fail problem: 0:05:53.975 G64: debug: IXEG: Performing Level-2 check 0:05:53.975 G64: debug: IXEG: Level-2 check FAILED 0:05:53.975 G64: debug: IXEG: Killing critical functions, kill set [1] 0:05:53.975 G64: debug: IXEG: Killing critical functions, kill set [2] 0:05:53.975 G64: debug: IXEG: Level-1 PASS / Level-2 FAIL. License invalid

Use the X-Plane default weight and balance screen to set weights and fuel.

Thanks for providing the solution here, @hermannk1!

Please post your log.txt.

Interesting - we will investigate!

Window heat was fixed in the update that was released roughly 6 hours ago (your post if 4 hours old). Engine start is a known issue (mentioned several times in the post about the known issues and also in the patch notes). We will look at the Generator temps and your suggestion is noted.

It says on the weight and balance GUI - read of the MAC%, enter that on the takeoff ref page and read of the required trim setting.

There is an update upcoming that will likely help you with your landing flare (and the takeoff, too).

The manual is outdated. Please use the X-Plane default GUI to enter weight, balance and fuel (the IXEG now uses the new load-station physics available in XP12, therefore the old ground services menu way of setting this could not be used anymore.

Thanks for letting us know, @Pacifica! Zink is working as an OpenGL bridge, so it isn´t surprising that it might influence the drawing of cockpit symbology... too bad that turning it off will also make the framerate decrease a lot for AMD users. I will bring this up with Laminar, maybe they can improve Zink to help with this...

Dead horse, please check post in Bug reports/IXEG confirmed

@Debowing Don´t use SAM.

This is turbulence, try it without real weather and no turbulence. I will try to see if I can reproduce the fuel problem!

I will doublecheck that again, can´t say that I have noticed that yet. Maybe if you are right between two values... we don´t do any dampening, so if the temperature is -30.499 and then changes to 30.500 and goes right around those values...yeah, I can see that changing rapidly all the time? Can you do a video of what you see? Bobby is hobby, nur wer muss fliegt Bus ;-)

You guys both have AMD GPU´s, correct? I suppose that your drivers are up to date. I am not familiar with those, but do you have a utility software that you can set certain things (like anti-aliasing, mipmapping, etc.) on? For Nvidia it is the Nvidia Control Panel. Maybe you have set some special setting there that would affect the OpenGL drawing?

Interesting...it should be off by a bit (they rarely are exactly the same, one being fed from the air data computer, the other showing raw data), but 300 feet may be a bit too much. I will check!

Hi, could you try again with all your custom scenery (especially X-Europe and VFR Hungary) removed temporarily to another folder? Vielen Dank, Jan

Thanks for the report - I will try to fly the BKX4 departure and see if I can replicate (and hopefully fix) this. Cheers, Jan

Hi there, and thanks for the detailed feedback! Some things are already known, you can always check that here: https://forums.x-pilot.com/forums/topic/27194-ixeg-v15-for-x-plane-12-confirmed-bugs/ The Nav1 frequency will be "weird" in other X-Plane aircraft, too - I agree that it looks strange, but in subsequent use it will default to the previous frequency you had tuned during shutdown, so it should be a very transient problem. The transponder code 7000 is for VFR flights in Germany, it is just an arbitrary choice. 2000 would be military night flying, 1200 is for VFR in the US. Fluctuating numbers are measured very often, the pilot needs them to be updated all the time. The documentation was not updated yet. The clock´s year can not be changed (yet), that is a very low priority but maybe can be changed in the future. The PROG page is still WIP, much of it´s content is not calculated correctly. The fuel flow at idle is indeed a bug that will be fixed for the next version. The effect of engine-anti-ice on fuel flow is negligible, we have not modeled it (just like the effect of winglets). The plane will always turn the shortest way, if you turn the heading bug past 180 degrees, it will reverse the direction. No, we won´t make a clickspot for all lights, but I might get Tom to make the inboard landing lights "toggle click" instead of "grab and pull". Cheers, Jan

Yeah, we have to keep an eye out for these things - ultimately the move to FMOD will alleviate a lot of the sound problems, I think. Today I lost all IXEG sounds after having the sim on pause for half an hour...

I would like to say it is a feature ;-), but if so - probably unintended. On the real aircraft, those key buttons are like "microswitches" and you will hear a click when you push them down. However sometimes they are so worn, that they dont make a click anymore but still work. Maybe the CLR button is like that (it is used very often).

Regarding the "pitch oscillations" - I have not been able to reproduce those YET, but this could be due to environmental conditions like turbulence, etc. If you use FL CHG when descending from a higher altitude like FL240, the target speed will revert to a Mach number (if you have been on VNAV before) and since the true airspeed for a given mach number increases rapidly with decreasing altitude, a jet will really "dive down" if you initiate a constant Mach descent. Modern airliners are better at mitigating this, but nevertheless, descent rates are high) 5000+ feet/min. Use V/S to initiate the descent - I did (with -2000 fpm) and the plane pitched down smoothly without overshooting and maintained 2000. Cheers, Jan

Just flying your route, @SWA4420, could it be that you did not remove the route discontinuity after the RNDRZ2 arrival terminates at BERBN? It actually ends in "radar vectors" and ATC would expect you to keep flying straight (away from the airport) - you are only allowed to turn onto the ILS if you are cleared for the approach, in that case move "SHAND" onto the "vectors" line to "close" the flightplan.

We have not heard back from @Pacifica, we asked him to remove his plugins to test if those have an influence... maybe you can try the same so we can isolate the conflicting plugin and work on a solution? Thanks, Jan