RXP

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.

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.

I've edited my post by the time you've answered with: ADB ‘is’ the nav data (Aviation DB) and ODB ‘is’ the obstacle data (Obstable DB). Please note these are more recent variable names used to unify the RXP GTN and GNS V2 naming conventions but the older name is still working: GNSDBFILE

@Bert Pieke Hi, ADB ‘is’ the nav data (Aviation DB) and ODB ‘is’ the obstacle data (Obstable DB). 1) Imagine you have all your db files located here: C:\GNS_DB\ Use: GNSNAVDATA= "C:\GNS_DB\" This tells the GNS V2 where to find all the DB files (BMAP.bin, terrain.adb, terrain.odb, terrain.tdb, worldwide.bin) 2) You want to test new obstacle data file (helicopter for example) and you save it here: C:\GNS_TERRAIN_DB\terrain.odb Use: GNSODBFILE= "C:\GNS_TERRAIN_DB\terrain.odb" This tells the GNS V2 where to find this file independently of the others. It will load the 'odb' file from here and all the others from GNSNAVDATA path or the default. 3) You have a new aviation DB file (new cycle) and you copy it here: C:\GNS_NAVDATA\worldwide_new.bin Use: GNSADBFILE= "C:\GNS_NAVDATA\worldwide_new.bin" This tells the GNS V2 where to find this file independently of the others. It will load the 'adb' file from here and all the others from GNSNAVDATA path or the default. This scheme permits you sharing the ’terrain db’ which seldom changes, and ‘override’ the ADB and ODB independently. NB: this works the same with the RXP GTN using GTNODBFILE and GTNADBFILE.

HI, I believe you can first download, then burn the card. In any case it is most likely first saved to the hard drive in a 'temp' folder. Unless this is only when using the Jeppesen JSUM system instead of the Garmin system?

Have you at least started with the "Recommanded" posts you'll find at the top of the 1st page of this discussion?

Hi, Yes this is correct! You can therefore configure these variables to broadly tell the GTN/GNS V2 where to look for the entire dabase file set, and/or you can selectively tell them where to look for specific database files (navdata, obstables).

Hi, It depends whether the aircraft is using part of the panel.png to 'paint' instruments in the 3D panel or not. I'm not sure how the best to find this out but to eventually start configuring the .ini to draw the GTN over the entire surface and see if there are bits of it appearing at different places in the 3D cockpit?

Hi, Congratulations for trying and succeeding! You'd have to make sure to enable mouse clicks in the rendering section. You might want to open the RealityXP.GTN.ini file of another aircraft (default created file is better) and see the available settings to add to your own section, namely usemouse, popleft, popright (they differ slightly from the GNS V2 because of the touch screen).