FSX with VOXATC 5.63When I try to start FSX with a flightplan, it CTDs. This morning, I loaded a FlightPlan with the Flight1 Islander, and I was ready to go, meaning, the flight plan loaded and I was inside the cockpit of the plane. Then I realized the plane did not have VOXATC configured for it.I went and did the Re-index and the Panel setup. Now when I load the flight plan, I get CTD. This has happened before, and the only solution I have found is to re-create the FSX.CFG file, which, then I have to tweak again for my liking. This gets old very fast.Any help will be greatly appreciated

Sad to read about CTDs there, ssanchez.Do you have some more details on the actual circumstances when they happen?When do you load that plan, what was set up in FSX before, which aircraft/situation is active there, what is the windows event log showing after this happened?

Sad to read about CTDs there, ssanchez.Do you have some more details on the actual circumstances when they happen?When do you load that plan, what was set up in FSX before, which aircraft/situation is active there, what is the windows event log showing after this happened?

When do I load the plan? From the FSX start screen, where I select Plane, Airport etc. What was set up in FSX before? Im not sure I understand the question. If you mean if the FP was in FSX before, yes, I get CTDs also whit existing Flight Plans.Which Aircraft or situation? ANY aircraft that is added to VOXatc will CTD. I did not have the CTD with the Islander until I added it to VOXAtc.Windows event log, Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module terrain.dll, version 10.0.61637.0, time stamp 0x46fadb59, exception code 0xc0000005, fault offset 0x0005595e, process id 0x93c, application start time 0x01cb9f9631b3d136.Fault bucket 547655984, type 1Event Name: APPCRASHResponse: NoneCab Id: 0Problem signature:P1: fsx.exeP2: 10.0.61637.0P3: 46fadb14P4: terrain.dllP5: 10.0.61637.0P6: 46fadb59P7: c0000005P8: 0005595eP9: P10: Attached files:C:\Users\Sergio\AppData\Local\Temp\WER77EF.tmp.version.txtThese files may be available here:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report09059e63Content of the WER fle are hereVersion=1EventType=APPCRASHEventTime=129372478942779974ReportType=2Consent=1UploadTime=129372478973129974Response.BucketId=547655984Response.BucketTable=1Response.type=4Sig[0].Name=Application NameSig[0].Value=fsx.exeSig[1].Name=Application VersionSig[1].Value=10.0.61637.0Sig[2].Name=Application TimestampSig[2].Value=46fadb14Sig[3].Name=Fault Module NameSig[3].Value=terrain.dllSig[4].Name=Fault Module VersionSig[4].Value=10.0.61637.0Sig[5].Name=Fault Module TimestampSig[5].Value=46fadb59Sig[6].Name=Exception CodeSig[6].Value=c0000005Sig[7].Name=Exception OffsetSig[7].Value=0005595eDynamicSig[1].Name=OS VersionDynamicSig[1].Value=6.0.6002.2.2.0.768.3DynamicSig[2].Name=Locale IDDynamicSig[2].Value=1033DynamicSig[22].Name=Additional Information 1DynamicSig[22].Value=fd00DynamicSig[23].Name=Additional Information 2DynamicSig[23].Value=ea6f5fe8924aaa756324d57f87834160DynamicSig[24].Name=Additional Information 3DynamicSig[24].Value=fd00DynamicSig[25].Name=Additional Information 4DynamicSig[25].Value=ea6f5fe8924aaa756324d57f87834160UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeUI[3]=Microsoft Flight Simulator® has stopped workingUI[4]=Windows can check online for a solution to the problem.UI[5]=Check online for a solution and close the programUI[6]=Check online for a solution later and close the programUI[7]=Close the programState[0].Key=Transport.DoneStage1State[0].Value=1State[1].Key=DataRequestState[1].Value=Bucket=547655984/nBucketTable=1/nResponse=1/nFriendlyEventName=Stopped workingConsentKey=APPCRASHAppName=Microsoft Flight Simulator®AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeThanksSergio

