RXP

Hi, Have you tried again since Friday? It might have been a temporary outage?!

The ini file looks correct, except both [XXX.PANELS] sections are set with visible=false and frame.rect = 0,0,0,0 which means they won't draw on the 3D cockpit. - I believe this is the auto generated default, not the one included with the Carenado isn't it? - Actually is there any included with the Carenado? If the GTN is "stuck" in "rebooting..." it really means it is rebooting (shutting down the garmin trainer in the background and restarting it) and if this keep displaying it means it hasn't completed this task yet, or got stucj doing so. The only reason I can think could be causing this, because it has happened already with a few aircraft but corrected since, is when the aircraft code logic is fiddling with the GTN plugin, trying to enable/disable it. There have been a few aircraft where the developers are trying to control the GTN from their aircraft utility panels, instead of letting the user controlling this via the RXP menu and dynamically adapt the aircraft around it, and due to the very asynchronous nature of the plugin, you can't expect a good outcome if you do this thinking it will react synchronously. Unfortunately I don't have this aircraft to try repro.

@AJZip this might help a lot of other people to know what mouse brands/models you did try!

There is one golden rule in VR: don't move the camera, the user IS the camera! https://forums.flightsimulator.com/t/bug-feature-fs2020-is-breaking-the-vr-golden-rule-dont-move-the-camera-the-user-is/344861?u=cptlucky8

Hi, Can you also confirm the terrain database is listed on the boot screen?

@Ludmar63 Thank you for the additional information. So if I understand correctly, so far it was only the GNS V2 on XP11 with Win11, and now it seems it is the GNS V2 on XP11/P3D5.3HF2 with Win11. I'm afraid the only way to try solving this will be to have you all trying different builds privately. I'll prepare something in the coming days and contact you all privately for this. Thank you for your patience and help with this issue!

Hi, First things first. Are you sure you're using FS9 v9.1 and not v9.0 ? -> You can cross check this: right click the fs9.exe file > Properties > Details and lookup the full version number. As for the popup message, it means there is a debugger attached to your FS9 session. Are you actually running a debugging session? -> If not, this means there is an add-on of some sort, or maybe you're using a launcher of some sort, which is using debugging mechanism and injected in the FS9 process.

Let me reassure you, I also fail to find my own posts quite often in just using the embedded search. This is why I nearly always use site wide search engines requests and I usually find it all! Here is the canonical form: site:avsim.com keywords For example the above is: site:avsim.com GTN VNAV garmin autopilot As for the integration I agree there is much more that can be done to make integration nearly 1:1 to real world integration, especially since the Reality XP GTN (and GNS V2) also output the actual same information which would be used IRL to do so. Having said this, I can assure you there are many X-Plane developers who are contacting us and who are taking advantage of the data our simulations are offering for their integration.

Hi, The current discounts are offering 35% off any product purchase. This one is easy: just use the "at home" coupon during purchase and the price will adjust in the e-commerce enabled installer. The 50% off discount is for the 2nd product of the same series. You download the coupons (a .zip) and once unzipped, there is a readme file explaining exactly what coupon file to use (as many coupons as combinations of 1st and 2nd purchase products). Say your 1st purchase was the GTN 650 for Prepar3D with 35% off with "at home", you can benefit from the 50% off with the other coupons when you purchase the GTN 750 for Prepar3D.

Hi, Are you referring to VDI (vertical deviation indication - en route)? If so, there are plenty of topics already about this in the forum: https://www.qwant.com/?q=site%3Aavsim.com+GTN+VNAV+garmin+autopilot And a recent discussion here:

@Kassu62 please follow the link from my post to see with your own eyes it is not just IPD adjutement (really, there are examples there you can try immediately on your monitor) @dogmanbird World Scale is live, NIS/FSR Sharpness is live too! @kdfw__ Thank you for your kind words! It won't be saved per-aircraft because OXRTK is game agnostic. But it is quick and easy to re-adjust and after a short while, you know pretty much what adjustment value you'd use with which aircraft.

Can you please post the link to their forums here, so that I can collate everything and see what I can try to pass them along?

Thanks! This rules out any problem with P3D4 or the GTN! Now what is the DC6 doing which is not working as excepted is most likely DC6 related only. It is possible they simply don't enable vertical tracking when the NAV source is the GPS because there never was any vertical guidance capable default GPS in FSim/P3D. It has happened with other vendors and if this is the case, it would take an update. Otherwise it might be as simple as an aircraft config file but I doubt it. Have you raised the question on their forums already?

I feel for you 🙂

