RXP

Commercial Member
  • Content Count

    2,919
  • Joined

  • Last visited

Community Reputation

343 Excellent

About RXP

  • Rank
    President, Reality-XP

Flight Sim Profile

  • Commercial Member
    Yes
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male

Recent Profile Visitors

3,123 profile views
  1. RXP

    No Flight Plan Import Button

    The easiest should be this: 1) install the trainer once and only once everywhere you want. Safer in default location, but otherwise with our v2.5.7 you shouldn't have any problem if on another drive, it should detect it. Otherwise, you may still use the environment variables to override auto-detection and point to other folders. NB: installing is different than installing+moving the installed files. If moved there is no way to auto-detect where they are, whereas if installed the trainer installer leaves traces where-to (at least for the purpose of uninstalling). 2) install the RXP GTN wherever you've installed the simulators. For X-Plane, the plugin gets copied into the XPlane folder tree and moves along with it, like any other XPlane module. For Prepar3d, the gauges and modules gets installed in a known and safe location which gets dynamically references via the 'add-on' XML file purposedly, for FS it requires the gauge file and module to be copied into the FS folder tree and our installer takes care of it.
  2. RXP

    No Flight Plan Import Button

    HI, I'm not sure installing the trainer in two different locations is helping anything, unless you explicitly tell the plugin, or the gauge depending, where to locate it. There is a mechanism for this documented in the user's manual via environment variables. Nevetheless you might want to reconsider installing a single trainer instance because there is no need for any more than 1. Then once settled, it might proove easier to find a solution.
  3. Let's keep our finger crossed that v2.5.7 solves the issue on your end. With Shadin Fuel disabled, it wouldn't cause the problem, but I'd rather you continue flying as it was just to make sure v2.5.7 solves this. Nonetheless, there is a potential division by 0 in the trainer I've detected thanks to your report, so I'll 'patch' the trainer for this.
  4. RXP

    Wrong Product?

    During installation it shows/tells it is for FltSim, both graphically to the left hand side with the series of Prepar3d, Flight Simulator logos, and in the text. Furthermore, the only installation options would be FltSim related, not X-Plane related. The downloaded installer also ends with -FSIM for our FltSim products and -XPL for our X-Plane products. I'd guess it might be easy to click the wrong box as they all look alike. I'm sending you a PM.
  5. Well it seems this is a bug in the trainer not taking care to test before dividing by 0... Try shutting down the engines (fuel flow = 0) while having power on the GTN (try always on) and I'm pretty sure this will crash. I've a couple ideas to workaround this.
  6. Hi Pavel and thank you for the detailed information! This is most appreciated! I can see from the RXP log files you are not using the latest GTN which is v2.5.7. You might want to use the latest: Otherwise, we'll see if the error reported is new or solved in 2.5.7 and let you know.
  7. RXP

    Mixing GNS and GTN

    Yes, these are different products entirely. Looking at your e-commerce receipts will tell you if this is the GNS V2 or not: GNS V2 product name is: RealityXP Garmin GNS 530 (XPlane) (product id: RXP-GNS530-XP) legacy is: Reality XP Garmin GNS 530 WAAS X-Plane 9 (product id: RXP-GNS530-X9) Just make sure you do not mix and match the two: you might have purchase both the legacy a long time ago, and the GNS V2 more recently, and you've just not installed the GNS V2 in XP10 but the legacy instead? I wouldn't want you to purchase the product twice.
  8. RXP

    No Flight Plan Import Button

    Please note: "FLPN" (flaps normal?) is not the same as "FPLN" (flight plan) 😉
  9. RXP

    Mixing GNS and GTN

    Your listing seems to show our legacy GNS isn't it? Should you have installed the GNS V2 on XP10, there should have been a "rxpGNS" folder there, with a "32" and "64" subfolders. Unfortunately, the legacy gns product is not designed nor working with XP11.
  10. RXP

    Navigraph Data in GTN750

    Hopefully, the RXP GTN using the latest trainer v6.50 makes you fly with cycle 1803!
  11. Thank you, this makes it easier! So what is happening, is a Windows system component (KERNELBASE.dll) is failing due to an invalid floating point exception. I don't have any idea what on your system could cause this, it could be many, from anti-virus, to 'system tools' running in the background, or drivers (audi/video mostly). I can't help but noticing these though: Dumping info for module C:\Program Files\Alienware\AWSoundCenter\UserInterface\AWSoundCenterDevProps.dll Dumping info for module C:\Program Files\Alienware\AWSoundCenter\UserInterface\AWSoundCenterOSD.dll This means you are running an audio-related software, most likely to offer on-screen-display, which gets injected in every single process/application you run. You might want to explore this avenue and find if you could disable this.
  12. RXP

    LPV not activated

    Here are some advisories found: https://www.garmin.com/en-US/aviationalerts/service-advisory-1029-rev-d-egnos-activation/ The combination of the EGNOS SoL broadcast and the database-enabled EGNOS capability facilitates the use of the EGNOS satellites in the navigation solution. The use of EGNOS will be transparent to the flight crew. Depending on certain criteria and available data in the navigation database, LNAV approaches augmented by EGNOS may provide advisory vertical guidance, which is indicated on the display as LNAV+V. https://www.garmin.com/en-US/aviationalerts/service-advisory-1372-rev-b-unavailable-rnav-gps-approaches-due-to-lack-of-vda/ A limited number of RNAV (GPS) approaches, including all service levels, are unavailable for selection when the approach includes LP minima and also has no published vertical descent angle (VDA). This issue is resolved in the following software versions: GNS 400W/500W Series main software versions 5.10 and later GTN 6xx/7xx Series main software versions 5.13 and later unrelated: DBs are growing in size so we'll be loosing more and more airports unless using regionalized DBs: https://www.garmin.com/en-US/aviationalerts/service-advisory-1846-worldwide-navigation-database/
  13. RXP

    LPV not activated

    I think I'm starting to get the "why", please correct me if I'm wrong. Looking at the LFLA RWY18 GNSS and it mentions the 'EGNOS' channel used (Ch 41134). However, the GNS only has WAAS (at least software 3.30). When trying a synthetic test on the trainer, anytime I make the LFLA RWY36 active, it disables 3D DIFF and reverts to 3D only in the satellite view page. As far as I remember, there was a software update on the GTN recently (yes GTN) which mentioned something along the lines of not disabling GNSS approaches. As far as I know, the aviation DB includes 'feature' bits which disable specific approaches based on equipment, and reviewing the trainer bowels I think this is what is happening in the GNS. Does this makes sense to you?
  14. RXP

    LPV not activated

    Looking into this issue, I've found these links for LFLA: https://www.sia.aviation-civile.gouv.fr/dvd/eAIP_11_OCT_2018/FRANCE/AIRAC-2018-10-11/html/eAIP/Cartes/IAC/LFLA/AD 2 LFLA IAC RWY36 GNSS.pdf https://www.sia.aviation-civile.gouv.fr/dvd/eAIP_11_OCT_2018/FRANCE/AIRAC-2018-10-11/html/eAIP/Cartes/IAC/LFLA/AD 2 LFLA IAC RWY18 GNSS.pdf For any other french airport: https://www.sia.aviation-civile.gouv.fr/ select "eAIP France" to the left select an effective date, this opens a new web page select "PARTIE 3 AERODROMES (AD)" | "AD 2 AERODROMES" to open the list of airports. select an airport in the list select "CARTES RELATIVES A L'AERODROME"
  15. Hi, I'd guess you've got this content from: "C:\ProgramData\Garmin\Trainers\GTN\crshrprts\gtn1\Logs" Can you please go one folder up, locate another folder which name is a typical GUID, typically: "C:\ProgramData\Garmin\Trainers\GTN\crshrprts\gtn1\70bbec66-b3bd-4975-9162-df462e18eb9f" In this folder, you'll find a file: crashrpt.xml which content is most needed!