RXP

@Matchstick https://www.avsim.com/forums/topic/628749-happy-new-year-2023/ @svtdoug I thank you for your patience and I'm sorry for the unusual situation. Online support will return to "normal" in a few days and should catch up with you all.

This has been a hard post to write. I hate that this happened and I kick myself every day for not paying more attention to our support operation in the past few months, while spending most my time on new products R&D. There is only so much one can do in a day and it is a good reminder you’re human and mistakes are easily made. And even though I hope this didn’t affect the majority of our customers, thanks to the maturity of of existing products and that they are reliably running, I want to apologize to those of you who were in needs of RXP assistance during that time. I also want to thank you for your enduring support throughout. We’ve been offering some of the most incredible simulation add-ons for 20 years because you keep us going every day, by buying our software, by giving us your good ideas, by telling your friends about us. You are the good in the world! So we’re going to do everything we can to rise above this and keep going even further, together.

Hi, please look at the recommend posts in this topic: https://www.avsim.com/forums/topic/605896-reality-xp-update-removed-airports-from-garmin-430530/

@Kakugo What used to be "worldwide" seems to be deprecated and shows as "Transatlantic" in the device, but I'd suggest you cross-check this prior purchasing anything. As for the GTN, there is no need because you can subscribe GTN database as-is. NB: this "equivalence" table is meant only to substitute the original GNS db subscription which you can usually burn only on a proprietary cartridge, with another type of subscription which you can burn on an SD card, which makes it easier afterward. However the regular GNS database updates are supposed to be also working fine with the GNS trainer.

Here is a non-exhaustive table of different GNS Trainer compatible DB: GNS Trainer | Database Type/Region | Serial Number | GNS DB (latest) | Substitute / comments --------------|-------------------------|----------------|-----------------|--------------------------------- bmap.bin | Worldwide Land | n/a | n/a | mg1000-ww-20M3 (G1000) | | | | mg600-ww-20M3 (G600/G500/G500H) | | | | terrain.adb | Airports Terrain | 006-D0122-04 | n/a | n/a | | | | terrain.odb | Obstacle (afct) | 006-D0123-02 | b500-ue-21B5 | bg1000-ue-XXXX (G1000) | | | | bdg600-ue-XXXX (G600/G500) | | | | | Obstacle (heli) | 006-D0123-03 | b500h-ue-21B5 | bdg600h-ue-XXXX (G500H) | | | | terrain.tdb | Terrain Worldwide-30 | 006-d0121-00 | t500-ww-20T1 | tg1000-ww-XXXX (G1000 - 30 Arc Second) | | | | worldwide.bin | Navigation Data (acft) | n/a | j500a-XX-2110 | jg1000-XX-XXXX (G1000 Jeppesen) | | | | jg600-XX-XXXX (G600/G500 Jeppesen) | | | | | | | | compatible: ww (transatl), int (international) NB: there are other regional database coverage available, besides int and ww, and they should work (most likely) NB: there is an official notice for the Jeppesen WW DB (Worldwise) Beginning with Cycle 1810 (effective September 13, 2018): Garmin will begin restricting the number of airports included in the Worldwide Navigation Database, based on the length of the longest runway. Heliports and Airports that do not contain a runway of greater than 5000 feet will be excluded from the Worldwide Navigation Database. All associated data with excluded airports (communication frequencies, approaches, runways, etc.) will also be excluded. Beginning with Cycle 1911 (effective October 10, 2019): Garmin will discontinue the Worldwide Navigation Database for the affected products listed above. The Transatlantic Database will be offered in place of the Worldwide Database. Other regionalized versions of the navigation database will remain available and will have no restriction on airports within the coverage area.

@BostonJeremy77 Thank you for the heads up. I can't find this 737 MAX though. Would you mind posting the link to it, and eventually the links to the 747 master branch/release page?

😂

@Kakugo I've cross checked for example the Garmin DB Data Exclusion bulletin but I didn't find LSZG there: https://avdb.garmin.com/docs/garmin_navigation_db_data_exclusions.html But on the Jeppesen DB Data Exclusion you can find: https://avdb.garmin.com/docs/garmin_data_exclusions.html It seems it is indeed removed because of this Garmin CDI scaling issue and requires software 5.10 at a minimum. Hopefully there are only a few approaches which are affected.

