GTN 750 and P3D5.2

[MkIV Hvd]

Part of the realism is entering the plan yourself. Real world pilots have to. Just mark your way points when you set your plan in sim for ATC and then punch them into your GTN. A lot easier than the virtual or real cursor dials on GNS units.

The touch screen is definitely better than twisting knobs! Real pilots though, don't necessarily have to manually enter flight plans. They have the ability to pre-plan and save on a memory card, which is what the LittleNavMap process would replicate for us in the sim here.

I have a RXP GTN 650 and a 750, and here's how I load flight plans, using Little Nav Map (LNV):

Paughco, thanks very much for the tutorial! I'd lost it and just found again it this morning. I know you've mentioned LNM lots and I've had it for months, but only started using it recently. What a great program!! I'm only using a fraction of its capabilities I'm sure, but whether IFR or VFR it's always running now. Have you run into any issues with duplicate waypoints locking the flightplan for use in the GTNs until removed or corrected, as happens sometimes with Simbrief flightplans?

Cheers,
Rob

[Paughco]

Locked waypoints happen all too frequently. Sometimes it's because an airport, navaid, or waypoint in LNV isn't present in the GTN database. Other times it's because there is more than one airport, navaid, or waypoint with the same name as the one in your flight plan. So when a flight plan contains locked points, I first try editing it by inserting the exact name either before or after the locked waypoint. About half the time my required waypoint shows up, so I insert that in the flight plan and delete the locked waypoint. Other times that doesn't work, so I go back to LNV and save a user waypoint right near the bogus waypoint in LNV, then save the new flight plan using the previously described process to get it into the GTN directory. This doesn't work if the locked point is the final destination, so I just add a nearby airport as the final destination, but I still land at the airport I want, so long as it's visible in P3D (now v3.5 for me!).

Once I was leading a MP flight out of Blue Canyon-Nyack (KBLU), low and slow through the Sierra mountains, up to Susanville Mun (KSVE), with a stop at this tiny little strip on a mountain ridge, Milhous Ranch (79CL). 79CL wasn't in my GTN database. I tried to add in a new waypoint on my GTN by editing the route graphically, but you can only do that if you already have a waypoint upon which to drag and drop the route. OK. I set up a new user waypoint at the approximate location of 79CL, and then edited that waypoint. I don't have P3D or my GTN running now, so I can't give an exact description of the process, but I was able to select an airport icon for my waypoint, give it the name Milhous, and finally I was able to tweak the coordinates so they exactly matched the coordinates of the actual airstrip! Once the waypoint was set up, I graphically edited my flight plan to include it. Managed to get into and out of there in my A2A Cessna 182. The MP flight went off very well.

Glad you've got your system working.

Seeya
ATB

[bullfox]

I had the Reality GTN 750 working fine in P3D5.2 but in 5.3 I cannot get it to intercept the GPS course.

[Paughco]

There’s a recent update for 5.3 compatibility.

[bullfox]

Well, I finally got the Reality GTN 750 to follow the magenta line in P3d5.3. I had deleted it completely and lost my reg key. but the Flight 1 site still had the purchase info and I was able to redownload the 750 without having to pay another $35.00. However, the install had not been updated with the new version for P3D5.3 so I had to download that and install it to get the unit working. My test airplane for all this was the Carenado B120. Now If I can just get the Reality 750 to work in the Comanche.

[Paughco]

Here's how I got the GTN working in my A2A aircraft: viewtopic.php?f=124&t=69395. Scroll down a ways for the full-on description. There's a file that can be downloaded from Dropbox, that, with a bit of finaggling, you can get the buttons working on your GTN.

Only thing is, you have to double click the buttons to get 'em to work. For example, to get the RXP GTN 750 in my Comanche to go direct to the map display, I have to double-click the menu button and hold it down on the second click.

I also have a GTN 750 2D window in my B-17 and in my MJ C-47.

Seeya
ATB

[bullfox]

I got the Reality GTN 750 working in the Comanche but could not get the pop up 750 to appear and disappear in response to key board commands although it responds to mouse clicks. I used the add on RXP GTN configurator.

[Paughco]

