Hi,

I recently bought the amazing Thandra Beaver for XP11 and it comes with a built in integration for the RXP GNS750, however not for the GNS530/GNS430. 

I tried to make a compatibility file according to the RXP Baron tutorial, however I realized that the Beaver does not save the screens of the GNS as other aircraft as it includes a special cockpit customization option.

The developer also confirmed that as you can see on this thread: 

RealityXP GNS ? - Thranda DHC-2 Beaver - X-Plane.Org Forum (x-plane.org)

I'd glad to know if we can make the GNS RXP to work with this aircraft

Thank you for your time!

Seconded. Hope this is doable 🙂

Got my vote. Fabulous plane GTN just doesn't look right. Cheers 

+another vote for this, big time ...

I’m right on the verge of plunging down the whole RXP and RealSimGear rabbit hole for a 430 and/or 530 setup, inspired by the new Thandra Beaver ... sad to hear it might not be supported at the moment.  Pleeeeeeease let me give you all my money!

And specifically, for the RXP folks, the question comes down to how flexible their architecture is with different (apparently non-standard?) sorts of render targets, as discussed in this post:  

Link

Hopefully this is something doable.  I’m actually not a huge consumer of their hyper-customizable instrument panel, so I hope that that customizability doesn’t end up hosing a scenario that frankly seems more more core (or at least, more core to me. :))

Yeah, so basically the Thranda folks have said they haven’t gotten enough questions about this so it’s a non-priority for them.  It’s a *bit* of a misrepresentation, as there’s the 4 of us here, plus I found several other threads rather easily for the Pilatus (which has the same powerful-yet-inexplicably-limiting custom panel designer) asking the same thing.  
 

So I guess the question comes back to you guys with RXP - how easy is it to enable, ASSUMING it’s even possible, and how much would it be worth to do it?

I still wait for @RXP to comment on this. Would like to hear his opinion. 

Weekly bump on this question, hoping that @RXP weighs in now that the seasonal festivities are more or less over ...

I'm sorry for the late answer on this topic.

To make it simple: you can't configure the GNS or the GTN to draw on anything other than the panel texture (as shown via panel_preview.png) because this is the only rendering surface which is supported by the XP11 SDK.

XP11 is giving a 1st class citizen treatment to their GNS via a dedicated FBO and 3rd party plugins are excluded from them, and they make it clear we shouldn't interfere with them because these are internal and subject to change (even more so with Vulkan).

I've been asking for custom rendering surface to the XP11 devs for ages (since XP9) and they've never came up with a solution all this time.

The easiest for this aircraft would just be it includes a space to rendering the GNS in the panel_preview.png, with a 3D polygon UV mapping this texture onto the panel where you'd render the GNS. This is not much to add when you're in the modeling tool as far as I understand, and with some hacks you might even be able to merge/embed it in the existing model/obj files manually (but it will be tedious).

I don't know how this specific aircraft is modeled, but if Joseph's comment "we're using the X-Plane GNS 430 and 530 units as external objects that are added in to the panel afterward, rather than using them as integrated on the panel" means they are external .obj files attached to the aircraft (standard XP11 way as seen in plane maker) I'd guess nothing would preclude adding a GNS .obj file which screen polys would be UV mapping the standard panel_preview.png texture?!?

Just checking in on this ... @RXP, did the Thranda guys ever reach out and start a conversation about how to accomplish this?  I’m definitely still interested in jumping off the default X-Plane 530 if I can get it working with the Thranda (kinda the only XP aircraft I’m still flying at this point ...), as my RealSimGear 530 is in the mail ...