Litjan

It is a contemporary misconception that a product is more valuable if it gets "frequent updates". The best product is the one that does not need updates - updating something means that it was in need of an update - hence not as good as one that is not in need of an update. The mode control panel works perfectly and if you are having problems with it (at least I can find nothing wrong with it and I flew the real aircraft for 10 years), I will go out on a limb here and say that you are not using it correctly. The same goes for the FMC, except for the clearly outlined areas where we consider it not fully functional yet as detailed in this post: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v15/ If you find anything not working in EXCESS to what is outlined in that post, please let us know. Best regards, Jan

I understand this - and I also like to have "development updates" on the games I play, stuff that the devs work on, plans for the future, just some chatter to read and follow along with. But we at IXEG are now just a small 2 person team with "real" jobs and families and shifting life priorities. We already talked a bit about what we could envision in the future... right now there is nothing to talk about. Tom is working slowly on converting the sounds to FMOD (which will not make them sound different at all) and we are still planning to fix some stuff like the VNAV and HOLDs, but a timeline can not be given and doing so would just not be reputable. For me the IXEG 737 project at this point is purely a labor of love. The income I get is negligible and my motivation is purely from my love for the aircraft and the good vibes and emotions I get when interacting with the users. If you want to see the 737 get developed further in the future, don´t take that motivation away. Posts like yours are a good way to kill that motivation. So as harsh as that may sound: There is nothing to talk about right now and we are also not some YouTube or Instagram channel who needs to post new content every day to keep his followers engaged.

The forums are quiet I think because everyone is just flying the plane. It works well, except for the VNAV, which we readily admit. Your other problems are most likely a matter of preference, and - sorry to be so frank - your inability to fly a 737-300 correctly. It is NOT doing "what it wants" and it is also not hard to control the speed - you are likely just a bad pilot . I have flown the real 737-300 for 10 years and this one flies exactly like the real one does. Yes, you need to plan ahead, just like when flying any high performance aircraft. We haven´t updated the plane in the last 9 months because it works fine and if you think a product is better because it gets more updates...well, maybe it just NEEDS more updates? How many factory recalls does a well-made car have per year?

Awesome, thanks for the feedback!

Not on the 737-300.

I just doublechecked in XP12.1.0 Beta 6 and the engine generators worked fine for me. You need about 50% N2 for them to be able to provide the right frequency, the engines idle at ca. 60% N2 normally.

I just flew a pattern around EDDF in 12.1.0 beta-4 and could not perceive any stutter (framerate low 30s). On the framerate graph you can see the framerate drop slightly every few seconds, this is likely due to additional CPU time required to poll the terrain database like Ben said.

While your post is hard to understand - I guess English is not your first, second or third language - I believe you want to know how to arm your LNAV mode on the ground so that it automatically engages when you lift off? The answer is that this was not possible on the 737 "classics", it is a feature that only newer Boeing aircraft have.

Remove XPUIPC or update it to a version that works with the IXEG.

You are probably using XPUIPC - there is only one version that works, the software is not updated and supported anymore.

I checked, and for me they are all working on my end - there is only one test position that will test the fire warning, it is next to the fire warning handles, labeled "TEST" and you have to move it to the right (position OVHT/FIRE). Then the bell will sound and all firewarning lights will illuminate. This works fine for me.

I will double check...thanks!

No.

Interesting...thank you!

Yes, I have seen this on occasion as well and have not yet found out what causes this...maybe a Zink issue, not sure.

Great!

Gizmo is not the problem, one of your other numerous (some of which are known to cause crashes) plugins is - possibly in combination with Gizmo. You will need to remove all of them temporarily (remove them, disable is not enough) and then run only vanilla X-Plane (the way it was when you first installed it) PLUS the ixeg 737. Then see if it crashes. Then add one plugin back after the other until the crash happens, then we have found the conflict. Once we know which plugin causes the conflict, one knows where to look for the problem to fix it.

You are doing something wrong.

Your hardware may be too good - because fps is just fine on my Ryzen 5800 and Geforce3090 with 32GB of RAM.

No.

See it this way, maybe? When you eventually upgrade to XP12...the IXEG will be there waiting for you (unless we moved to XP13 by that time )

I assume X-Aviation and I know IXEG (since I am part of the team) is perfectly willing to accept the potential loss of sales from the XP11 version at this point. We believe that the potential benefit from providing a separate download environment for that version is not outweighing the increased complexity that this would bring. We realize that many people are still running XP11, just like there are many people still on FS2004 or WindowsXP. On a personal note, whenever I read about someone sticking with XP11 there is usually an emotional unwillingness to deal with the new and unknown...in this case totally unfounded ;-) Cheers, Jan

Ah, thank you for the beautiful pictures - they bring back fond memories of flying the Classic for 12 years! The NG is supposed to fly fairly similar to the Classic (although most variants are a bit heavier), I am sure you will enjoy it!! I assume the difference might be like the one between 747-400 and 747-8 (the ones I fly now), they are subtle but noticeable nonetheless. Good luck and success with your type rating, all the best, Jan

Your license check has failed: 0:09:19.169 G64: warn: We have received:[lss.xa.validation] msg:[8599407] param:[187465520] 0:09:19.170 G64: debug: IXEG: ----Beginning License Check Sequence---- 0:09:19.170 G64: debug: IXEG: defaulting IXEG license to OFF before activation checks 0:09:19.170 G64: debug: IXEG: Staging kill functions in case license invalid.... 0:09:19.170 G64: debug: IXEG: Verifying Level 2 backup before initiating checks..... 0:09:19.170 G64: debug: IXEG: Level 2 backup ready and standing by, Beginning license checks 0:09:19.170 G64: debug: IXEG: --------------------------------------------------------------- 0:09:19.171 G64: debug: IXEG: Checking for valid license via Level 1..... 0:09:19.171 G64: debug: IXEG: Level-1 license check good. Requesting Level-2 check.... 0:09:19.171 G64: debug: IXEG: Performing Level-2 check 0:09:19.171 G64: debug: IXEG: Level-2 check FAILED 0:09:19.171 G64: debug: IXEG: Killing critical functions, kill set [1] 0:09:19.171 G64: debug: IXEG: Killing critical functions, kill set [2] 0:09:19.171 G64: debug: IXEG: Level-1 PASS / Level-2 FAIL. License invalid You need to contact the X-Aviation support to get help with that. In addition, your X-Plane installation is completely overloaded with add-ons and extra scenery, some of it not running correctly, some of it not compatible with XP12, or known to cause crashes. I would suggest "cleaning house" ;-)

After you try to run the plane and shut down X-Plane, go to the X-Plane 12 folder and find the file "Log.txt". You can attach that file to the next post here, then I can take a look if I spot something out of the ordinary.