The only way I know to get the pop-up to work is to click on the left side of the frame or bezel, in the area below what looks like a slot for a micro SD card and to the left of the back button. Click on the one in your instrument panel to get the pop-up. You have to click in the on same spot on the GTN in your panel to get it to go away. I find the pop-up to be useful when you're trying to mess with the GTN when you're flying through bumpy air.

Seeya
ATB

[MkIV Hvd]

Locked waypoints happen all too frequently. Sometimes it's because an airport, navaid, or waypoint in LNV isn't present in the GTN database. Other times it's because there is more than one airport, navaid, or waypoint with the same name as the one in your flight plan.

Thanks for the heads up! I've found that the locked waypoints I've seen are always because of duplication, but once you get to the point of having to edit the saved plan to make it useable, it sometimes seems more of a pain than just entering them manually. However, I've gone ahead and used the LNM flight planner for the last two weeks and haven't had the issue...brilliant!! VFR or IFR, it's active on every flight! I even set it up to fail once when I noticed a duplicate navaid on a route I wanted to fly, so let LNM set up the flight plan, saved and loaded into the GTN without a hiccup. I'm glad you've mentioned LNM enough that I finally went all in...thanks!

Here's how I got the GTN working in my A2A aircraft: viewtopic.php?f=124&t=69395. Scroll down a ways for the full-on description. There's a file that can be downloaded from Dropbox, that, with a bit of finaggling, you can get the buttons working on your GTN.
Only thing is, you have to double click the buttons to get 'em to work. For example, to get the RXP GTN 750 in my Comanche to go direct to the map display, I have to double-click the menu button and hold it down on the second click.

I fought with this for a while and just gave up. I could never get the buttons to work on the 650 in the Civ Mustang and the only one I really want is the DIRECT one, as the other functions can be accessed in other ways anyway. As you brought it up, this appears to be a different thread path for assistance, so I'm going to try it again...not for too long, but I will try...

Cheers,
Rob

[Paughco]

Rob: You have to double-click all the buttons on every A2A aircraft except for the Bonanza. I can get the GTN 650 in my Civ Mustang to show the map by double clicking and holding the left mouse button down on the menu button. It's been a whjle since I worked on getting either the GTN 650 or GTN 750 working in my A2A aircraft (except for the Cub, Spitfire, and the P-40), but I recall starting by copying RealityXP.GTN.ini from my "C:\Users\MyName\Documents\Prepar3D v5 Add-ons\A2A\SimObjects\Airplanes\A2A_Beechcraft_35_Bonanza\" folder into the appropriate P-51 aircraft folder. Then I selected the F1 GTN in the aircraft P-51 configurator, and went through the rest of the modifying process described in previous posts.

I've got the file f1vc.xml in my "C:\Users\MyName\Documents\Prepar3D v5 Add-ons\A2A\SimObjects\Airplanes\WoP3_P51D_civ\panel" folder. Here's f1vc.xml, in Wordpad, showing the button mod:

============ begin f1vc.xml =================
<Gauge Name="f1vc" Version="2.04">

<!-- Reality XP GTN Buttons Bridge -->
<!-- Bridges Reality XP GTN 750/650 Touch with f1 3D bezel -->
<!-- Credits: Reality XP, Sean Moloney and Ryan Butterworth -->

<Element>
<Select>
<Value>
(L:F1GTNMOUSE,bool) 0 !=
if{
(L:F1GTNMOUSE,bool) 0x0001FA01 - sp0
l0 28 / int sp1 l0 28 % sp0
<!-- map F1 model to RXP GTN unit -->
<!-- use: 8 0 8 0 for 652=unit2, 651=unit1, 752=unit2, 751=unit1 -->
<!-- use: 8 8 0 0 for 652=unit2, 651=unit2, 752=unit1, 751=unit1 -->
8 0 8 0
4 l1 case 4 2 l0 1 &amp; ? + sp1
l0 0 == l0 1 == or if{ l1 (>K:GPS_MENU_BUTTON) }
l0 2 == l0 3 == or if{ l1 (>K:GPS_DIRECTTO_BUTTON) }
l0 4 == l0 10 == or if{ l1 8 &amp; (>K:GPS_BUTTON2) }
l0 6 == l0 11 == or if{ l1 8 &amp; (>K:GPS_BUTTON3) }
l0 8 == l0 9 == or if{ l1 (>K:GPS_BUTTON1) }
l0 12 == l0 18 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_DEC) }
l0 14 == l0 19 == or if{ l1 8 &amp; (>K:GPS_GROUP_KNOB_INC) }
l0 20 == l0 26 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_DEC) }
l0 22 == l0 27 == or if{ l1 8 &amp; (>K:GPS_PAGE_KNOB_INC) }
l0 24 == l0 25 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }
l0 16 == l0 17 == or if{ l1 (>K:GPS_CURSOR_BUTTON) }
0 (>L:F1GTNMOUSE,bool)
}
</Value>
</Select>
</Element>
</Gauge>

