DRS

I have been working on this issue and at least have a direction as to what needs to be done. It is a bit beyond the scope of what I am familiar with but I thought I would post my findings in the hope that either someone or perhaps RXP can figure out a solution for this. I sent my question to Austin and he forwarded it to Philipp Ringler who provided me with this answer. Timely responses from both of them. "The reason is, the X-Plane 12 C172 doesn't _have_ a 3d panel. Shift+Ctrl+Alt+Space only works for planes that have a panel texture that is mapped to the 3d panel. The screens are made as 3d objects with a "device surface" - a screen that is directly mapped to an avionics device. The advantage of this technique is it saves both on VRAM and fps, because the intermediate copying into the panel.png is no longer necessary. In the old style, the pixel would be copied from the avionics device screen first onto the panel.png, and then that would in turn be copied onto a 3d object that makes your virtual cockpit. These two copies both take time (frames) and memory (VRAM). The new style is much more efficient, because it only copies pixels once, from the avionics device to the surface of the 3d object. These "device surfaces" for objects have been introduced in X-Plane 11, and in X-Plane 12 they are open to third-party developers like Reality XP as well. In X-Plane 11, if you wanted a third-party device you had no choice but to use the old, slow, two-copies method - the third party would go via the panel texture. In X-Plane 12, third parties can instead access the frame buffer directly, and enjoy the new, faster path, the same as X-Plane's own devices. This is explained in detail here: https://developer.x-plane.com/sdk/XPLMDisplay/#AVIONICS_API This is technical documentation for developers, you don't need to understand that, but developers of plugins for X-Plane 12 should understand that. The X-Plane 12 C172 is obviously build with the new technique, it doesn't use panel copying. Therefore, it will work fine with third-party devices that use the new callbacks. It won't work with third party plugins that rely on panel copying. I am not up to speed on third party developments, so I don't know if Reality XP has an X-Plane 12 version of their GPSs that works with the callback method as opposed to the panel method. A cursory glance at their homepage looks like their GNSs claim to be X-Plane 12 compatible, but of course they don't say which version of drawing they are using. It might be worth asking them and asking whether they support the new X-Plane 12 API. If they do, this is both faster with fps, uses less VRAM, and will work with airplanes that are authored in a modern way."

Here is the GNS.ini file to implement the 530/430 into the new TOGA Simulations MU-2 Marquise v2 panel. I have also set up both units to link to their respective VOR 1/2 and enabled crossfill in the RXP settings. You may want to adjust these to your personal preference. Enjoy!

I think the issue is the folder path. My stuff shows up in the same path as yours except the Folder is 'LocalState' NOT 'LocalCache'. Try moving the 414 folder from the LocalCache to the LocalState and see if the plane shows up.

Mine shows up with the Search terms of both "Cessna 414" and just "414". Knowing you are an FSEconomy user, is it possible that you have some other aircraft aliased with the same name? That can make things disappear. You could also try removing all other things from your Community folder and leave just the 414 in there and see what happens. The MSFS Addons Linker on Flightsim.to works great for stuff like that.

Regarding the new backgrounds and text layout for the AP and Transponder, all the TDS GTN liveries have the new black backgrounds and text formatting changes while all the PMS GTN ones still have the blue background on the AP and the yellow background and old style text/ spacing.

I tried turning off the AP, FD, YD buttons on the left side of the AP and all the yellow lights extinguished. The GPS will still only arm and only HDG or ROL will go active. Doing a Direct-TO in the GPS to the next waypoint draws the magenta line correctly on the GTN but it will not follow it. The same issue occurs when going to VLOC manually on the GTN for doing an ILS approach. LOC and GS show as armed, The localizer and glideslope needles show correctly on the HSI. The localizer captured but then it flew through LOC went from armed to active and then back to armed once the needle fully deflected the other way. It zig zaged back and forth through the localizer and in the process GS never went active or was captured. I manually flew it and got back on profile and on glideslope and then LOC and GS went from armed to active. I have done successful LPV and ILS approaches earlier today but that was on flights after a fresh start of the sim. I am going to try with the PMS version and see what results I get with multiple flights.

I am having an issue with the TDS GTN model. I can do a successful flight using the GPS and it works great following the flight plan and doing an approach. Once I land and do another flight without shutting down the plane and restarting, just leaving the engines running and do another flight (FSEconomy flying). ROL or HDG is the only mode that will go active and GPS will show as armed but won't go active, and it won't follow the new flight plan entered into the GTN. The only remedy I have found is to shut down the TDS app via Task Manager and then restarting it. Then things work normally again. This may be a TDS issue but I thought I would see here if anyone else is having this issue and if not I will ask in the TDS Discord. I have the latest version of the TDS.

Great aircraft! Really enjoying the first couple of flights. Is there a list of the various custom commands, events, that are used so things can be set up to work with various hardware panels, Streamdeck, Spad.next?

I have solved the problem but another question has come up. There was a flight plan in the flightplan folder: C:\ProgramData\Garmin\GNS Trainer Data\GNS\FPL. Once I removed that things start correctly. The only issue is it always starts on the import flight plan page and it didn't do that before. Any ideas on how to get it to start on the map page?

My GNS 430 and 530 both freeze and crash Xplane after clicking ok at the self-test screen. As seen in the photo the radio frequency panel opens on the left side and then the freeze occurs. I have uninstalled and reinstalled both the 430 & 530 as well as the Garmin Trainer Lite. Re-run the Xplane installer. This happens on both 11.41 and 11.50b17 and also b13 which I was using before the upgrade to b17. I have removed all plugins from the plugin folder and still the same result. I also have the GTN 650/750 installed and they work without issue, likely as it is a different trainer involved. All Windows updates are current except the 2004 update. X-Plane log file doesn't seem to shed any light on things either. I think it is some issue with this particular machine as everything works fine on my backup install on my laptop. Not sure when things stopped working properly but they did work fine a month or so ago. Just wondering if anyone else has experienced this or has any ideas aside from a complete Xplane reinstall?

Airfoillabs C172 - GNS 430 Panel Config My first attempt at doing one myself as I couldn't find one for this model. Puts the GNS 430 screen in the 3D cockpit on the AFL 430 screen. I also enabled 'Use simulator GPS commands" and everything is working great!

Does the GTN 650/750 for P3D use the same Trainer version as the XPlane version? The XPlane version which I have seems to have just been upgraded and have more features than before and also is now better than the F1 version I have for P3D. With the sale on I would like to get the RXP versions for P3D if they will have the same upgraded features as the Xplane version. Thanks for a great product and looking forward to the G500/600 when it comes out!