Matchstick

The TEGB bug is triggered even if you aren't in the region, I think it's caused when the G500 reads the data from a wide area around your current location (perhaps 1000NM or maybe the entire globe ?) which includes the scenery.

There was a new release version of OpenGPWS posted to the main Github repostory yesterday with the fix included and pasting the contents of that into the plugins\OpenGPWS folder of the aircraft I've been testing has stopped them crashing. https://github.com/skiselkov/opengpws/releases It may well be that there are other issues that will be caused by doing this so it's only a very temporary fix to get the planes up and running again until a patched version of the G500 can be released.

I'm afraid I'm not workign from hope today so I haven't been able grab any load data but I'll trry to grab that this evening However I did notice on the FlyJSim discord there was mention that their Q4XP was also crashing with the XP12 TE GB North and one of their devs have confirmed that it's an issue with OpenGPWS which has now been fixed in the source. It might be a coincidence that two products both using OpenGPWS are crashing with the same scenery but I do wonder if it's worth looking at.

I've run into an odd problem with the new XP12 version of the OrbX True Earth GB North and the RSG G500 which is resulting in XP12 crashing when the G500 is enabled. I first spotted the issue when starting a flight in the HSF EC130 with the RSG G500 plugin installed with the GTN 650 and 750 enabled with direct route between EGTC and EGVA entered (neither airport is in the TB GB North region). Shortly after turning on the avionics the sim CTDed. I've been able to replicate the issue in a clean copy of XP12 12.0.9 with no scenery other than Global Scenery and Airports plus XP12 TE GB North and no plugins other than Gizmo using the HSF EC130, the Torquesim BN-2B Piston Islander and the default C172 G500. The process is simply to load the aircraft at EGTC, enable the battery and avionics (if the G500 doesn't start with battery) and wait. The sim will freeze and then CTD within approximately a minute. I've tried the same steps without the XP12 TE GB North scenery and with the XP1 TW GB North Scenery rather than the XP12 version and in both cases the sim was fine after serveral minutes. I've attached log files for the 3 aircraft I tested with the XP12 TE GB North scenery as well as logs for the C172 G500 with no TE Scenery and with the XP11 TE GB North scenery. Additionally a scenery_pacs.ini files shows what was loaded when the TE scenery was enabled. Log - XP12 TE Islander.txt Log - XP11 TE C172.txt Log - no TE C172.txt Log - XP12 TE C172.txt Log - XP12 TE EC130.txt XP12 TE scenery_packs.ini no TE scenery_packs.ini

It's now 18 months since the initial release of XP12 - can you say least say if the turbine engine modelling is now complete ?

Thank you for that.

That's the sort of thing I've been asking for for about 6 month now. Thank you. Are systems/avionics, flight model and sound expected to require substantial work once turbine and 3d models are more complete ?

The issue isn't the time that's being taken. The issue is the refusal to talk to customers about what stage the project has got to (and I use "refusal" deliberately there).

I'm honestly at a stage where I would like more information on how the development progressing than a bland assertion. I'm not asking for a release, I'm not asking for a release date but I would like some actual idea of where in the development process the project is.

Patience is not an infinite virtue, especially if someone feels it is being taken advantage of.

There quite a lot to be said for something that can actually be flown now, not some utterly indeterminate time in the future (if ever).

Are you still getting the Level 2 authentication failure message in the Log ?

Have you tried opening a different plane first then opening the DC-3 ?

What I did was start a flight with the 737 which worked fine, then went back to the main menu and started the flight from a different location, which then fails to load the aircraft properly because of the Level 2 authentication failure. On my system at least, even with no plugins enabled this error appears 100% reproducible.

Just retested the problem with the plane failing the Level 2 license check the second time it's loaded within an XP session but this time with no plug-ins installed and it's failed again. So at least for me this issue doesn't seem to be a plug-in conflict. Zipped copy of the log file attached. Log - 737 no plugins.zip