======================== end f1vc.xml =====================

Here's my panel.cfg for the Civ Mustang (I tried to bold all the references to GTNs):

========= begin panel.cfg ===================
// F1650
[Window Titles]
Window00=Main Panel
Window01=Clipboard
Window02=Mini Controls
Window03=Payload and Fuel Manager
Window04=Map
Window05=Radios
Window06=Maintenance Hangar
Window07=GPS
Window08=AFK
Window09=none2
Window10=dbg
Window11=none3
Window12=none4
Window13=GTN 650

[VIEWS]
VIEW_FORWARD_WINDOWS=10,20,30,FUEL_PANEL,50,51,52,53,54,100,101,102,103

//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1024,768
position=1
visible=1
ident=10

// gauge00=tester!tester, 420, 50, 400, 1000 //Comment for release


[Window01]
Background_color=0,0,0
size_mm=322,615
pixel_size=322,615
window_pos= 0.0, 0.2
position=0
visible=0
ident=20
sizable=0

gauge00=WoP3_p51d!clipboard, 1,0,322,615

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.12, -0.60, 0.32
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 15 ,0 ,0
3DP_SIZE = 0.35, 0.35
3DP_CAMERA_TRANSFORM_REFERENCE = CAMERA

[Window02]
Background_color=0,0,0
size_mm=321,376
pixel_size=321,376
window_pos= 0.51, 0.2
position=0
visible=0
ident=30
sizable=0
gauge00=WoP3_p51d!controls, 1,0,321,376

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = -0.12, -0.45, 0.35
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 15 ,0 ,0
3DP_SIZE = 0.20, 0.20
3DP_CAMERA_TRANSFORM_REFERENCE = CAMERA

[Window03]
Background_color=0,0,0
size_mm=649,689
pixel_size=649,689
window_pos= 0.51, 0.2
position=1
visible=1
ident=FUEL_PANEL
sizable=0

gauge00=WoP3_p51d!manager, 1,0,649,689

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.45, -0.35, 0.1
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,60
3DP_SIZE = 0.35, 0.35
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

[Window04]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=1
ident=50
sizable=0

gauge00=WoP3_p51d!mapscreen, 255,1,770,766
gauge01=WoP3_p51d!map_settings, 1,50,246,232

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.0, -0.55, 0.20
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 35 ,0 ,0
3DP_SIZE = 0.35, 0.35
3DP_CAMERA_TRANSFORM_REFERENCE = CAMERA

[Window05]
Background_color=0,0,0
size_mm=187,252
pixel_size=187,252
position=6
window_pos= 0.025, 0.9
visible=1
ident=51
sizable=0

gauge00=civ!radios, 1,0,

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = -0.20, -0.25, 0.40
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,-20
3DP_SIZE = 0.15, 0.15
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA


[Window06]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=52
sizable=0

gauge00=WoP3_p51d!maint_hangar, 1,0,1024,768

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = -0.44, -0.30, 0.1
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,-60
3DP_SIZE = 0.4, 0.4
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

[Window07]
Background_color=0,0,0
size_mm=420,217
position=8
visible=0
ident=53
sizable=0
nomenu=0

gauge00=civ!gns_400, 0,0,420,217
gauge01=civ!gps_500, 103,27,310,225

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.00, -0.20, 0.45
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,0
3DP_SIZE = 0.25, 0.25
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

[Window08]
Background_color=0,0,0
size_mm=321,321
pixel_size=321,321
position=5
visible=1
ident=54
sizable=0

gauge00=civ!afk, 1,1,321,321

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.20, -0.25, 0.40
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,20
3DP_SIZE = 0.13, 0.13
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

