joomie

What planes for X-Plane support GTN 650/750 VC integration?

Recommended Posts

Can this one or any other device from RealityXP get fully integrated into a virtual 3D cockpit in X-Plane?

I used Google for two hours now and find no description/ how to guide to estimate if I can do that.

I read that it is possible in the PilotEdge forum. But I've no clue, how difficult that would be.

 

My interest is to put such a device into the 3D cockpit of the Carenado SR22T aircraft.

 

Second question is how regular one can update the database for the tool and how much that cost?

 

Many thanks and cheers,

joomie

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Does anyone have a list of which planes support these 2 units for direct virtual cockpit integration and not as a 2D pop-up panel?

Share this post


Link to post
Share on other sites

Very interested in this answer myself, newly adopted xplane user here and cant do without my trusty gtn 750 from FSX. Its a perfect addition to my A2A GA aircraft.

Share this post


Link to post
Share on other sites

Support for direct 3D cockpit is included, provided you manually edit the RealityXP.GTN.INI file in your aircraft folder.

 

This gives you the means to literally tell the plugin where (pos + size) to 'paint' the gauge on the panel. You just need to type in the 3D panel coordinates and the GTN plugin will just paint it there.

 

Otherwise, it requires 3rd party vendors to model the GTN in 3D (polygons + texture). This gives you the integration in the 3D cockpit in full 3D.

 

Nevertheless, we are looking at alternative ways to support universal 3D cockpit integration but this will have to wait until after we release our new GNS WAAS simulation product.

Share this post


Link to post
Share on other sites

Thanks for the reply Jean-Luc, I'm particularly interested in which vendors have already modelled the unit in 3D so I don't have fiddle about editing files?  I've search extensively for vendors with full 3D integration but come up short so far.

Share this post


Link to post
Share on other sites

The product is brand new, and with XP11, I guess most vendors are really busy porting their aircraft to this new version first. Once settled, I 'm sure more aircraft will be pre-configured. What I'm sure is that the more vocal our customers are, the greater the chances!

Share this post


Link to post
Share on other sites

The product is brand new, and with XP11, I guess most vendors are really busy porting their aircraft to this new version first. Once settled, I 'm sure more aircraft will be pre-configured. What I'm sure is that the more vocal our customers are, the greater the chances!

 

Are there any more detailed information available for developers on what is needed for VC integration? Modelling the frame is not the problem, but how do we map the GTN panels onto the 3D object? And are there custom commands your GTN provides we need to map to the manipulators?

Share this post


Link to post
Share on other sites

Yes Mario the information is available!

 

First, you can see all the exported commands in the user's manual (p. 8) or explore them via the X-Plane 'commands' interface. As for the 'panel' it is also documented in the user's manual (p. 6).

 

Last but not least, the GTN also publishes custom datarefs for advanced/custom integration with custom HSI/NAV display. Also in the user's manual! (p. 9)

 

This shall get you covered, and if not, you can always contact RXP via the website!

Share this post


Link to post
Share on other sites

Could you please give a little more detail in how to enable the 3D panel within the RealityXP.GTN.INI file? I've tried a few different variables such as adding the below entry at the bottom of the file, however I can't see the gauge overlayed within the VC.

 

