I have the Milviz PC6 for P3D5 reinstalled, with a 750 and 650 combo.

The units both work ok in the VC.

Either of the 750 or 650 pops up as a window quite happily, but the other then causes a CTD when I try to open the pop up.

See video -->>>>  

Interestingly the A2A C182 with the same combo works just fine.

See video -->>>>  

 

 

PC6 panel.cfg extracts

[Window03]
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

[Window04]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

[Vcockpit02]
Background_color=20,20,20
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01
gauge00=..\panel\Milviz_GPS!FBS_GNS430_2,  0,451,640,262
gauge01=..\panel\KAP140_HSI!MV_KAP140Display,  0,852,640,163
gauge02=..\panel\KAP140_HSI!MV_KAP140Servos,  0,0,1,1
gauge03=..\panel\PC6_XMLGauges!KR 87 ADF,  0,715,640,134
gauge04=rxpGTN!f1vc,0,0,1,1
gauge05=Console!console_GTN750_650,  0,0,1,1
gauge07=..\panel\PC6_XMLGauges!n1_2,  822,105,200,81
gauge08=..\panel\PC6_XMLGauges!n1,  823,225,200,81
gauge09=..\panel\PC6_XMLGauges!egt1,  822,376,200,81
gauge10=..\panel\PC6_XMLGauges!np1,  822,860,200,81

[Vcockpit15]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$GTN750
gauge00=rxpGTN!GTN_750_1, 0, 0,677,794,NO_BEZEL

[Vcockpit16]
Background_color=0,0,0 
size_mm=1024,512
visible=1
pixel_size=1024,512
texture=$GTN650
gauge00=rxpGTN!GTN_650_1, 0, 0,677,297,NO_BEZEL

A2A C182 panel.cfg extracts

[Window13]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

[Window14]
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