[Window09]
Background_color=0,0,0
ident=100
render_3d_window=1
nomenu=1
type=special

gauge00=WoP3_p51d!keys, 1,1,1,1
//gauge01=WoP3_p51d!cockpitBuilder, 2,2,2,2 //Disable VC - for cockpit builders.

[Window10]
Background_color=0,0,0
size_mm=330,450
pixel_size=330,450
position=5
visible=0
nomenu=1
ident=101
sizable=0

// gauge00=dbg!panel, 144,0 //Comment for release

[Window11]
Background_color=1,1,1
ident=102
window_size=1.000,1.000
nomenu=1
zorder=100

gauge00=WoP3_p51d!blackout, 0,0

[Window12]
Background_color=0,0,0
size_mm=685,685
pixel_size=685,685
position=3
visible=0
ident=103
nomenu=1
zorder=99

gauge00=WoP3_p51d!engine_details, 1,1,685,685

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.40, -0.40, 0.1
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 20 ,0 ,60
3DP_SIZE = 0.4, 0.4
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

[Window13]
Background_color=0,0,0
size_mm=937,390
ident=14403
window_pos= 0.660, 0.740
window_size= 0.340, 0.260
zorder=99
gauge00=rxpGTN!GTN_650_1, 0, 0,937,390

;POS: LR/TD/FA
3DP_WORLDSPACE_POS_OFFSET = 0.00, -0.20, 0.45
;PBH: pitch, roll, yaw
3DP_PBH_OFFSET = 0 ,0 ,0
3DP_SIZE = 0.25, 0.25
3DP_CAMERA_TRANSFORM_REFERENCE=CAMERA

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=512,512
visible=1
pixel_size=640,640
texture=$reticle

gauge00=WoP3_P51D!GPS_F1_650, 1, 1, 1, 1
gauge01=WoP3_p51d!code_r, 1,1,1,1
gauge02=WoP3_p51d!status1,2,2,2,2
gauge03=WoP3_p51d!damage, 3,3,3,3
gauge04=accusim_xml!code_s,4 4,4,4,4
gauge05=A2A_Accusim!lua, 5,5,5,5
gauge06=A2A_Accusim!AVS, 6,6,6,6
gauge07=A2A_Accusim!events, 7,7,7,7
gauge08=A2A_Accusim!random, 8,8,8,8
gauge09=A2A_Accusim!storage, 9,9,9,9
gauge12=WoP3_p51d!number, 384,384,128,28
gauge13=WoP3_p51d!number2,256,384,128,64
gauge14=p51!avionics, 0,0,512,384
gauge15=civ!autopilot, 10,10,10,10
gauge16=civ!oat, 256,449,185,62


[Vcockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN650
background_color=0,0,0

gauge00=rxpGTN!GTN_650_1, 0, 0,677,297,NO_BEZEL
gauge01=!f1vc,0,0,1,1

[Vcockpit02]
Background_color=0,0,0
size_mm=2048,2048
visible=0
pixel_size=2048,2048
texture=$rain
gauge00=Windshield!main,0,0,0,0
texture00=Windshield, 0,0,2048,2048

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

=========== end panel.cfg ========================

Hope that helps.

Seeya
ATB

[MkIV Hvd]

Paughco,

Thanks very much for detailing that process, I'll give it another shot this afternoon! Going through the install process with F1 and the RXP change tool was easy...getting the dang DIRECT TO button to work, not so much!

Cheers,
Rob

[twsharp12]

Petition for A2A to put the Reality GTN into all the A2A configurators since Flight1 is no longer supported. It's only in the Bonanza.

[MkIV Hvd]

Petition for A2A to put the Reality GTN into all the A2A configurators since Flight1 is no longer supported. It's only in the Bonanza.

Where do I sign!!!!!

Paughco, thanks again man, I tried but no joy still. My files all match yours, so I'm likely missing a step, but I don't care anymore...until A2A decides to support the RXP GTN in all their airplanes per the petition
Until then, it's only one button and there are ways around not having the DIRECT TO function.

Cheers & Happy New Year!!
Rob

[Paughco]

Try activating the 2D version and see if the buttons work.

[bullfox]

An update to support the Reality GTN across the board is a great idea!