RXP

Commercial Member
  • Content count

    2,076
  • Joined

  • Last visited

  • Days Won

    1

RXP last won the day on October 14 2016

RXP had the most liked content!

7 Followers

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

1,944 profile views
  1. Missing Add-On Menu The Gauge Add-Ons menu requires SimConnect which is normally installed automatically with the simulator. For 32 bits simulators, it requires a minimum of SimConnect FSX-SP2, which is found on the installation disks (FSX-ACC/SP2) or in the following folder (FSX-SE): "SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi" Should the menu fails to display, you can create or manually edit the add-on/SimConnect files. P3D4: Start Windows notepad, create a new text document, copy and paste the following content, then save to: "My Documents\Prepar3D v4 Add-ons\Reality XP GTN\add-on.xml" <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AddOnXml" version="3,3" id="add-on"> <AddOn.Name>Reality XP GTN</AddOn.Name> <AddOn.Description>Legendary Gauges Redefined</AddOn.Description> <AddOn.Component> <Category>DLL</Category> <Name>Reality XP GTN Menu</Name> <Path>C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\64\rxpGTN_menu.dll</Path> </AddOn.Component> <AddOn.Component> <Category>Gauges</Category> <Name>Reality XP GTN Gauge</Name> <Path>C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\64</Path> </AddOn.Component> </SimBase.Document> P3D3: Do as above but change both <Path> lines ’64’ to ’32’ as shown below, and save the file to: "My Documents\Prepar3D v3 Add-ons\Reality XP GNS\add-on.xml" <Path>C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\32\rxpGTN_menu.dll</Path> <Path>C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\32</Path> P3D2, P3D1, FSX-SE, FSX: The menu uses the global DLL.xml file found here: "C:\Users\[name]\AppData\Roaming\Microsoft\FSX\dll.xml" Open the file with notepad, then copy and paste the following <Launch.Addon> section: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> ... </Launch.Addon> <Launch.Addon> <Name>Reality XP GTN Menu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Reality XP\GTN Simulation\FltSim\32\rxpGTN_menu.dll</Path> </Launch.Addon> </SimBase.Document>
  2. What is this? ????? It's here! Mind you, you've just posted 7 hours ago, to which I've replied ?????
  3. What about just running FSX at normal priority?
  4. Hi, I'd be surprised this issue is back, especially nothing has changed in the code for this since many versions now. Could this be a recent ForeFlight update (or bug) counterbalancing some GNS counter-balacing code? NB: I can't see the screenshots, it requires authentication.
  5. Hi, First things first: please do check the RXP log files for any possible information (see User's Manual for file/path). Like gillesbdx says, a failing A/P is most likely related to sim1.dll (considering all your GNS settings are correct, i.e. link A/P etc...). However, please also note the A/P coupling won't work with the latest P3D4.2 just released a few days ago, we are working on the update for it.
  6. Hi, like explained in the User's Manual: Configuration Panel Press and hold the SHIFT key then RIGHT-Click the top edge of the GNS device to open the configuration panel. As for the rest: Missing Add-On Menu The Gauge Add-Ons menu requires SimConnect which is normally installed automatically with the simulator. For 32 bits simulators, it requires a minimum of SimConnect FSX-SP2, which is found on the installation disks (FSX-ACC/SP2) or in the following folder (FSX-SE): "SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi" Should the menu fails to display, you can create or manually edit the add-on/SimConnect files. P3D4: Start Windows notepad, create a new text document, copy and paste the following content, then save to: "My Documents\Prepar3D v4 Add-ons\Reality XP GNS\add-on.xml" <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AddOnXml" version="3,3" id="add-on"> <AddOn.Name>Reality XP GNS</AddOn.Name> <AddOn.Description>Legendary Gauges Redefined</AddOn.Description> <AddOn.Component> <Category>DLL</Category> <Name>Reality XP GNS Menu</Name> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\64\rxpGNS_menu.dll</Path> </AddOn.Component> <AddOn.Component> <Category>Gauges</Category> <Name>Reality XP GNS Gauge</Name> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\64</Path> </AddOn.Component> </SimBase.Document> P3D3: Do as above but change both <Path> lines ’64’ to ’32’ as shown below, and save the file to: "My Documents\Prepar3D v3 Add-ons\Reality XP GNS\add-on.xml" <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\32\rxpGNS_menu.dll</Path> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\32</Path> P3D2, P3D1, FSX-SE, FSX: The menu uses the global DLL.xml file found here: "C:\Users\[name]\AppData\Roaming\Microsoft\FSX\dll.xml" Open the file with notepad, then copy and paste the following <Launch.Addon> section: <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> ... </Launch.Addon> <Launch.Addon> <Name>Reality XP GNS Menu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Reality XP\GNS Simulation\FltSim\32\rxpGNS_menu.dll</Path> </Launch.Addon> </SimBase.Document>
  7. Hi Richard, Thank you for your kind words and sorry for the delay. The power state and many others are already available via the published L:Var "rxp.gps.discrete_out" It is mentioned in the User's Manual but not extensively documented there. Do you have any particular need for this?
  8. @EPICfan I've edited the post with the correct link for our latest GNS V2. Sorry for the delay. I'm not sure it'd show 'WAAS' though, which is the denomination for our legacy GNS instead, but the URL is the correct one for the latest nevertheless.
  9. Please let me know how if disabling the option works best on PilotEdge or not. As a matter of fact, the latest update added this option (was standard before), and the standard is now 'any AI'. The purpose is that many customers flying with 3rd party traffic injected in the simulation used to set their X-Plane AI count to 0, which was in fact telling our plugin there is no AI to display. The trick used to be to set XPlane AI count to whatever you prefer so that the GTN/GNS V2 pick it up, and let the 3rd party AI traffic injects data into the datarefs slots. However, doing so, it seems X-Plane is computing AI traffic for nothing. Nevertheless, we'll add a few more heuristic to prevent 'ghost' aircraft like this one.
  10. Hi, The HSI requires enabling the 'HSI' link in the settings panel. It is independent of the A/P coupling. This might explain why the HSI needle didn't point to the right direction. As for the e-commerce problems, it seems our e-commerce procurement partner is giving a number of our customer a problem lately as reported on the forums. We are not sure what is the problem on the internet, or the servers, but I'm sure they'll fix it soon. In the meantime, you might want to cross check this:
  11. Unfortunately, until X-Plane SDK offers the capability for third party developers to create in-sim, live, 3D planar surfaces to not only draw to, but also to capture mouse clicks, we'll have to deal with the limitations of displaying/rendering our plugins to pre-existing surfaces in the aircraft 3D panel, and to use a full screen invisible window to grab the mouse... :-(
  12. Hi, This most likely is the new AI code which is now using 'heuristics' to gather the entire 19 MP datarefs slots, since it appears whenever using 3rd party traffic plugins, the X-Plane SDK fails to report the actual number of injected traffic. You can restore previous versions mode with: Settings | Gauge Options | Advanced | Use Simulator AI Traffic Count Next update will reverse the logic, i.e. default using simulator AI count, and option labeled "Use Third Party AI traffic"
  13. Hi, info@ is not for support, this forum is! Have you tried this:
  14. Hi, this most likely reads: "there is no service available to update the databases on the trainer". In other words: "there is no 'update' or 'subscribe' button readily available". However, the GTN Trainer uses the same DB files as the real unit (more or less). What governs this all is the DB EULA (the Trainer EULA does not explicitly precludes using another DB with it, although it considers the trainer as a whole). However, IIRC, the JSUM EULA granted the right to use the Jeppesen DB both on real and simulated devices explicitly. (I can't find it back yet - I've been digging tons of archives but failed so far).