I used to be able to run missions, CV69-12, T-45C Goshawk Carrier, CarrierOpsfsxf18.    Now when I run the missions, it loads, my screen goes black, and I get

CTD simscheduler.dll.

 

I can run aicarriers and land on the USS Nimetz, etc.   Also, missions that use the default FSX carrier work fine.     Anybody have any ideas.   I can not think of what could have changed to start causing this. 

 

Any help would be appreciated.

 

 

Bill

This is an automatic message.

 

This topic has been moved from "MS FSX Missions Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Try disabling User Access Controls (UAC).  Goto the Start Button and type User Access then look up in the menu and click on How to change User Access Controls.  Move the slider all the way down.

 

Best regards,

Jim

Jim

 

UAC was already off.

Since it applies to missions, try renaming your logbook.bin (in your MyDocuments\FSX folder) to logbook.old.  Restart fsx and see if the problem still persists.  If it does, then your logbook.bin is corrupt.  There's a repair utility in the AVSIM Library.  You may also be missing component a component of the mission which means a FSX/Acceleration repair or complete uninstall/reinstall.

 

Best regards,

Jim

Jim

 

Renaming Logbook did not solve the problem.   I tried searching for the repair utility, but I came up empty.   Can you point in the right direction to fine it.

 

Thanks

Jim

 

Renaming Logbook did not solve the problem.   I tried searching for the repair utility, but I came up empty.   Can you point in the right direction to fine it.

 

Thanks

The logbook may not be corrupted then but here is the link to the LogBookRecovery program - http://library.avsim.net/download.php?DLID=98186.  I'm running out of suggestions in the event this does not work.  I ran FSX in Kiosk mode and had no issues whatsoever.  If you can load FSX normally, the Kiosk mode should work too.

 

Best regards,

Jim

I just noticed the missions did not come with FSX and probably were addons from FlyAway Simulations.  This is most likely the problem.  You'll have to go to the developer of that product and see if he/she has a solution to the mission.  Make sure all of the components of the mission(s) are installed in FSX.

 

Best regards,

Jim