Sorry, the event log doesn't seem to help here, very generic modules there, no triggers as far as I can see.Are you using FSInn by any chance? I had a flight plan loading problem there, that's why I'm asking.So if you open FSX and that default trike is rotating, you load a flight plan and get a CTD? Does "Added to VoxATC" mean that you ran the VAPanelSelect app and selected that plane there? This app just edits the panel.cfg of the chosen plane, no fsx.cfg change or any other changes done. So it can't trigger a fault on loading flight plans by design.The only thing which comes to my mind is that the app adds some faulty entries and the gauges therefor cause errors.Can you look up e. g. the panel.cfg file of the BN2 Islander and post the [Window Titles] section and the VoxATC entries? You can find the file here SimObjects\Airplanes\Flight One BN-2 Islander\panel and the entries should look like this[Window Titles]Window00=No 2D PanelWindow01=Mini PanelWindow02=KLN90 GPSWindow03=VoxATCWindow04=VoxATC Recent Comms////<VoxATC[Window03]visible=1position=4size_mm=400,200pixel_size = 400, 200background_color=0,0,0ident=14077zorder=5alpha_blend=0.65gauge00=VAGauge!VoxATCPrompt,0,0////>VoxATC////<VoxATC[Window04]visible=0position=5size_mm=400,600pixel_size = 400, 600background_color=255,255,255ident=14078zorder=5gauge00=VAInfo!VoxATCInfo,0,0,400,600////>VoxATCIf they do, all entries are correct and only the gauges itself could be faulty or missing to cause any problems. There should be two present in the Gauges folder of FSX. VAGauge.gau and VAInfo.gau.Please make sure to run the panel app and VoxATC itself as Admin to give them sufficient rights for changing panel files and stuff.

Thanks for your help and time.Yes, where the Trike is rotating, if I go to load or create a flightplan, I get CTD after creating the flightplan when trying to go back to the rotating trike screen.If I load a flightplan while in the cockpit, I get the same. As I said above, I was able to load a flightplan with the Islander until I realized it was not in VOXATC so I went out completely of FSX, did a indexing, then the panel setup utility (ran both as admin) then went back and when loading the FP, I got CTD. Yes, I use FSINN, and no, uninstalling is not an option. both my VAs would hang me. Besides, as I said before, re-doing the FSX.CFG file fixes the issue, is just that I dont want to re-do all my mappings and settings and tweaks everytime I want to fly with VOXATC.Here are the entries for the panel.cfg for the Islander. Both gauges are in my gauges folder[Window Titles]Window00=No 2D PanelWindow01=Mini PanelWindow02=KLN90 GPS////<VoxATCWindow03=VoxATCWindow04=VoxATC Recent Comms////>VoxATC////<VoxATC[Window03]visible=1position=4size_mm=400,200pixel_size = 400, 200background_color=0,0,0ident=14077zorder=5alpha_blend=0.65gauge00=VAGauge!VoxATCPrompt,0,0////>VoxATC////<VoxATC[Window04]visible=0position=5size_mm=400,600pixel_size = 400, 600background_color=255,255,255ident=14078zorder=5gauge00=VAInfo!VoxATCInfo,0,0,400,600////>VoxATCSo, I guess everything checks out... but I still get the CTD

The FsInn stuff triggers the problem here, I had and still have this too.Workaround 1As you most of the time will use either FSInn or VoxATC, you can disable (not uninstall, just avoid loading) the FSInn dll (which is the following entry in your dll.xml file (near the fsx.cfg) <Launch.Addon> <Name>FSCopilot</Name> <Disabled>False</Disabled> <Path>Modules\FSCopilot.dll</Path> </Launch.Addon>Workaround 2The other workaround is to avoid loadig flight plans on the free flight screen (where the airplane's rotating) but to load a flight plan later, when the actual location (e. g. at the gate) is loaded. This works for me even if the mentioned dll is active.Be aware that FSInn is beta and try to test the disabled dll to see that your FSX will behave normally then. I don't know which thing is the culprit here but the FSInn dll surely triggers this strange behavior with CTDs. If you want to have both things active, use the second workaround. No uninstall needed, just some attention.You are right, the panel.cfg entries of yours are correct. No problem there.

CoolIP,You have saved my Christmas. :( Workaround number 2 will not work, because VoxAtc is not loading the flight plan when Im in the cockpit, but disabling FSINN has allowed me to fly using VOXATC againThanks!!!

Glad to read this, ssanchez. :(