[GTN_650_1.PANEL3D]
; display window if true.
visible = true
; show screen only gauge if true.
nobezel = true
; display type: WINDOW,PANEL2D,PANEL3D
frame.type = PANEL3D
; display position and dimension (left,top,width,height)
frame.rect = 0,0,678,285
; freeze display position if true.
frame.lock = false
; screen only border size (pixels).
border.size = 0
; screen only border color (#RGB or #RGBA).
border.rgba = #000000

Share this post


Link to post
Share on other sites

 

 


frame.rect = 0,0,678,285

 

You may find that this should be :-

frame.rect = 0,1024,678,285

 

As 0,0 is left.bottom of texture.

Share this post


Link to post
Share on other sites

I have tried every combination of numbers and configurations, but maybe it just won't do what I think it should. Do I need to go into Planemaker to make adjustments, or should this be just a simple  add-in of the PANEL3D code?

 

Bluebell2, I saw your other post and related video. Did you have to go into Planemaker to make any adjustments or remove other instruments first? I even used your GTN.INI file (converting from 750 to 650), and it still doesn't show up anywhere in my 3D cockpit. Do I need to enable something within the plugin menu? The windowed mode works fine, but I just want to cover up/overlay the GNS 430 gauges.

 

Thanks!

Share this post


Link to post
Share on other sites

Bluebell2, I saw your other post and related video. Did you have to go into Planemaker to make any adjustments or remove other instruments first? I even used your GTN.INI file (converting from 750 to 650), and it still doesn't show up anywhere in my 3D cockpit. Do I need to enable something within the plugin menu? The windowed mode works fine, but I just want to cover up/overlay the GNS 430 gauges.

 

It is not just a simple matter of editing the GTN.ini file.

First you need space on the cockpit_3d\-PANELS-\Panel.png texture for the GTN screen that does not overlap any other gauge. this is the reference to

; display position and dimension (left,top,width,height)

frame.rect = 0,1024,678,285

You can use the position of the GNS430 but you then need to remove the old GNS430 or hide it.

You need to edit the Aircraftname_cockpit.obj file with Blender or AC3D to add the screen.

You also need to use Blender or AC3D to add the GTN650 3D object to right position in 3D cockpit.

Then Planemaker to add the GTN650.obj and adjust 3D panel.

 

Hard just to explain on a forum post, here is an example of adding GNS430/530.

http://forums.x-plane.org/index.php?/forums/topic/77414-how-to-add-the-new-arinc424-gns430530s-to-the-732/

 

Also.

 

HAPPY NEW YEAR,

TOM.

Share this post


Link to post
Share on other sites

Thanks so much for the detailed information, Tom! Now I know what I'll be doing on my holiday today! :smile:

 

I'll report back on my progress. Happy New Year as well!

Share this post


Link to post
Share on other sites

Success! Well...ignoring the old GNS 3D model in the stack, but the GTN 650 shines through! :smile:

 

YNE7jsB.jpg

 

Now all I need is a 3D model of a GTN 650, and we'll have a significant upgrade for this old bird. Thanks again for the tips, Tom!

Share this post


Link to post
Share on other sites

This is looking nice, and will fit with our new GNS WAAS for XPlane too.

 

Thank you for sharing!

Share this post


Link to post
Share on other sites

 

 


Now all I need is a 3D model of a GTN 650, and we'll have a significant upgrade for this old bird. Thanks again for the tips, Tom!

 

Now this is nice. Creating a 3D model should not be difficult.

Share this post


Link to post
Share on other sites

Can I use it on XP10 with Carenado Seneca V ? Does it will interact with carenado G500 ?

Share this post


Link to post
Share on other sites

Hi all,

    I tried to do a vc install of the gtn 750 into the default xplane 11 baron 58 using the ini file(s) listed earlier in this post and the best I can get is that I can see the top left corner (comm area) of the gtn 750 inside the lower right area of the default garmin 530 screen, and clicking on it works...the freqs change n stuff....but no matter how I have tried changing the  frame.rect values it does not move any further over/up.  Also...bringing up a popup window does not work at all yet.  

I use xplane in VR with occulus rift and fly-inside and for some reason, unlike other external windows, the  window for the gtn 750 cannot be imported into Vr, so the only way to use it seems to be if I can install it in the VC....I do see the corner of the gtn 750 in VR as well as without Vr...

Thanks in advance....any help from the pros will be greatly appreciated...I am brand new to this and to doing anything with the planemaker app but willng to try if that is what it takes...  

tim   

 

Share this post


Link to post
Share on other sites

Hi Tim,

The popup window is not different than any other window and should display like any other too. However, v2.4.9 RC uses a different type of X-Plane SDK window as a first step toward supporting XP 11.1 pop out windows (it won't pop out yet, but the code is preparing the change). Do you mean when using VR, the popup window won't show even with v2.4.9 RC? It might be a limitation of 11.1beta for now.

Nevertheless, adding a 'rendering view' of the GTN in the 3D cockpit requires having a 'rendering surface' already defined in the 3D panel, as X-Plane, unlike FltSim, doesn't allow one to simply 'add' a gauge in the cockpit, simply because there are no gauges in X-Plane, but plugin code rendering every frame instead. This is why we have to resort to our configuration file (RealityXP.GTN.ini) which has provisions to setup additional rendering views. These in turn gives instructions to our plugin to draw what and where when X-Plane tells our plugin it is time to draw.

You might want to download our GNS User's Manual from our web site and read the Baron 58 tutorial. This will give you essential knowledge about this process.

Share this post


Link to post
Share on other sites

Hi, 

Thanks for the  quick reply...

Lets see....first, I am using XPlane 11.10 with the latest 1.83 version of fly-inside....works very well. 

Yes, when in VR clicking on the visible corner of the Gtn 750 I see will activate the buttons but it does not pop out to become more readable...no sure if it is supposed to or if it is not just because my gtn 750 VC install is not correct.  Thats kind of a secondary problem right now....after just getting the VC installed...but is important eventually because if the gtn750 is like the g1000 glass cockpits, it wont be very clear in Vr without the popout. I just purchased the Gtn750 two days ago for this purpose so I'm pretty sure I have the latest....at least trying to update said I did....

Not sure what needs to be done to have a 'rendering surface' already defined in the 3D panel...I saw that I can drag n' drop a garmin 530 onto the 3d panel inside Planemaker....but if that is what you mean...don't I have to get a Gtn 750 representation into the cockpit equipment dock for that?  I don't know how to do that at this point...I'm brand new with planemaker....or is that something that has to be done with an app like Blender which I see mentioned here and there on the forums (Been looking at a lot of forum messages for the last two days!).

I thought I had the GNS users manual already and read through it a couple of times but did not see a Baron 58 tutorial....maybe I'm looking at the wrong doc?  I downloaded it when i downloaded the app.  I will look again because that may be just what I'm looking for.  

 

Additionally, in case it helps you guys, and just FYI...most apps like mapping apps or text files etc...just about anything launched outside of fly-inside/Xplane but visible on the desktop, can be 'imported' into VR and should up 'floating' in the cockpit.  For some reason that does not work with the Gtn750...when you select the import window feature in VR the Gtn750 does not show up in the list of available windows to be imported....Not sure why..,

Thanks again for the prompt reply...really appreciate it and I hope you can understand my 'jargon'...

tim

 

 

 

Share this post


Link to post
Share on other sites

Hi Tim,

The version from the website is v2.4.8. The first topic in this forum has the link to download v2.4.9 RC (release candidate). The 'RC' has the different window scheme I'm mentioning.

The GTN displays in-sim, in a X-Plane controlled window. It is not an operating system window. Their latest SDK and 11.1 now offers the tools for popping out the windows (like their default GPS) but it is not implemented yet in the GTN because XP11.1 is a beta and not all is working. Once XP11.1 is official out of beta, we'll follow through with the update to the GTN to support the pop out windows (if we managed to, so far it looks promising though).

I'm referring to the GNS User's Manual for X-Plane, not the GTN User's Manual.

 

Share this post


Link to post
Share on other sites

Hi,

Sorry, I didn't realize the release candidates were not included or mentioned as available from the upgrade selection.  I will dl that version and give it a try when I get back home.  If it is put into a window I should be able to suck it into vr and use it as I do the map apps I'm using now.  That would be perfectly usable until the pop out update is complete.  It should have occurred to me that that window was a self running app and not inside a window...  If your looking for beta testers (in VR) for your pop-up work, I would be happy to help....

  With the new update, do I still need to enter the frame.rect  info or does the plugin figure that out now? 

The guide I have been looking at is a 17 page doc I got from the RealityXp website.  I don't remember the exact title...

Thank you, I can't wait to give it a try!

tim

 

 

Share this post


Link to post
Share on other sites

You'll find the tutorial page 16 and 17 of the GNS V2 X-Plane User's Manual.

The plugin 'rendering' settings don't change with v2.4.9 either. You still tell X-Plane where to render using the frame.rect entry!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now