Jump to content

Anyone done GTN 750 mods for this?


Recommended Posts

Posted

 I'm not sure how much actual net profit RA made when they redid the TDuke v2 with GTN integration.  

 

They got a purchase from me (FSX version) near a time when I need to build a new system and consider a move from FSX to P3D or SE. i.e I am not in the mood to purchase more items for my current FSX system. Their efforts also were a key influence for me to snag the GTN 750. Guess that's an example of trickle-down economics!

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

Posted

Ryan,

 

I got the (FSX) GTN750 display in the VC but pressing any GTN button brings up the default Garmin?

 

 

 

You'll have to email me or pm me... I'm off to work the night but maybe I can help tomorrow

| FAA ZMP |
| PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 32GB 5600 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

  • 2 months later...
  • 1 year later...
Posted
Quote

I got the (FSX) GTN750 display in the VC but pressing any GTN button brings up the default Garmin?

vonmar  Just on [Vcockpit02]  add the comment to gauge07   //gauge07=PA46350P!ToggleCAR530,      7,337,493,30

:blink:

  • 4 months later...
Posted
Quote

alexcunille: ... Just on [Vcockpit02]  add the comment to gauge07   //gauge07=PA46350P!ToggleCAR530,      7,337,493,30

you refer to a different aircraft: PA46 350 piston. 
Here is P46T Jetprop topic.

My suggestion:

  • GTN750 inside GNS530 bezel
  • GTN650 inside WX radar bezel
  • GNS430 original gauge: Unable to set GTN650 here

 

mgI56NI.jpg

[Vcockpit02]

Background_color=0,0,0 

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$Panel_2

 

gauge00=WX_Gauge_3D_P46T!WXGauge,  9,9,492,309

gauge01=Radio_P46T!RadioAdf,  524,670,496,100

gauge02=DIGTTRANS_P46T!transponder,  516,529,501,126

gauge03=Radio_P46T!RadioTrans,  520,126,496,112

gauge04=F1GTN!GTN750VC,  90,304,330,355,UNIT1

gauge05=GAUGEP46T!Gauge_Anum_R,  381,786,635,229

gauge06=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298

gauge07=F1GTN!GTN650VC,  579,295,448,181

 

 

Regards

Stefan

vpa558.png

Posted

Correction for the above panel.cfg for P46T Jetprop:

[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126
 

sorry

vpa558.png

Posted
On 9/29/2017 at 0:28 PM, wildtomcat said:

Correction for the above panel.cfg for P46T Jetprop:

[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126
 

sorry

Stefan,

Thanks.

Edit: I added the lines above to the panel.cfg. The 750 works fine but I cannot bring it up by clicking on it .The 650 does not work. I only see part of it inside the gns430 "frame" and clicking on it brings up the carenado gns430

Posted

I see. The clickspots in the GNS530 and 430 bezel are kind of hardcoded in the model, no gauges we can change. So the GTNs can´t be opened with clicks on them but with shift+4 and shift+5. Or by the GTN stack. I use buttons on my goflight panels for it.

Maybe I changed something in the other parts from panel.cfg, too. this is my complete panel.cfg:

[Window Titles]
Window00=G500
Window01=Toggle_Manual
Window02=Toggle_Control
Window03=Flight1 Garmin GTN750 U1 - DO NOT MODIFY
Window04=Flight1 Garmin GTN650 U2 - DO NOT MODIFY
Window05=INFO
Window06=GP430


[VIEWS]
VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=1024,1024
window_size_ratio=1.000  
position=8
visible=0
ident=MAIN_PANEL
window_size= 0.500, 0.666
window_pos= 0.010, 0.310
no_luminous=1

gauge00=G500_P46T!g500_config,  0,0,1,1
gauge01=G500_P46T!g500,  0,0,1024,1024
gauge02=PA46T!ToggleCARG500,  0,0,1024,50


//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=713,1000
position=0
visible=0
ident=793
window_size= 0.351, 0.817
window_pos= 0.520, 0.020
zorder=5

gauge00=PA46TManual!manual,  0,0,711,998


//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=500,261
position=0
visible=0
ident=796
window_size= 0.198, 0.137
window_pos= 0.010, 0.145
zorder=5

gauge00=PA46T!Control_windows,  0,0,500,261


//--------------------------------------------------------
[Window03]
Background_color=0,0,0 
size_mm=937,887
position=7
visible=1
ident=14401
window_size= 0.340, 0.580
window_pos= 0.000, 0.420
zorder=99

gauge00=F1GTN!GTN750,  0,0,937,887,UNIT1.POP


//--------------------------------------------------------
[Window04]
Background_color=0,0,0 
size_mm=937,390
position=7
visible=1
ident=14404
window_size= 0.340, 0.260
window_pos= 0.338, 0.740
zorder=99

gauge00=F1GTN!GTN650,  0,0,937,390,UNIT2.POP


//--------------------------------------------------------
[Window05]
file=info.bmp 
size_mm=419,181
window_size_ratio=1.000  
position=0
visible=1
ident=142
window_size= 0.250, 0.120
window_pos= 0.010, 0.020

//--------------------------------------------------------
[Window06]
Background_color=0,0,0 
size_mm=524,310
position=7
visible=0
ident=10010
window_size= 0.310, 0.300
window_pos= 0.525, 0.715
no_luminous=1
zorder=7

gauge00=GPS_430_3D_P46T!GNS430_nc2,  0,0,528,310
gauge01=PA46T!ToggleCAR430,  117,6,292,232


//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_1

gauge00=GAUGEP46T!Gauge_Eng13D,  768,343,256,343
gauge01=GAUGEP46T!Gauge_Eng23D,  768,0,256,343
gauge02=GAUGEP46T!Gauge_Volts_Amps,  7,521,318,279
gauge03=GAUGEP46T!Gauge_Anum_L,  87,805,328,212
gauge04=GAUGEP46T!Gauge_Button_Anum,  422,803,600,217
gauge05=GAUGEP46T!Gauge_Clock,  332,518,279,279
gauge06=PA46TJ!GPSVSI,  0,0,2,2


//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126


//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_3

gauge00=GAUGEP46T!Gauge_Autopiloto,  0,0,512,119
gauge01=GAUGEP46T!Gauge_Anum,  0,120,384,177
gauge02=GAUGEP46T!Gauge_Anum_APSEL,  0,299,384,174
gauge03=P46T_Cabin_alt!C340_PRESS,  0,0,1,1


//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_4

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_5

gauge00=G500_P46T!g500_config,  0,0,10,10
gauge01=G500_P46T!g500_3D,  0,0,768,515


Day=255,255,255
Night=223,255,255
Luminous=246,115,119

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

vpa558.png

  • 10 months later...
Posted

For anyone wondering, this plane works fantastic with the Flight 1 G500/600 Garmin gauge/trainer replacement with the above panel mods for the Flight 1 GTN-750.

Simply add the GTN750 using the Flight 1 GTN panel config.
Then, swap the Carenado G500/600 with the Flight 1 Garmin G500/600 using the F1GNS panel config tool.
Finally, make the edits to the panel.cfg that displays the GTN750 inside the 530 screen. Works awesome, excellent plane.

Did anyone ever figure out how to get around the hard coded bezel click spot for the default 530 gps? I guess not all addon aircraft are as easy to modify as the amazing RealAir addons. 😉

Andrew

Archived

This topic is now archived and is closed to further replies.

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...