[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle

gauge01=A2A_C182!code_c182t_r, 1,1,1,1
gauge02=A2A_C182!status1,2,2,2,2
gauge03=A2A_C182!damage,	3,3,3,3
gauge04=accusim_xml!code_s,	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
gauge10=A2A_C182!code_c182t_m, 1,1,1,1
gauge11=gps!gps_500,	0,0,1065,675
gauge12=C182!avionics, 0, 576, 1024,447
gauge13=A2A_C182!annunciator, 1, 454, 854,120
gauge14=A2A_C182!number, 794, 0, 228,77
gauge15=A2A_C182!aoa_indexer, 993, 79, 29, 58
gauge16=A2A_C182!GPS_F1_dual, 1, 1, 1, 1
gauge17=rxpGTN!f1vc,0,0,1,1

[VCockpit02]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0
gauge00=rxpGTN!GTN_750_1, 0, 0,677,794,NO_BEZEL

[VCockpit03]
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

 

Edited December 27, 20214 yr by RXP

Even more interesting..

On a restart Im encountering other issues as well.

1. The pop up images are corrupted; and

2. The GTN650 gauge isn't the right height (despite it displaying perfectly ok in the A2A 182 with the same settings)?

But the corrupted pop ups now dont CTD

@RXP any idea what could cause this please?

Video -->> 

 

@RXP and now it appears I'm back to the original problem in the first post...but with the 650 showing at half its supposed vertical height?

 

 

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Thursday, June 19, 2014 at 16:37 FSPS Build:22767
[Window Titles]
Window00=Main Panel
//Window01=GPS
Window02=Autopilot
Window03=Reality XP GTN Unit 1 (managed)
Window04=Reality XP GTN Unit 1 (managed)

[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL
VIEW_FORWARD_DIR=10.000, 0.000, 0.000

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

//[Window01]
//Background_color=0,0,0 
//size_mm=1280,650
//window_size_ratio=1.000  
//position=2
//visible=0
//ident=GPS_PANEL
//window_size= 0.710, 0.552
//window_pos= 0.290, 0.480

//gauge00=..\panel\PC6_XMLGauges!FBS_GNS430_2d,  640,0,640,268
gauge01=..\panel\PC6_XMLGauges!KR 87 ADF,  640,268,640,134
//gauge02=..\panel\PC6_XMLGauges!FBS_GNS530_1d,  0,0,640,468
gauge03=..\panel\PC6_XMLGauges!FBS_GTX330,  0,468,640,170

[Window02]
BACKGROUND_COLOR=1,1,1
size_mm=170,84
window_size_ratio=1.000  
position=8
visible=0
ident=Autopilot
window_size= 0.400, 0.128
window_pos= 0.500, 0.180
gauge00=..\panel\KAP140_HSI!MV_KAP140_PopupDisplay,  0,0,170,84

[Window03]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

[Window04]
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

// --------------------------

[Vcockpit01]
Background_color=0,0,0 
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$vpanel

gauge00=..\panel\PC6!PC6_Controllers,1,1,1,1
gauge01=..\panel\PC6!PC6_SysEvents,1,1,1,1
gauge02=..\panel\PorterSystems!PorterSystems,  0,0,1,1
gauge04=..\panel\amsinterop!amsinterop,1,1,1,1
gauge05=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\MV_PC-6_Base\\PC6_XML_Sounds#80
gauge06=TrueGlass!Core,0,0,1,1
gauge07=RealLight!Core,0,0,1,1


[Vcockpit02]
Background_color=20,20,20
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01
//gauge00=..\panel\Milviz_GPS!FBS_GNS430_2,  0,451,640,262
gauge01=..\panel\KAP140_HSI!MV_KAP140Display,  0,852,640,163
gauge02=..\panel\KAP140_HSI!MV_KAP140Servos,  0,0,1,1
gauge03=..\panel\PC6_XMLGauges!KR 87 ADF,  0,715,640,134
gauge04=rxpGTN!f1vc,0,0,1,1
gauge05=Console!console_GTN750_650,  0,0,1,1
gauge07=..\panel\PC6_XMLGauges!n1_2,  822,105,200,81
gauge08=..\panel\PC6_XMLGauges!n1,  823,225,200,81
gauge09=..\panel\PC6_XMLGauges!egt1,  822,376,200,81
gauge10=..\panel\PC6_XMLGauges!np1,  822,860,200,81
//---------------------------------------------------------

[Vcockpit03]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_01
texture00=RL_1, 0,0,2048,2048

[Vcockpit04]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_02
texture00=RL_2, 0,0,2048,2048

[Vcockpit05]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_03
texture00=RL_3, 0,0,2048,2048

[Vcockpit06]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_04
texture00=RL_4, 0,0,2048,2048
[Vcockpit07]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_05
texture00=RL_5, 0,0,2048,2048

[Vcockpit08]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_06
texture00=RL_6, 0,0,2048,2048

[Vcockpit09]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_07
texture00=RL_7, 0,0,2048,2048

[Vcockpit10]
Background_color=0,0,0
size_mm=4096,4096
visible=1
pixel_size=4096,4096
texture=$VC_08
texture00=RL_8, 0,0,4096,4096

[Vcockpit11]
Background_color=0,0,0
size_mm=4096,4096
visible=1
pixel_size=4096,4096
texture=$VC_09
texture00=RL_9, 0,0,4096,4096

[Vcockpit12]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_0

texture00=TG_0, 0,0,2048,2048

[Vcockpit13]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_1
texture00=TG_1, 0,0,2048,2048

[Vcockpit14]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Bell_407
gauge01=..\panel\PC6_XMLGauges!Chronometer,   270,410,630,630
gauge02=..\panel\PC6_XMLGauges!C310_DME, 10, 0,300,80

[Vcockpit15]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0
gauge00=rxpGTN!GTN_750_1, 0, 0,677,794,NO_BEZEL

[Vcockpit16]
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

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

 

C182

PC6

 

Edited December 27, 20214 yr by RXP

Hi,

There are multiple issues with the configuration and this might explain the problem.

1) You should only use one unit #1 and one unit #2 in the same panel.

- In your case, use instead (750_1 + 650_2) or (750_2 + 650_1)
- This can also be for example (750_1 + 430_2)

In other words, don't use two different models with the same unit number because it is not supported.

2) The popup [window##] entries have conflicting dimensions

Use either size_mm or window_size but not both.

https://www.prepar3d.com/SDKv5/sdk/panels_and_user_interface/panels/panel_configuration_files.html#windowXX and vcockpitXX

PS: Further reading the documentation I'm even wondering whether the panel might not be causing other problems because [Window01] is lacking in the middle of the list?! Previous versions used to linearly scan the panel.cfg and any missing entry is usually signaling the sim to stop scanning.

Edited December 27, 20214 yr by RXP

22 minutes ago, RXP said:

Hi,

There are multiple issues with the configuration and this might explain the problem.

1) You should only use one unit #1 and one unit #2 in the same panel.

- In your case, use instead (750_1 + 650_2) or (750_2 + 650_1)
- This can also be for example (750_1 + 430_2)

In other words, don't use two different models with the same unit number because it is not supported.

