Coop

I think @Pils advice should get it sorted for activation. The FMOD warnings are known (we haven't done the FMOD XP12 upgrade process yet). Regarding the object missing, if it persists after activation, please file that bug. https://torques.im/bugs

We don't have a precise ETA on the CJ yet.

Yes the G500 will be getting updates for XP12, the current version should be largely functional in XP12 for the time being.

Yes, if the G500 displays themselves are low resolution, that is going to be something else in the stack beyond our control causing that.

We are working on preparing our X-Plane 12 versions of our aircraft and will be making them available to customers through a public beta process. All customers have access the XP12 version of their product for free. If you would like to take part in the public beta's, please fill out this form here: https://torques.im/tsxp12pb and we'll get you added once the beta starts on the various products. With X-Plane 12, there are many bugs that could crop up. To report bugs, the only place to ensure bugs get properly recorded is through our bug reporter form at https://torques.im/bugs. We will triage all reports that come in through here. More to come soon

It depends on how the aircraft was setup and configured for prioritization. I'm not sure how this aircraft setup its panel objects.

That is showing the optional RealityXP GTN integration. The GTN750/650 from RealityXP is purchased separately from their own site for X-Plane.

X-Plane autoscales texture resolution based on available VRAM and the texture resolution slider, it isn't something in our control.

In X-Plane settings -> Data Output, there is a checkbox to show the FPS in the main window. It will then show in the top left of the X-Plane screen.

Initial testing shows that they largely do currently work unofficially, but we will be doing proper XP12 (free) updates for both.

What framerate is your sim running at? I can't get a great look from that video but it appears that it might be quite low. This is dependent on the X-Plane graphical settings. If the CPU is fully saturated, it can block our engine model from running causing the engine oscillations.

Those error messages regarding the Earth orbit textures should be unrelated to any CTD experienced (they are common for tiles of exclusively water). Regarding CTD, unfortunately in both log.txts I am not seeing any obvious culprit and we aren't currently tracking any common CTDs on this product. We'll look into this to see if anything further comes up to give us a better idea.

The TorqueSim Islanders have both G5 and G500 integrations. You would need to re-run the TorqueSim Islander (BN-2B and/or BN-2T) installer to grab the G500 variant if you haven't ran it since purchasing the G500.

Did you select the "G500" version of the BN-2T from the aircraft selection dialog in X-Plane?

It appears that the aircraft is unable to reach the validation server to activate your license. This could either be due to no network connection, a conflicting plugin blocking network traffic, or some sort of firewall configuration. If there isn't an issue with the network, try temporarily removing 3rd party global plugins and see if the issue resolves.

In order to debug what is going on, we will need you to send us a copy of the X-Plane log.txt file. You can find a guide to get this file here: How to find the X-Plane log.txt file?

There is a list of aircraft where we have known integrations here: With 3D integrations, VR support should be functional, but we don't test VR heavily ourselves.

From the SR22, you can try copying the 'svs.dll' file from sr_systems/win_x64 into the pr_systems/win_x64.

Properly installed navdata is not specific to a certain aircraft. The aircraft should be inside the X-Plane 11/Custom Data folder and contain the files indicated in the screenshot. If these are installed properly, the X-Plane X1000 will load them, otherwise it will revert to the default old navdata.

Press and hold the bottom right button on the PFD for Baro Set. After 2 seconds it should toggle to mb from inHg.

From the log.txt file, it appears the synthetic vision system is failing to load with this driver. Unfortunately that is something that is out of our control, as it appears this driver doesn't contain the necessary OpenGL calls for SVS.

It is something we are looking into

Hi Simon, Does this occur if you use the default GNS instead of the GTN? If so, this sounds like a configuration issue with the RealityXP settings. In those settings, make sure that the RealityXP GTN is writing to the VOR and HSI datarefs. If you send screenshots of the RXP settings dialog in X-Plane I can try to pinpoint ones to try to get it working.

Hi Franz, We aren’t currently doing VR specific popouts for our windows, but it is something we will look into for a future update.

What hardware are you using? The brake-control interface should all be handled by X-Plane so this sounds like something might have corrupted in the X-Plane preferences, or some interference with the hardware.