Yesterday I purchased the Cessna 206 Stationair by Carenado. Installation of the aircraft is very straight forward, run the executable file and the aircraft is installed. The aircraft comes in three different configurations, standard, cargo and amphibian.My problem is that when I attempt to create a new flight with either the standard or cargo models I incurr a CTD. The error message calls out a panels.dll issue. Attempting to create a new flight with the amphibian model, the flight loads and everything under FS9 appears to run as expected. I reviewed the earlier postings found within this forum, but none discussed a problem with a CTD between different models produced by the same manufactuer. I would think if one of the Cessna 206 models failed, the other two would most likely fail in a similar state. Any ideas?By the way, the Carenado product appears to be a great model. The detailing of the aircraft (limited to the amphibian model)is some of the best work I have seen in flight simulation.ThanksTom

What view were you in before you saved it? Even though the 206 isn't that complicated of an aircraft, saving an aircraft in anything other than the 2D cockpit will sometimes cause problems. FTR I haven't had a CTD with it yet, so that is the best advice I can offer.I agree, great aircraft!Regards, MichaelKDFWhttp://www.calvirair.com/mcpics/mcdcvabanner.jpgCalVirAir International

Mike thanks for the response.My problem is a load issue. That is when creating a new flight I can select the amphibian verson of the 206 from the Carenado's aircraft drop down menu and go forward in creating and flying the flight. With any other selection of the 206 from the Carenado aircraft selection menu, I can see the plane in the window, but when I 'ok" the selection to return to the create the flight window my FS9 goes to CTD.Tom

couple of things:1) is your default flight default, meaning using the default cessna 172 at Seattle Intl.?2) did you try to unistall the C206 then reinstall from start to finish? Uninstall the C206 completely, then reinstall.Just my thoughts. I know I run into a lot of problems when I change my default flight from the Microsoft Cessna 172, etc.Kevin

Kevin, the answer to both questions is yes. I am using the default 172 out of Seattle as my default flight. At one time, I was using a freeware version of the 172 panel from FriendlyPanels, but since I reinstalled FS9 in February I have only used the default FS9 panel. I ran the uninstall Carenado program files option found in program start up menu to delete my first installation. The CTD of the aircraft problem continued after second installation.Tom

Hi TomI see 2 options:1) something went wrong during the download and you have a corrupted version from Carenado. very rare indeed! but possible.downloading the 206 again could be an idea2) something goes wrong with your FS install (a file deleted by mistake or problem of compatibility, etc...). in this case I would recommand, if you have enough room in your HD of course, that you rename your current FS folder to FS9OLD or something like that, allowing you to install another FS somewhere else in your HD.then install SP2 and the 206, and see what happens.before that can you try the following...create a new FS9.cfg (by moving your current file momentally to your desktop, a new one will be created automatically)or, if you own FSUIPC, do the same for the config file in order to create a new one.I hope you'll very soon enjoy your 206good luck :-) David in Jerusalem

David thanks for your help.I reloaded both the Fs9.cgf and FSUIPC.ini files. Even at FS9s lowest settings the problem still remains. I have a couple questions:What is the correct file size and date of the panels.dll file?What is the correct file size and date of the Carenado Full download?ThanksTom

you're welcome Paulsorry but I don't know what you mean by panel.dll as there is no dll file in the panel.the FULL 206 zip file from Carenado is a 57,567 KB file and is from 1/25/06a quick question...do you have any ViMaCore2004.dll file in your MODULES folder?once I had a similar problem than yours and removing this file (it's a LAGO file for dynamic objects) cured the problem. who knows?regards,David

To everybody thanks for your help. The Carenado help desk got back to me last night with a solution to my problem. The following is taken for their email:ear Tom, If you are using and ATI video Card, please update the drive at: https://support.ati.com/ics/support/default...sk=knowledge&folderID=27Here are 2 transcriptions of what other customers did about this problem that we can't replicate in our systems:"I found the problem to be inside the Panel.cfg files, the original line at a Window point read: eg.[Window00]file=..panelCarenado Panel 206.bmp - I changed the pathway to:[Window00]file=....Carenado Cessna 206panelCarenado Panel 206.bmpthe CTD at loading was due to the file not finding the panel and kicking me out. After this mod to each relevant line, everything works fine now."And here is other possible solution:"I uninstalled the 206 package, reinstalled it, removed my ATI driver and reinstalled it. The problem is now gone!"Let me know the results.CarenadoThe following is the letter that I returned to them after resolving the problem:First off thank you. All three versions of the aircraft are now working perfectly.The first change that I made was to review and modify the panel.cfg files. The amphibian and the cargo versions were already set to your recommended change. All three panel configurations of the standard version needed to be changed. After verifying that the changes were correct, I ran FS9 and selected your aircraft. The problem still remained. The amphibian version loaded, but the standard and cargo version CTD. Microsoft reported the error as being the panel.dll module.On the second attempt, I used the link that you provided to update my ATI video card drivers. Prior to loading the new drivers, I reloaded my old set of drivers to ensure a clean rewrite of the new driver set. The new set of available drivers was dated 6 April 2006. For my video card there were three available files. The files were an update to the driver set, a new control center, and a parental control option.After installing both the new driver set and the control center, I once again reloaded FS9 and your aircraft. I had some interesting results. Both the amphibian and cargo versions loaded without a problem. The standard version loaded, but was missing its panel bit map file. All of the aircrafts gauges were displayed against a black background. I went back into the panel configuration and reversed my earlier changes to the standard version panel configuration files and now everything is working. My recommendation to anybody having a similar problem is to start with the video card driver update. The problem appears to be that your excellent model, like most FS9 models, needs the newest technology available to it to run properly.Again thank you for your help.Tom

Nice!! :-)enjoy Tom!David

I had a similar problem getting FS to accept the 206, but installed the new ATI drivers, then started in the default mode and then add the 206, and now all is WELL....Only used it for a few minutes but it really looks GREEAT, glad I got it..........Now to get the new INTEL MB and processor and will be off to the races!!! (until something new comes out):9 B42L8