2) The popup [window##] entries have conflicting dimensions

Use either size_mm or window_size but not both.

https://www.prepar3d.com/SDKv5/sdk/panels_and_user_interface/panels/panel_configuration_files.html#windowXX and vcockpitXX

PS: Further reading the documentation I'm even wondering whether the panel might not be causing other problems because [Window01] is lacking in the middle of the list?!

Thanks, I'll try playing with those then, but I'm curious as to why the exact same settings work fine with the A2A C182?

I don't know why one but not the other, but usually it is because there are other "service" gauges in the panel which are hard coded and expecting a certain "config" (such as the typical "popup" toggle overlay gauges). In any case the A2A panel.cfg is wrongly using 2x _1 units as well and this is not supported (some features might break such as CDI mode sync etc...)

Please note the windows_size way is easier to work with: it is dependent on the screen size, not the window00 size, and gauge position and dimension is set in percent, instead of pixels. In other words this:

[Window03]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,937,887

Changes to this:

[Window03]
Background_color=0,0,0
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,100, 100

1 minute ago, RXP said:

 

Thanks, that makes sense, cheers for your usual helpfullness 🙂

1 hour ago, RXP said:

 

So I changed to this below:

Amended window 03 and 04 as you suggested.  Also used one _1 and one _2 units.  Incorporated Window01 again.

Exact same behaviour in sim regardless :S @RXP

EDIT: I also tried out a version of this removing the window 01 and renumbering the others. Still exactly the same behaviour in sim.  Both gauges work, but as soon as I try to pop out the second, it CTD, and the 650 is still missized.

[Window Titles]
Window00=Main Panel
Window01=GPS
Window02=Autopilot
Window03=Reality XP GTN Unit 1 (managed)
Window04=Reality XP GTN Unit 1 (managed)

[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL
VIEW_FORWARD_DIR=10.000, 0.000, 0.000

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

[Window01]
Background_color=0,0,0 
size_mm=1280,650
window_size_ratio=1.000  
position=2
visible=0
ident=GPS_PANEL
window_size= 0.710, 0.552
window_pos= 0.290, 0.480

gauge00=..\panel\PC6_XMLGauges!FBS_GNS430_2d,  640,0,640,268
gauge01=..\panel\PC6_XMLGauges!KR 87 ADF,  640,268,640,134
gauge02=..\panel\PC6_XMLGauges!FBS_GNS530_1d,  0,0,640,468
gauge03=..\panel\PC6_XMLGauges!FBS_GTX330,  0,468,640,170

[Window02]
BACKGROUND_COLOR=1,1,1
size_mm=170,84
window_size_ratio=1.000  
position=8
visible=0
ident=Autopilot
window_size= 0.400, 0.128
window_pos= 0.500, 0.180
gauge00=..\panel\KAP140_HSI!MV_KAP140_PopupDisplay,  0,0,170,84

[Window03]
Background_color=0,0,0
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=rxpGTN!GTN_750_1, 0, 0,100,100

[Window04]
Background_color=0,0,0
ident=14403
window_pos= 0.660, 0.740
window_size= 0.340, 0.260
zorder=99
gauge00=rxpGTN!GTN_650_2, 0, 0,100,100

// --------------------------

[Vcockpit01]
Background_color=0,0,0 
size_mm=256,256
visible=0
pixel_size=1024,1024
texture=$vpanel

gauge00=..\panel\PC6!PC6_Controllers,1,1,1,1
gauge01=..\panel\PC6!PC6_SysEvents,1,1,1,1
gauge02=..\panel\PorterSystems!PorterSystems,  0,0,1,1
gauge04=..\panel\amsinterop!amsinterop,1,1,1,1
gauge05=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\MV_PC-6_Base\\PC6_XML_Sounds#80
gauge06=TrueGlass!Core,0,0,1,1
gauge07=RealLight!Core,0,0,1,1

[Vcockpit02]
Background_color=20,20,20
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01
gauge00=..\panel\Milviz_GPS!FBS_GNS430_2,  0,451,640,262
gauge01=..\panel\KAP140_HSI!MV_KAP140Display,  0,852,640,163
gauge02=..\panel\KAP140_HSI!MV_KAP140Servos,  0,0,1,1
gauge03=..\panel\PC6_XMLGauges!KR 87 ADF,  0,715,640,134
gauge04=rxpGTN!f1vc,0,0,1,1
gauge05=Console!console_GTN750_650,  0,0,1,1
gauge07=..\panel\PC6_XMLGauges!n1_2,  822,105,200,81
gauge08=..\panel\PC6_XMLGauges!n1,  823,225,200,81
gauge09=..\panel\PC6_XMLGauges!egt1,  822,376,200,81
gauge10=..\panel\PC6_XMLGauges!np1,  822,860,200,81

//---------------------------------------------------------

[Vcockpit03]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_01
texture00=RL_1, 0,0,2048,2048

[Vcockpit04]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_02
texture00=RL_2, 0,0,2048,2048

[Vcockpit05]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_03
texture00=RL_3, 0,0,2048,2048

[Vcockpit06]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_04
texture00=RL_4, 0,0,2048,2048
[Vcockpit07]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_05
texture00=RL_5, 0,0,2048,2048

[Vcockpit08]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_06
texture00=RL_6, 0,0,2048,2048

[Vcockpit09]
Background_color=0,0,0
size_mm=2048,2048
visible=1
pixel_size=2048,2048
texture=$VC_07
texture00=RL_7, 0,0,2048,2048

[Vcockpit10]
Background_color=0,0,0
size_mm=4096,4096
visible=1
pixel_size=4096,4096
texture=$VC_08
texture00=RL_8, 0,0,4096,4096

[Vcockpit11]
Background_color=0,0,0
size_mm=4096,4096
visible=1
pixel_size=4096,4096
texture=$VC_09
texture00=RL_9, 0,0,4096,4096

[Vcockpit12]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_0

texture00=TG_0, 0,0,2048,2048

[Vcockpit13]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_1
texture00=TG_1, 0,0,2048,2048

[Vcockpit14]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Bell_407
gauge01=..\panel\PC6_XMLGauges!Chronometer,   270,410,630,630
gauge02=..\panel\PC6_XMLGauges!C310_DME, 10, 0,300,80

[Vcockpit15]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0
gauge00=rxpGTN!GTN_750_1, 0, 0,677,794,NO_BEZEL

[Vcockpit16]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN650
background_color=0,0,0
gauge00=rxpGTN!GTN_650_2, 0, 0,677,297,NO_BEZEL

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

 

Edited December 27, 20214 yr by kevinfirth

In this case what would help is the exact crash data, like the error code (0xC0000005?), the offset, and the module name.

6 minutes ago, RXP said:

In this case what would help is the exact crash data, like the error code (0xC0000005?), the offset, and the module name.

Faulting application name: Prepar3D.exe, version: 5.3.15.28131, time stamp: 0x61c28ec5
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x3614
Faulting application start time: 0x01d7fb4b775cec38
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 2c5d56d6-e3ba-45f2-ac23-d1d7f307d873
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: Prepar3D.exe, version: 5.3.15.28131, time stamp: 0x61c28ec5
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x3d8
Faulting application start time: 0x01d7fb4aa1ebbfaf
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: b2301966-fc8d-4f95-bc86-471e12c34967
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: Prepar3D.exe, version: 5.3.15.28131, time stamp: 0x61c28ec5
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x3a20
Faulting application start time: 0x01d7fb4925f1163f
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 0cb168e9-dbab-45ff-b000-799977bda419
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: Prepar3D.exe, version: 5.3.15.28131, time stamp: 0x61c28ec5
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x1fec
Faulting application start time: 0x01d7fb46ea4049e1
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 4aca4d9f-41d6-4753-a2f7-91a300eafeef
Faulting package full name: 
Faulting package-relative application ID: 

@RXP seems to have been part resolved.
I took out gauge00 (the old gns430) and renumbered the others sequentially in [Vcockpit02].

Now there is no CTD when selecting either pop up in any order. 🙂

I still have the 650 showing the wrong size though.....

Edited December 27, 20214 yr by kevinfirth

This doesn't tell yet what P3D is doing which is triggering the crash, but it tells the crash is from the standard Windows component "ucrtbase.dll" and always at the same code location, and always for the same reason:

Exception code: 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN)
Fault offset:   0x000000000007286e
Module name:    ucrtbase.dll
 

NB: this error code can be misleading https://devblogs.microsoft.com/oldnewthing/20190108-00/?p=100655

 

Something you can do is try to isolate in removing what could be unnecessary "management" gauges:

[Window01]
gauge00=..\panel\PC6_XMLGauges!FBS_GNS430_2d,  640,0,640,268
gauge02=..\panel\PC6_XMLGauges!FBS_GNS530_1d,  0,0,640,468

[Vcockpit02]
gauge00=..\panel\Milviz_GPS!FBS_GNS430_2,  0,451,640,262
gauge05=Console!console_GTN750_650,  0,0,1,1

 

NB: the RXP GTN already supports its own "popup window" function directly clicking on the screen, and you can choose to popup the window with Right Mouse Button, or SHIFT+Left Mouse Button:

 

RealityXP.GTN.ini

[GTN_XXX_#.NAME_OF_THE_SECTION]

; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button).
popleft = 
; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225).
popright = 

 

With your panel the ident numbers you'd use are 14401 and 14403

Edited December 27, 20214 yr by RXP

13 minutes ago, RXP said:

Something you can do is try to isolate in removing what could be unnecessary "management" gauges:

Done already, see prev post.

13 minutes ago, RXP said:

NB: the RXP GTN already supports its own "popup window" function directly clicking on the screen, and you can choose to popup the window with Right Mouse Button, or SHIFT+Left Mouse Button:

Popups work fine now, the improper gauge numbering must have been the problem.

I still have the missized 650 in the VC panel   Interesting, if you look at my first video in the OP, you can see the 650 is correctly sized there....??

Edited December 27, 20214 yr by kevinfirth

40 minutes ago, kevinfirth said:

Done already, see prev post.

All 4 of them (the ones I've indicated)?