Happy New Year's Eve!

I JUST purchased the GTN 650 to use alongside the 750. Anytime I bring up the pop-up 650 my sim crashes. P3D v4.4.

This seems to have something to do with the Panel Manager. There are three entries for my GTN units. Two work, bringing up a GTN 750 or a GTN 650. The third crashes the sim when I check it. Seems like the .cfg file might need to be edited?

Edited December 31, 20187 yr by snpower

Hi,

Can you please detail what is this 3rd GTN about? 

Is this the same model as the 750 or the 650 (not a 635 for example)?

I believe it is a 750 unit. I went ahead and used the Add-On manager to remove both products; the extra panel is still visible in the panel manager (see screenshot) even without any GTN setup.

 

 

It seems that all is resolved by re-installed the GTN's via the Reality XP GTN Menu.

Unfortunately I spoke too soon. As soon as I double-click on the 650 or select it in the panel manager the sim crashes. Upon restart I lose both GTNs and have to set them up again.

First I select the option to replace gauges. Second, I configure the pop-up windows. When I am done, what I am seeing is THREE OR FOUR GTN's in the panel manager. Two or three reference 'Unit 1' and one references 'Unit 2'. The GTN 750 populates the panel but the 650 does not unless I assign it to mutiple VC's. Please see screenshots. This might be self-imposed, somehow but I have been adding a single 750 to various aircraft for months with no issues. I believe my panel.cfg has become problematic...

Here are the relevant 'Window' entries in the .cfg file. There is obviously too much information:

// GTN750_650

[Window Titles]
Window00=Main Panel
Window01=Throttle
Window02=C310 Prelight
Window03=Reality XP GTN Unit 1 (managed)
Window04=Reality XP GTN Unit 1 (managed)
Window05=Reality XP GTN Unit 1 (managed)
Window06=Reality XP GTN Unit 2 (managed)

[Window02]
Background_color=0,0,0
size_mm=500,243
window_size_ratio=1.000  
position=0
visible=0
ident=70
window_size= 0.400, 0.324
window_pos= 0.000, 0.040

gauge00=C310_XMLGauges!C310_Preflight,  0,0,500,243

//--------------------------------------------------------
[Window03]
Background_color=0,0,0
size_mm=937,390
window_size_ratio=1.000  
position=7
visible=0
ident=14403
window_size= 0.340, 0.260
window_pos= 0.660, 0.728
zorder=99

gauge00=rxpGTN!GTN_650_1, 0, 0,937,390

//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=937,990
window_size_ratio=1.000  
position=7
visible=0
ident=14401
window_size= 0.340, 0.580
window_pos= 0.660, 0.160
zorder=99

gauge00=rxpGTN!GTN_750_1, 0, 0,937,990

[Window05]
size_mm=100,100
window_pos=0.000000,0.000000
window_size=0.324219,0.573711
visible=1
always_visible=1
zorder=99
background_color=0,0,0
ident=15751
gauge00=rxpGTN!GTN_750_1, 0, 0,100,100

[Window06]
size_mm=100,100
window_pos=0.000000,0.573711
window_size=0.324219,0.254176
visible=1
always_visible=1
zorder=99
background_color=0,0,0
ident=15652
gauge00=rxpGTN!GTN_650_1, 0, 0,100,100

 

 

 

I've now re-installed my Milviz C310 in order to get a clean panel.cfg file. I think I see the crux of the problem: BOTH GTN units are assigned as 'Unit 1'. I'm not sure what I am doing to make this happen?

In the end, a simple change to the panel.cfg file: the 750 is 'Unit 1' and I renamed the 650 as 'Unit 2'.

 

Edited January 1, 20197 yr by snpower

Hi,

It is obviously a wrong panel.cfg file. The assistant is supposed to properly manage no more than 2 windows entries so this makes me wonder what could have been the sequence of actions in the assistant that lead to this.

Nevertheless, the crux of the problem is that you cannot have twice a _1 or twice a _2 unit in the panel.cfg file. This is mostly the unique restriction otherwise you can have up to 4 (maybe 8 but I'm not sure) instances of the same gauge on the panel.cfg (1 in VC and 3 popups for example - useless but cool as a tech demo of RXP technology capable of displaying these 4 devices at the same time without any loss of FPS - or marginally computer depending).

So can you confirm this is now resolved?

I can confirm this is resolved. Thanks for your help.