+100 I won't go back to 3D either except when flight testing RXP devices during development 🙂 VR also reveals when an aircraft 3D model is proportionally correct and when it is not (I'm not talking about world scale perception here but relative size of cockpit items, like having a 1/2 size GNS bezel in front of you in a correctly sized cockpit). There are a number of aircraft I won't cite which are showing dimension problems like this which you can't see on the monitor, because perspective projection is making these appear correct instead. Since you're new to VR, my personal suggestion would be that you try Half Life Alyx... Even if you end up no liking the game much (but it can be addictive mind you), I believe it is THE game to try out in VR. It was built for VR only and it is an experience to live and try once in my opinion!

I confirm it is coming up in the other more general OpenXR ToolKit project, and this is working great! The world scale adjustment is pretty much based on what I've documented here and I'm glad we can put in motion some of these ideas, which honestly, would have been quite simple to implement in the core game from the get go... In addition to NVidia NIS Upscaler, the OXRTK is also embedding the AMD FidelityFx FSR Upscaler and it might be just personal, but I like it much more than NIS in VR because I find it is not taking more computing resources and the sharpening feels much more natural, albeit less contrasted than NIS though. At least users will have the choice to use what fits their headset panels and vision sensitivity better! I'm also working on other QoL features, such as a filter to reduce the over exposure in VR. It won't be a magic wand but it will help a little bit. I've also an experimental implementation of a tweak which corrects some of the 3D vector maths lighting bug in FS2020 (something contributing a lot to the shimmering bug... wait, there is no shimmering bug did they say in the last Q&A? 😉 ) but the problem is that this tweak is also causing WMR motion smoothing to loose its tracks sometimes. So for those not using motion smoothing I might consider implementing this in the official release. Here is the official OpenXR ToolKit project where this is happening (there is no release available yet): mbucchia/OpenXR-Toolkit: A collection of useful features to customize and improve existing OpenXR applications. (github.com) There is a lot going on in this project and I must say Matthieu is doing an excellent job and I'm honored to be working with him on this project!

Just to make sure, what is the full version number of your Prepar3d.exe file (right click > properties > details)?

The Baron (if you've kept it prior they remove it)? Otherwise the Mooney Bravo should do.

Hi, In order to display the GTN in the 3D panel, you usually just need to configure the GTN to do so, provided there is an existing space in the virtual cockpit render texture panel.png. This is better explained in the user's manual and in this topic: https://www.avsim.com/forums/topic/535115-tutorial-upgrade-x-plane-11-baron-58-gps/ Also, I don't remember specifically all the mod already published but did you try looking in the official panel mod topic, or maybe better, in the following pinned topic: https://www.avsim.com/forums/topic/523298-gtn-750-default-cessna-172/

Did you try this with a simple stock aircraft or the DC6?

Hi, You might want to start with the included RXP GTN User's Manual? Windows Start > Reality XP or C:\Program Files (x86)\Reality XP

@Airmanf117 please do not cross post. Is there any RealityXP.GTN.defaults.ini file in the aircraft folder?

@Sky Terrier You might want to review the dedicated topic for this, starting with the recommended posts: https://www.avsim.com/forums/topic/546848-rxp-gns-530w430w-v2-database-update/

Hi, If the GTN is displaying fine in a popup window, it means it working fine and the reason you don't see anything in the 3D panel is most likely therefore a configuration problem. You might want to cross check the RealityXP.GTN.ini file and whether there is a 3D panel entry for the 650, and whether it is set to "visible" with a proper frame.rect value. You can find more information about all this in the User's Manual and in this tutorial: https://www.avsim.com/forums/topic/535115-tutorial-upgrade-x-plane-11-baron-58-gps/

Hi Mike, I'm sorry for the delay, and I thank you for your patience with this issue and your help to solve this. If I understand the test cases: - render to 3D panel -> no issue - render to popup window -> no issue - render to popped out window -> no issue - render to 3D panel + popup window -> no issue - render to 3D panel + popped out window -> memory leak/growth over time. I'll review if there could be anything "leaking" a resource in our code but I doubt it in this case: each of the render targets (the 3D panel "overlay" and the popped out window) are not allocating any resources "per frame". In other words, once created, they are pretty much not allocating anything. Furthermore, the code running behind the popup or the popped out window is the very same. The only difference is an X-Plane flag telling whether the window is popup or popped out. Quite confusing but I'd think it is something related to X-Plane popped out windows internally, or maybe something system wide which is hooking on any window and which is causing this memory leak/growth over time? Something you might want to try: running in the configuration 3D+Popped-out, when you start experiencing the issue, go to the RXP menu and change the window from popped-out to popup, then observe whether you restore perf/memory, then change it back from popup to popped-out, and observe if memory grows again. With this information I shall be able to file a report to LR.