Sign in to follow this  
OrtegaS

FSX-Steam Crashes

Recommended Posts

Hello,

 

It seems when i install the Mindstar GNS430/530 into an A/C where VC gauges are used the sim locks up after a few min of play.  If i disable that, then all seems well, but the VC gauges are blank and clickspots are disabled.  I have to use SHIFT + X to pop up the panel and use that way.  It would at least be nice to have some display in the VC gauge while using the 2D pop up.  I know each developer is different, and have even read of some of the same issues  elsewhere online,  but it doesnt seem to be that prevalent.  If you don't mind checking to see  if I missed something plz.  I used the Milviz C310 installer which has a mindstar installer.  Real Air i tricked the configurator into thinking there is a RXP gauge with a dummy file RXPgns.dll in the guages folder then altered those entries with mindstar entries.  I hope I'm missing something, but these are their entries, with a few minor differences to suit my needs.   These issues were present even before I made minor changes.  My changes are in red.

 

Thank you,

Steve

 

 

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Tuesday, July 22, 2014 at 18:46 FSPS Build:22767

[Window Titles]
Window00=Main Panel
Window01=Throttle
Window02=Copilot
Window03=Engine Panel
Window04=Electrical Panel
Window05=C310 Prelight
Window06=Mindstar GNS530/430


