FSCopilot 1.7 CTD

[Tim A]

I'm using the beta FSInn1.3/FSCopilot1.7 with FSX and Vista Home Premium. PC is core Duo 2.4GHz, 2GB Ram, 750GB HD, Nvidia 7950Go/512MB gfx.

Situation: In the main user interface screen, loading a flight plan within the free flight screen causes FS to crash to desktop. Moving to the free flight screen from the settings or pilot records screens causes the same problem. The error is logged in the windows Application log as follows:

Faulting application fsx.exe, version 10.0.61355.0, time stamp 0x4643ee0a, faulting module FSCopilot.dll, version 1.2007.508.1, time stamp 0x4640a058, exception code 0xc0000005, fault offset 0x00034f10, process id 0x1514, application start time 0x01c80f6b47b029aa.

Deleting (or renaming the extension) of FSCopilot.dll prevents the problem.

Flight plans can be loaded/created from within the sim without crashing. The problem seems to be specific to the free flight interface. It's a real problem if the default flight has a flight plan associated with it, since FS will not start, and if FS opens on a screen different to Free Flight, you are also in a bind.

FSInn/FSCopilot has been thoroughly removed (including deleting start menu entries & scrubbing the registry) and reinstalled multiple times, to no effect.

The other CTD which causes problems (including collateral damage to fsx.cfg) is the 'pure virtual function call' error. It can occur multiple times in a session, or not at all. It seems to occur when 'something happens', e.g. opening the chat window, switching views etc. Unfortunately, the error log is unhelpful in this instance:

Faulting application fsx.exe, version 10.0.61355.0, time stamp 0x4643ee0a, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x458b0c46, process id 0x3e8, application start time 0x01c809d43d61f5c0.

These two issues are really all that is spoiling (for me) an otherwise excellent app.

Tim

[L. D. James]

I'm sure we'll be able to figure out the problem. Start off by uninstalling again FSCopilot/FSInn. During this uninstall, insure that there is no fscopilot.dll in the modules directory of FSX.

Insure that you have FSX/SP1 installed. Insure that FSX had been upgraded to SP1 on a clean install.

Install the FSInn1.3 package.

Follow the steps in detail at: http://forum.apollo3.com/dcboard.php?az=show_topic&forum=110&topic_id=17&mesg_id=17&page= .

Let me know if any of the steps are unclear or if you have problems doing any of them.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

[Tim A]

All done by the book. (I can't set 'run as administrator' though, since UAC is turned off and the option is greyed out). Anyhow, FSInn is fine "in sim", it's just in the outer UI shell there's a problem.

I'm sure it did work in the past!

Hmmm, just had a thought.... <goes away>

<comes back>
Don't know why I didn't think of it before - Heck I even mentioned potential damage in my original message! I just renamed the fsx.cfg file, so it built a new one, and presto! I can open flight plans again! :-) Of course, now I have to reapply all the cfg tweaks LOL ...

That just leaves the 'pure virtual function call' CTD (and yes, I do have the C++ runtime installed)...

Thanks,
Tim

[L. D. James]

The check mark is a requirement. Is there a check mark in the three modules? You're right, turning off UAC will make the change unavailable. However, it won't remove the check mark. You'd have to turn UAC on to have access to placing or removing a check mark from the option.

There might be other problems, but I would hate to try to fix a different part that might not be broken when the culprit might be a simple missing check mark.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

[Tim A]

Okay, I'll switch on UAC, set the checkmarks and switch it off again. Since the CTD doesn't happen every session, it may take a while to establish a probable cure (absence of proof is not proof of absence, etc). Will let you know...

Cheers,
Tim

[Tim A]

The pure virtual CTD hasn't happened yet. But the CTD on loading flightplans/changing screens is back, and I have to delete fsx.cfg again. This is so frustrating! :-(

[L. D. James]

Sorry about the frustration, I'm sure the matter is simple. There are steps that have to be done to identify the problem. Some of the steps are somewhat timely, but so far they have worked every time.

It might help you to lose some of the frustration if you take into consideration that I'm the one doing the analysis and giving the suggestions, and if you would just take your time and do the steps and report what you see.

Because FSInn has worked in every environment I've tested, including such old machines that Windows Vista/FSX will actually drag and barely work.

If you've carefully done all the steps to the exact letter and are still having problems, I would suspect your problem might either be some other program or install that is interfering with FSX's operation, there's some problem with the integrity of the FSX/SP1 install or a problem with the OS install.

You can verify the first two considerations by doing a full uninstall of FSX. You can back up your Documents\Flight Simulator X subdirectory so that you can restore your awards and other configurations later.

After this full uninstall, start over with the steps:

Installing FSInn
http://flightsim.apollo3.com/docs/fsinn/connectiontovatsim.htm

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

[Johnno]

Hi Larry. I'm a long time FltSimmer with real flying experience and have had FSX since day 1 .....with Vista.

I run a local FS group here in Oz and we fly online together every week....but there we only use FS9 with XP. For FSX I have the latest computer setup with the 8800 card, and for FS9 I have another computer with XP. In FS9 we use both SBox or FSInn no problems. Now I really like FSX except for the fact that we cannot get online with Vista.

I read forums galore and everyone seems to have major probs with FSX/Vista so I was somewhat cheered by your Oct.10 update on this subject........however having had several huge crashes over the years which required the reinstallation of the base programs plus all the addons (heaps of them), I am very wary about trying the 1.7 and 1.3 versions for my FSX machine.

What I'm really asking is.....should I go ahead with 1.7/1.3 for my FSX/Vista setup at this point in time......or am I stepping into dangerous waters? To have to reinstall everything yet again would blow my brain.....would rather wait until all is proven 100% OK to use.

Regards from John White, VH-EKW Coffs Harbour NSW Australia

[L. D. James]

How are you doing, John. You're saying you're experiencing CTD's? That's the name of this subject thread.

If that's what you're experiencing, there is already a problem with your installation. The first thing you should do is check your drivers and insure that FSX will run with your environment before even installing any version of FSInn.

If you're experiencing something different than the symptoms described in the beginning of this thread, please start a new one for the sake of resolution flow.

Put a brief reference of the symptoms or subject matter of the new thread. The new subject (if it's new) will make it easier for others who has a similar question to find the answer, or know where to put their additional information on the matter.

Again, CTD's can be can also be a result of having a faulty power supply, or one that's rated lower with lower watts than the minimum requirement for the video card. Check those factors first.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames