Unwanted CTD for a certain model

[BoeingvsAirbusNKL]

I witnessed an unwanted CTD when I wanted to fly the CASA 295M from Premier Aircraft Design.

I clicked fly now, the loading bar came up, the bar was still 0% and then, BOOM, CTD.

Has anyone heard of or witnessed this problem?

 

[Blackbird686]

I had the same problem with PAD's PC-12 but the 295 is fine in my sim. I ended up finding a bad XML gauge in the PC-12's gauge cab folder. I zapped it from the configuration and replaced it with a similar gauge.... simple fix but diagnosis was a buggar. I just took a wild stab and started with the gauges, this has been an issue with a few of the models I have... they've done the same thing.

BB686

 

[Tom Clayton]

Try the Windows event logs and see if there's a filename associated with the shutdown.

 

[BoeingvsAirbusNKL]

I think i found the problem: PANELS.DLL

 

[BoeingvsAirbusNKL]

I tried antivirus: no luck.
I tried replacing panels.dll: no luck.
I have no idea what to do!

 

[BoeingvsAirbusNKL]

I am moving my fs9 folder to my my c: drive. I hope it works.

 

[Blackbird686]

Did you have a go with the Windows Event Viewer, as Tom suggested? That's how I found the problem with the PC-12. Just say'n...

BB686

 

[BoeingvsAirbusNKL]

I did use event viewer. that is how I found panels.dll was the source of the problem.

 

[Lane Street]

A crash caused by panels.DLL indicates a bad gauge.

Determining which gauge is causing the crash is a process of elimination.

Start by backing up the panel.cfg.

Does the plane have a VC? If so, remove all of the [VCockpitnn] sections and test.

If it still crashes you can disable individual gauges by adding // to the beginning of the line...

go from...

gauge00=Cessna!ADF,545,86

...to...

//gauge00=Cessna!ADF,545,86

...to comment out any gauge.

I would remove all of the pop up Windows and first focus on the main panel.

Comment out half of the gauges and test.

If it still crashes comment out half of the remaining gauges and test.

If it doesn't crash, remove half of the comments and test.

Rinse and repeat.

When you identify the culprit, go back to your original panel.cfg and comment out that gauge and test. There may be more than one bad gauge.

You can then look for an alternative replacement gauge.

cheers,
Lane

 

[BoeingvsAirbusNKL]

Thanks for the info, Lane.

 

[BoeingvsAirbusNKL]

Unfortunately, I removed the casa 295 from my aircraft folder.

 

[BoeingvsAirbusNKL]

I just don't have the patience to find the culprit.

 

[BoeingvsAirbusNKL]

Solved!

I found the Culprit! It was the Clock.cab!

 

[Blackbird686]

Glad you got it sorted... I almost got to the point of dumping the PC-12, then I found the offending gauge at the last minute.

BB686