[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL

VIEW_FORWARD_DIR=10.000, 0.000, 0.000



//--------------------------------------------------------
[Window00]
file=Main_Panel.bmp
size_mm=1680,1050
window_size_ratio=1.000  
position=7
visible=1
ident=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000

gauge00=C310_XMLGauges!FBS_KAP140,  856,777,392,117
gauge01=C310_XMLGauges!KR 87 ADF,  1280,600,392,99
gauge02=C310_XMLGauges!C310_DME,  25,737,150,75
gauge03=MilVizC310!EDM700_L,  -9,850,200,198
gauge04=MilVizC310!EDM700_R,  206,852,200,198
gauge05=C310_XMLGauges!C310_Airspeed Indicator,  220,450,169,169
gauge06=C310_XMLGauges!C310_Vertical Speed,  648,657,169,169
gauge07=C310_XMLGauges!C310_Altimeter,  648,449,169,169
gauge08=C310_XMLGauges!C310_RMI_NAV_Source,  612,989,24,24
gauge09=C310_XMLGauges!C310_HSI_NAV_Source,  507,844,24,24
gauge10=C310_XMLGauges!C310_RMI,  648,868,169,169
gauge11=C310_XMLGauges!C310_HSI,  413,644,202,194
gauge12=C310_XMLGauges!C310_TurnCoordinator,  220,657,169,169
gauge13=C310_XMLGauges!C310_Clock,  62,597,117,117
gauge14=C310_XMLGauges!CopilotPanel,  1010,  337 ,546,48
gauge15=C310_XMLGauges!EnginePanel,  444,927,151,53
gauge16=C310_XMLGauges!ElectricalPanel,  444,983,151,64
gauge17=C310_XMLGauges!ThrottleQuad,  1399,844,279,208
gauge18=C310_XMLGauges!C310_Gear_Flap_Panel,  858,906,529,153
gauge19=C310_XMLGauges!C310_Fuel_Low_Left,  1557,829,25,25
gauge20=C310_XMLGauges!C310_Fuel_Low_Right,  1623,829,25,25
gauge21=C310_XMLGauges!C310_Artificial_Horizon,  413,442,202,194
gauge22=MPI_GNS!GNS530,  856,494,392,283,1:3:0
gauge23=MPI_GNS!GNS430,  1280,416,392,184,2:3:0
//gauge22=C310_XMLGauges!FBS_GNS430_2,  1280,416,392,184
//gauge23=C310_XMLGauges!FBS_GNS530_1,  856,494,392,283
gauge24=C310_XMLGauges!BK_AudioPanel,  856,416,392,78
gauge25=C310_XMLGauges!FBS_GTX330,  1280,699,392,104

draw_order00=gauge22,gauge23,gauge03,gauge04

//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=296,547
window_size_ratio=1.000  
position=8
visible=0
ident=10030
window_size= 0.176, 0.514
window_pos= 0.834, 0.486
zorder=2

gauge00=C310_XMLGauges!C310_ThrottleQuad,  0,0,286,547


//--------------------------------------------------------
[Window02]
file=Copilots_Panel.bmp
file_1024=Copilots_Panel.bmp
size_mm=824,1050
window_size_ratio=1.000  
position=0
visible=0
ident=10040
window_size= 0.500, 1.000
window_pos= 0.510, 0.000
zorder=1

gauge00=C310_XMLGauges!C310_Clock,  649,947,106,106
gauge01=C310_XMLGauges!C310_Manifold_Press,  33,455,164,164
gauge02=C310_XMLGauges!C310_Airspeed Indicator,  442,864,164,164
gauge03=C310_XMLGauges!C310_RPM,  33,660,164,164
gauge04=C310_XMLGauges!C310_FuelFlow,  33,864,164,164
gauge05=C310_XMLGauges!C310_FuelQty,  235,659,164,164
gauge06=C310_XMLGauges!C310_LeftEngineTemps,  235,457,164,164
gauge07=C310_XMLGauges!C310_RightEngineTemps,  442,457,164,164
gauge08=C310_XMLGauges!C310_EGT,  442,659,164,164
gauge09=C310_XMLGauges!C310_Suction,  649,661,106,106
gauge10=C310_XMLGauges!C310_OAT,  649,804,106,106
gauge11=C310_XMLGauges!C310_DoorSeal Switch,  646,539,24,24
gauge12=C310_XMLGauges!C310_Fuel Qty Switch,  304,859,27,24
gauge13=C310_XMLGauges!C310_FuelTest_Left,  236,841,30,30
gauge14=C310_XMLGauges!C310_FuelTest_Right,  376,  841 ,30,30
gauge15=C310_XMLGauges!CopilotPanel,  0,341,546,48


//--------------------------------------------------------
[Window03]
file=EnginePanel.bmp
file_1024=EnginePanel.bmp
size_mm=789,196
window_size_ratio=1.000  
position=0
visible=0
ident=10050
window_size= 0.400, 0.179
window_pos= 0.000, 0.830

gauge00=C310_XMLGauges!C310_EnginePanel,  0,0,798,196
gauge01=C310_XMLGauges!EnginePanel,  0,142,789,53
gauge02=C310_XMLGauges!EnginePanel,  0,0,789,30


//--------------------------------------------------------
[Window04]
file=ElectricalPanel.bmp
file_1024=ElectricalPanel.bmp
size_mm=800,102
window_size_ratio=1.000  
position=0
visible=0
ident=10060
window_size= 0.520, 0.120
window_pos= 0.000, 0.880

gauge00=C310_XMLGauges!ElectricalPanel,  0,0,800,27
gauge01=C310_XMLGauges!C310_ElectricalPanel,  0,0,800,102


//--------------------------------------------------------
[Window05]
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


//--------------------------------------------------------
[Window06]
Background_color=0,0,0
size_mm=800,910
window_size_ratio=1.000  
position=7
visible=0
ident=11013
window_size= 0.340, 0.580
window_pos= 0.660, 0.420
zorder=99

gauge00=MPI_GNS!GNS530,  0,0,800,581,1:2:11013
gauge01=MPI_GNS!GNS430,  0,581,800,330,2:2:11013


//--------------------------------------------------------
[Vcockpit01]
file=C310_VC_01.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01

gauge00=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Airplanes\\Cessna 310R MilViz\\panel\\C310R_Sounds#22
gauge01=C310_XMLGauges!FBS_KAP140,  0,767,640,163
gauge02=C310_XMLGauges!KR 87 ADF,  0,630,640,134
gauge03=C310_XMLGauges!C310_DME,  649,32,300,150
gauge04=MilVizC310!EDM700_L,  658,193,350
gauge05=MilVizC310!EDM700_R,  658,540,350
gauge06=C310_XMLGauges!C310_Logic,  693,11,1,1
gauge07=C310_XMLGauges!3D_Altimeter,  681,796,283,368

//--------------------------------------------------------
[Vcockpit02]
file=C310_VC_02.bmp
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_02

gauge00=C310_XMLGauges!FBS_GTX330,  0,376,512,136


//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=64,64
visible=1
pixel_size=64,64
texture=$C310_VC_03

gauge00=C310_XMLGauges!FLTPanel_dimming,  0,0,64,64


//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=64,64
visible=1
pixel_size=64,64
texture=$C310_VC_04

gauge00=C310_XMLGauges!InstPanel_dimming,  0,0,64,64


//--------------------------------------------------------
[Vcockpit05]
file=Mindstar_GNS530.bmp
size_mm=512,512
visible=1
pixel_size=512,512
texture=$MPI_GNS530

gauge00=MPI_GNS!GNS530,  0,0,512,,1:1:-1


//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0
size_mm=512,512
visible=1
pixel_size=512,512
texture=$MPI_GNS430x2

gauge00=MPI_GNS!GNS430,  0,0,512,,2:1:-1



[Color]
Day=255,255,255
Night=85,85,85
Luminous=140,140,140

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

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

// Panel Configuration file
// RealAir Simulations Beechcraft Turbine Duke V2 2014 Update
// Panel and Gauge Programming by Sean Moloney
// Copyright (c) 2014 RealAir Simulations

// ===============================================================================
// IMPORTANT - 'Window01' AND 'Window02' BELOW ARE RESERVED FOR GPS POPUPS AND CAN
// BE OVERWRITTEN BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY
// EDITING THIS FILE. IF YOU WANT TO ADD CUSTOM WINDOW ENTRIES, YOU CAN USE ANY
// VALUE FROM 'Window03' TO 'Window 09'.
// ===============================================================================

[Window Titles]
Window00=Main Panel
Window01=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
Window02=Blank

[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[Window01]
Background_color=0,0,0
size_mm=800,910
window_size_ratio=1.000  
position=7
visible=0
ident=15531
window_size= 0.340, 0.580
window_pos= 0.660, 0.420
zorder=99

gauge00=MPI_GNS!GNS530,  0,0,800,581,1:2:15531
gauge01=MPI_GNS!GNS430,  0,581,800,330,2:1:15531

//window_pos=0.739583,0.000000
//window_size=0.260417,0.300000
//visible=0
//ident=15531
//zorder=99
//gauge00=rxpGNS!GNS530,0,0,100,100


[Window02]
size_mm=1,1
position=0
visible=0
ident=15600
BACKGROUND_COLOR=0,0,0
gauge00=RASDuke!Blank, 0, 0, 1, 1

[VCockpit01]
size_mm=1024,1024
pixel_size=1024,1024
texture=$RAS_Duke_CFG
background_color=1,1,1

gauge01=Config!Options, 1020, 1023, 1, 1
gauge02=Config!RealView, 1021, 1023, 1, 1
gauge03=Config!RadioLayout, 1027, 1023, 1, 1

gauge04=RASDuke!InitVars, 1022, 1023, 1, 1
gauge05=RASDuke!1hzCode, 1023, 1023, 1, 1
gauge06=RASDuke!2hzCode, 1024, 1023, 1, 1
gauge07=RASDuke!18hzCode, 1025, 1023, 1, 1

gauge08=RASDuke!NavCom1, 1, 2, 509, 61
gauge09=RASDuke!NavCom2, 1, 64, 509, 61
gauge10=RASDuke!ADF, 4, 127, 332, 49
gauge11=RASDuke!Xpndr, 7, 243, 305, 57
gauge12=RASDuke!Autopilot, 5, 177, 292, 62
gauge13=RASDuke!DME, 4, 305, 256, 46
gauge14=RASDuke!KA285_Annun, 512,2,337,108
gauge15=RASDuke!Annunciator_Turbine, 516, 111, 226, 245
gauge16=RASDuke!Moritz_LCD, 808, 133, 214, 259
gauge17=RASDuke!Fuel_Qty_LCD, 410, 128, 105, 86
gauge18=RASDuke!Master_Warn, 893, 1, 130, 129

// ===============================================================================
// IMPORTANT - 'gauge19'. 'gauge20, 'gauge21', and 'gauge22' BELOW CAN BE OVERWRITTEN
// BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE
// IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY
// CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22'
// ===============================================================================

//gauge19=rxpGNS!GNS530, 1, 660, 504, 364
gauge19=MPI_GNS!GNS530, 1, 660, 504, 364, 1:1:-1
gauge20=RASDuke!Blank, 0, 0, 1, 1

gauge21=RASDukeTv2_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Duke Turbine V2/Panel/Sound/RASDukeTv2_Sound.ini
gauge22=RASDuke!Sound_Manager, 1,1,3,3

gauge23=RASDuke!Pressurisation, 1024, 1023, 1, 1


[Color]
Day=255,255,255
Night=225,117,89
Luminous=200,200,101

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

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

While I can review the files... beyond that you've actually given me very little to go on with regards to actually offering support.

 

You say you get a lock up...  When doing what?  Does the sim crash to desktop?  Is there an error message?  Is there a Windows Error log entry?

Share this post


Link to post

Thank you.

 

There does not ever seem to be an error msg associated with this issue.  It does not crash to desktop.  It simply freezes as is.  There is still sound related to the current attitude.  But I can do nothing else with FSX.  Its like a picture with sound. This seems to happen whenever I move from the V/C to a 2d popup panel of the GNS.  Back and forth.

 

I didn't see any error generated from FSX in the event viewer, but the "information" side had this:

 

 

og Name:      Application
Source:        Windows Error Reporting
Date:          7/28/2016 12:27:47 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      MainBang
Description:
Fault bucket 107719236887, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: EZCA.exe
P2: 1.1.8.7
P3: 2a425e19
P4: StackHash_1410
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_F6_FROM_ntdll+0x0007718C
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_EZCA.exe_4c287196e0de6cc28cf736a7bbb5d3687a2_794a7b46_26ec22c4

Analysis symbol:
Rechecking for solution: 0
Report Id: 2ee114f6-086c-4c8d-a4ab-ff53906a3d81
Report Status: 0
Hashed bucket: 3b2c0c93909d336b8ae44df53e453217
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-28T17:27:47.433693000Z" />
    <EventRecordID>37972</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MainBang</Computer>
    <Security />
  </System>
  <EventData>
    <Data>107719236887</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>EZCA.exe</Data>
    <Data>1.1.8.7</Data>
    <Data>2a425e19</Data>
    <Data>StackHash_1410</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>PCH_F6_FROM_ntdll+0x0007718C</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_EZCA.exe_4c287196e0de6cc28cf736a7bbb5d3687a2_794a7b46_26ec22c4</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>2ee114f6-086c-4c8d-a4ab-ff53906a3d81</Data>
    <Data>0</Data>
    <Data>3b2c0c93909d336b8ae44df53e453217</Data>
  </EventData>
</Event>

 

Thank you,

 

Steve

Share this post


Link to post

That indicates EZCA... isn't that some kind of view control application?  How are you opening/closing the popup window?  When you say freeze.  If the aircraft is in motion, does it freeze as well or is there just the loss of user in put?

Share this post


Link to post

Hello,

 

I was just about to post.  Yes it is a view prgm.  I uninstalled it. Ran FSX for the longest period without issue.  I actually stopped the pgm intentionally.  Reinstalled EZCA and still no issues (no freezes.....as of yet.)  I have run it the longest without interruption.  So I might venture it was EZCA somehow-logic says anyway.  I hope I'm good to go at this point.  Thank you very much.

 

If you dont mind?   I know there is no map but no fix names are visible above 15nm.....?

and LPV appchs or ILS appchs do not indicate a Glideslop dev indicator ...correct?

 

Thank you again,

 

Steve

Share this post


Link to post

To see LPV vertical guidance indication you would have to use one of our analog nav displays or Carenado would have to pay attention to our variables that we provide to drive the needles.  With the installation of the 430/530 we installed an additional gauge called MPI_CDIGauge.gau.  It has two gauges that can be used for navigation purposes.  the KI209 is the same gauge that's in the default C172 panel for NAV1.  The GI106A is a Garmin NAV display.  They are both analog.

 

As for names... yeah, we have a bug in that... so they're disabled right now.  Sorry... but trust me... it was ugly and unreadable.

Share this post


Link to post

I've got the same freezing of FSX-SE after opening the popup.....the problem is with the 530, the 430 works fine.

 

Cees

Share this post


Link to post

In the default Cessna 172 the popup is without problems, It's the combination of 3d and 2d  of the 530 that freezes up FSX-SE in the third party planes from A2a and Milviz.

 

Cees

Share this post


Link to post

Without the popups it works okay. I disabled them in the panel cfg. 

 

Cees

Share this post


Link to post

Are you using the same program as the OP?

Share this post


Link to post

Hello Cees,

 

Sorry for your troubles.  If you read my posts it appeared there was a conflict(issue) with EZCA.  At least looking at my Event Viewer indicated a problem with it.  I don't think, for me, there ever was an issue with the Mindstar gauge.  Uninstalling EZCA solved my freezes.  After reinstalling, I'm still experiences no issues so it might have corrected a corruption somewhere.  If you have been experimenting with the *.cfg files I would look there.  If you don't use EZCA (as a possible culprit like in my case), then use FSX with an A/C that you are not trying to use the Mindstar gauge with.  If you can pull up 2D panels (pop ups) using the click spots or the shift+X without issue, then maybe your are not coding your .cfg files the right way.

 

 

 


In the default Cessna 172 the popup is without problems, It's the combination of 3d and 2d of the 530 that freezes up FSX-SE in the third party planes from A2a and Milviz.
   

That really sounds like your doing something wrong.  I have both and they work ok.

Good luck,

 

Steve

Share this post


Link to post

Ed,    :hi:

 

OP?

 

Sorry, it's early over here! Other person? I don't have that program (EZCA) installed.

 

Steve,


I have used the exe's of the planes (in the tools folder) do the  job for me. That won't work, obviously. :Thinking:

 

Cees

 

( I'll be gone until Wednesday on a little trip, I won't see the answers until then.)

Share this post


Link to post

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
Sign in to follow this