Commercial Member
  • Content count

  • Joined

  • Last visited

Everything posted by RXP

  1. 11.21 should've fine though otherwise I'd guess there would be much more similar reports in the forum. Otherwise, you might want to search for conflicting plugins, starting with moving out all plugins to a different folder, testing if this cures the issue, then reintroducing the plugins one by one until finding the culprit.
  2. Hi, Now included in the Reality XP GNS 530/430 V2 FltSim v2.3.12 and Reality XP GTN 750/650 Touch v2.4.16! Mid Continent MD41-1484W Annunciator Control Unit Mid Continent MD41-1028 TAWS CONTROL UNIT The rxpGpsAnnun.cab includes two gauges offered as addition to the GTN and GNS V2, the Mid Continent WAAS annunciation panel and the Mid Continent TAWS control unit. They are released as XML gauges, so that it makes it easy for third party vendors to integrate the same annunciation panels as-is in their aircraft, or using the same XML code when displaying in an EFIS for example. Both gauges install automatically to P3D4 and P3D3 using the GNS V2 and GTN existing add-on.xml file. It requires editing the panel.cfg file to add them to the actual panel though. For manual Installation: Prefered method is using the Prepar3d addon xml file: 1) copy the file rxpGpsAnnun.cab to "C:\Program Files (x86)\Reality XP\Gauges" 2) copy and paste the following to a new file named 'add-on.xml' <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AddOnXml" version="3,3" id="add-on"> <AddOn.Name>Reality XP GPS Annunciation</AddOn.Name> <AddOn.Description>Reality XP Gauges</AddOn.Description> <AddOn.Component> <Category>Gauges</Category> <Name>Reality XP GPS Annunciation</Name> <Path>C:\Program Files (x86)\Reality XP\Gauges</Path> </AddOn.Component> </SimBase.Document> 3) copy the add-on.xml file into: "Documents\Prepar3D v4 Add-ons\Reality XP Gauges" Alternatively, copy the rxpGpsAnnun.cab file in the simulator Gauges folder. Gauge specs: rxpGpsAnnun!TAWS,0,0,350,100 rxpGpsAnnun!WAAS,0,0,350,100 Known limitations: - Requires Reality XP GTN 750/650 Touch v2.5 minimum. - Requires Reality XP GNS 530/430 V2 v2.4.1 minimum. PS: For the old-timers, they used to be included in our GNS legacy, but weren't included yet in the GTN or the GNS V2 gauge file. I've decided to reboot these gauges and offer them as XML gauges, so that it makes it easy for third party vendors to integrate the same annunciation panels as-is in their aircraft, or using the same XML code when displaying in an EFIS for example.
  3. I'm hoping you'll enjoy these goodies!
  4. Hi, have you checked your anti-virus for any 'RXP' quarantined item?
  5. RXP

    unable to import flight plan

    @awash2002 what about the rest?
  6. This is the legacy GNS product , moving the discussion to the correct forum.
  7. I just want to make sure bat this: the latest release version is 11.20: https://www.x-plane.com/2018/05/x-plane-11-20-final-released/ all other newer versions are 'beta' and could break any plugin.
  8. RXP

    Gtn750 and native vr x plane 11

    @gordong please understand this is XPlane limitation only, not offering the means for third party plugins to implement any form of touch screen, or even more generally 3D mouse inputs (the later are possible only when pre-compiled into the 3D model as specific mouse triggers) In non-VR, I've documented in these fora we do use a trick which consists in creating an invisible XPlane plugin window covering the entire XPlane screen for the sole purpose of capturing mouse events.
  9. Hi, see the following section: [GTN_750_1.PANELS] frame.rect = 0,0,0,0 For an unknown reason it has reset to 0,0,0,0 You might want to try these values from another thread: frame.rect = 1436,2048,610,748
  10. RXP

    FS Radio Fix?

    Hi, this is very easy to do manually: http://www.prepar3d.com/SDKv4/sdk/simulation_objects/aircraft_configuration_files.html#radios
  11. RXP

    How to navigate with GNS-530 WAAS

    Hi, The autopilot is following the heading bug (HDG mode). Make sure to enable NAV mode instead.
  12. This sounds like the latest XPlane version (which is a beta if I'm not mistaken) is maybe causing this then. Can you try reverting back to the latest official RELEASE version instead?
  13. RXP

    User waypoints file

    Hi, can you please elaborate and detail exactly what you mean with 'only click once' ?!?
  14. Hi, Was this working fine prior the last week? Which XPlane version are you running: the latest official release version, or the latest beta version? Did it started to fail roughly around the time you'd have updated XPlane to the latest beta version?
  15. RXP

    User waypoints file

    Hi, Please make sure to review the RXP GTN User's Manual for paths to these files, and where to find a ready to use sample pack.
  16. RXP

    GTN750 Dark after reinstall

    Hi, The files installed in C:\ are in the correct place. However, unrelated to the trainer installation issue, the latest GTN installer should copy the plugin files and the 'rxpGtnSim' files into the "C:\Program Files (x86)\Reality XP\GTN Simulation\X-Plane\" folder too (in sub folders: 32\ 64\ and bin\) The User's Manual file name is not the latest either. However, the log files show the latest version number ok, so at least, the files installed in the XP11 plugin folder are correct, so are the rxpGtnSim##.dll (per the log file version number as well). I'm glad you've got all sorted out in the end!
  17. usually the hardware is pre-configured with a selector, this should be written on a sticker, otherwise default is 0 (zero). The selector servers the purpose to differentiating 2 hardware devices of the same type connected to the computer, so that you can use for example selector 0 with GNS #1 and selector 1 with GNS #2.
  18. RXP

    GTN750 Dark after reinstall

    Hi, have you manually moved the trainer files to M: after installation, or have you pointed the installer to M: when the Garmin trainer installer offers a 'choose a location' option? Are you running X-Plane as admin or as a normal user?
  19. RXP

    GTN750 Dark after reinstall

    Hi, simple answer: like you've just did, because THIS is the support forum! Can you please review the content of the RXP log files (see GTN User's Manual for file/path)?
  20. Please review the User's Manual, you have to manually edit the RealityXP.GNS.ini file to tell which hardware specifically: ; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 It is possible the initial ini file created in the aircraft folder as a HardwareIdx = -1 which disables the hardware.
  21. meaning Garmin's or Jeppesen's
  22. RXP

    new user query

    Hi, I'm sorry for the delay but this is a lot of questions at once. Let me try to answer: 1) When the airplane 'turns away', were you expecting the A/P to be in APPR mode and the CDI mode on VLOC, or NAV mode and the CDI mode on GPS? 2) popup window: most likely a RealityXP.GTN.ini setting (in the aircraft folder) is wrong, but it would be best other customers report their experience for this one. 3) GTN 750 and GTN 650 are 2 different products like you can see on our website.
  23. Hi Ron, yes, and it is already taken care of! The RXP GNS Hardware Driver is specifically for the PFC hardware (PFC 430 among others). Any customer of the GNS Hardware Driver unlocks the feature in any of their RXP software, including the latest GNS V2. In addition, the last couple GNS V2 update now include the new 64bits PFC DLL we were waiting for to make it work in P3D4 and XP11!