The GNS Jeppesen DB are supposed to work ok, but not just them. The G500 have been working too because they are the same format. (DB1, the older format prior the introduction of DB2 format 3 about years ago)

I believe you can't extract them from the card unless you do have a card reader on the PC and the driver to present it as a drive. However, the files are most likely saved to disk prior writing and usually you'd find these in a "temp" folder, in the "user" folder, or in the "programdata" folder somewhere. Otherwise, some G500 DB subscription (at least the Jeppesen one) are compatible with the GNS and in this case, it burns on a regular SD card in the FAT format.

@mSparks Do you mind posting the LAT/LON/ALT of this screenshot, along with the actual screen res it was rendering?

I'm pretty certain your PM box will get flooded with requests for results and this might just be easier posting them here 🙂 Like @Janov is saying, the purpose of this topic was to evaluate how much worth it really is in practice, and @mSparks must be commended for helping you ride along the way (and let us learn a few Linux tricks in the process too). You'd left most of use craving not having the end results after all these steps and discussion pages!

I'm looking forward to the XP11 scenario you'd suggest, thank you for all the Linux details and help too!

Why not posting the location, time of day, XP11 settings, screen res (this looks like 1920x1080?) of this screenshot so that a bunch of us can just try what it looks like on their system at similar conditions? Not a scientific experiment, but could give some indications whether one would want trying Linux or not depending on what it gives on his/her system. I personally wouldn't consider worth my time trying Linux if I show 120fps in the same conditions as your screenshot above on my Win10 test system, but to each his own. NB: this is a genuine sincere question, not a hypocritical mockery in disguise.

Unfortunately it is not funny at all, but hopefully it is limited to the 'A' APIs (it is in fact MAX_PATH = 260). When using the 'W' API instead (wide chars - I know don't pick this one up either - UCS2 vs UTF16 etc...) the limit is 32767 provided you prefix the paths with a "\\?\" https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation Nevertheless, the file API is a mess and antiquated from the 16 bits area I agree with you, and look, even FS2020 code is messing around with path containing any "accented" character... as if they're using the 'A' API with a fixed US code page like 1252... this begs some other questions indeed but these are irrelevant to this topic!

Thank you for the follow up. In case, please don't forget to add the aforementioned lines in the .ini file found in the aircraft folder you are flying so that it can trace additional information in the log file if needed.

There is definitely something peculiar because at the very least the first few lines should tell something about the location of the trainer when using LogTrainer = 5 Are you sure you're editing the RealityXP.GTN.ini file in the correct aircraft folder?

Not to the bottom. Please look what the two lines are preceded with in my example then find the same line in your file.

This is peculiar. Are you using any 'tool' like process lasso? Have you cross checked you've configured Windows to run the trainer on your discrete GPU in case you have both discrete (NVidia/AMD) and embedded (in the Intel CPU)? If you're in this case please review the RXP User's Manual troubleshooting section for this topic. You might want to also manually edit the RealityXP.GTN.ini file in notepad and add the following: [GTN_650_1] LogTrainer = 5 DebugValue = 1 ... Next time you run XP11 the GTN log files shall have more details about what is going on.

Can you please confirm: Are you running XP11.50? Are you running it in Vulkan? You do have reinstalled the GTN 650 with the e-commerce installer using your F1 credentials? The GTN 650 used to work on your system with XP11 before?

Can you confirm your anti-virus program has not quarantined any 'rxp' file?

Hi, Can you please post the content of the RXP log files? (see user's manual for file/path)

Hi, This is not a graphic anomaly, rather, the code driving this aircraft fighting against the GNS VLOC/GPS mode most likely. Please review the GNS settings and make sure CDI sync is set as SIM <=> GPS.

Hi, the Jeppesen G500 DB has been working fine so far*. I don't know for the Garmin DB itself. AFAIK the Jeppesen process permits separate D/L from card burning, otherwise, the G500 is using standard SD cards and this makes it easier to extract afterward. You might want to start reading the recommended posts in this discussion though especially the search tips.

Remember environment variables are set prior launching a program, therefore in this case, the program is not the trainer in the background but the simulator. If you change the var, you'll have to relaunch the simulator for it to take effect.