FS2004 error on "exit" or on "end flight" Options

[Bahadir ALKES]

Dear Maddog users, I've been using this Maddog "the best simulation ever created for FS2004" for almost 2 weeks, and I must say, I feel like I've wasted all my time flown with other payware add ons. Maddog is really great, and folks, I've read and learnt a lot from the topics in this site. My personal thanks for all those, who contributed and shared their help here with us.

My problem is; Everything during flight or on the ground works just fine. But, when I decide "that's enough for today", I click on "menu" then "end flight" or "exit"; then it gives me an error message saying "FS2004 encountered an error" and restarts FS2004 automatically. I dont much care about it, but due to improper turn off, what if it corrupts FS files and ######, if I lose all those sceneries and add ons? I don't want to reinstall all over. The other add ons don't cause such an error, just with lovely MADDOG.

I am using FS2004, Vista home premium 32 bit, Maddog 2010 pro. I've read through the topic "installation and registration with vista" many times, did everything just as it said, even uninstalled and installed maddog a few times, nothing has changed. There is a very interesting point here...:

For example, start with cold and dark position, Start APU, go through all check lists, start engines, but don't move and shut down engines, close all systems one by one, you can exit or end flight properly; but if you take off, even if you turn back to the same aiport, you can not exit or end flight properly. Any solution for this?

And by the way; where the ###### is the TO / GA switch ? I am tired of Ctrl + Shift + G !!!


"Fair winds on your wings"


Bahadir ALKES





Edit....: all those #### s are very funny , first one was d_a_m_n_e_d, second was h_e_l_l

This post has been edited by Bahadir ALKES: 22/06/2010, 17:24

[fosl]

I have Vista Ultimate 32 bit and fly the maddog 2010. I get a crash upon exiting fs2004 every once in a while and it says Maddog gua unloaded. Ive done some testing on my system and it seems if I turn on the radar at any point in the flight then Ill get the crash while trying to exit. If I do not turn on the wx radar, no problems.

[Bahadir ALKES]

I have Vista Ultimate 32 bit and fly the maddog 2010. I get a crash upon exiting fs2004 every once in a while and it says Maddog gua unloaded. Ive done some testing on my system and it seems if I turn on the radar at any point in the flight then Ill get the crash while trying to exit. If I do not turn on the wx radar, no problems.

Sir, thank you for the answer, it is really interesting. I'll give it a try tonight and see if it is the cause of the problem. If it is, then maybe we can ask Mr. Marras to fix it, and pray for Mr. Marras to read this "official support forum", and "find" a solution. Perhaps it would be fair to say.....:

"The best add on ever, technical support by devs : never"

[Jon]

Dear Maddog users, I've been using this Maddog "the best simulation ever created for FS2004" for almost 2 weeks, and I must say, I feel like I've wasted all my time flown with other payware add ons. Maddog is really great, and folks, I've read and learnt a lot from the topics in this site. My personal thanks for all those, who contributed and shared their help here with us.

My problem is; Everything during flight or on the ground works just fine. But, when I decide "that's enough for today", I click on "menu" then "end flight" or "exit"; then it gives me an error message saying "FS2004 encountered an error" and restarts FS2004 automatically. I dont much care about it, but due to improper turn off, what if it corrupts FS files and ######, if I lose all those sceneries and add ons? I don't want to reinstall all over. The other add ons don't cause such an error, just with lovely MADDOG.

I am using FS2004, Vista home premium 32 bit, Maddog 2010 pro. I've read through the topic "installation and registration with vista" many times, did everything just as it said, even uninstalled and installed maddog a few times, nothing has changed. There is a very interesting point here...:

For example, start with cold and dark position, Start APU, go through all check lists, start engines, but don't move and shut down engines, close all systems one by one, you can exit or end flight properly; but if you take off, even if you turn back to the same aiport, you can not exit or end flight properly. Any solution for this?

And by the way; where the ###### is the TO / GA switch ? I am tired of Ctrl + Shift + G !!!


"Fair winds on your wings"




Bahadir ALKES





Edit....: all those #### s are very funny , first one was d_a_m_n_e_d, second was h_e_l_l

Interesting...seem to have the same issue...I'm also running Vista Home Premium 32 bit, 2010 Pro for FS9. I've only had it a handful of days, but think I've had the same issue after each mad dog flight. I always turn on the wx radar, too.
Oh, and the TO/GA button(s) are on the throttle (towards the rear....i.e., facing the cockpit door).

This post has been edited by Jon: 29/06/2010, 4:49

[gesto]

Have similar problem .No matter what I tried there is no remedy.Every time I decide to end flight the FS2004 switches off with error message.
Can we have an official reply to this ?

Setup: WIN7/64 ,nvidia 8800GT-Intel 2 6600 2.4Ghz

[kdfw]

I can confirm that with the WX radar on and exiting the flight, I get CTD. It's ok if the radar is off.

FS9, win7-64.

[Petrovich]

Same here.
That terrible error makes impossible turn-around flights without restarting FS.

FS9.1, Win7 Pro x64, MADDOG2008 Pro SP1

This post has been edited by Petrovich: 06/07/2010, 9:27

[Bahadir ALKES]

I can confirm that with the WX radar on and exiting the flight, I get CTD. It's ok if the radar is off.

FS9, win7-64.

Exactly, if the wx radar is off, you'll encounter no problems when exiting. Now that we know the cause, we are looking forward to receiving an update. I just don't understand why no one cares about the problems, the users face.

[shazapis]

Hello,

I get the same message occasionally. It is one of these things I've grown to cherish about the Maddog

Regards,

Spiros Chazapis
Athens, Greece

PS Did you get my second email about the multiplayer issue?

[Yu-Can]

Kept getting same error with Vista 64. Will try shutting down radar and see what happens...

[VulcanB2]

Hi,

I get it regardless. It is FSUIPC.

Best regards,
Robin.

[Bahadir ALKES]

I don't turn on weather radar anymore, and now FS doesn't CTD on exit. I don't think it is related with FSUIPC, it might be a code error on the software. Weather radar is real fun to use, but I can not use it due to this error. There is another problem with this aircraft which needs to be repaired. If you start with a default aircraft, switch NAV - GPS selector to GPS mode, then change aircraft to Maddog; your aircraft will make weird things on final approach. That's why, I recommend you to start FS with default Cessna or Boeing 737, switch to NAV mode, then change the aircraft to Maddog.

"Fair winds on your wings"


Bahadir ALKES

[kdfw]

I wish the developer will fix this CTD problem.

[kdfw]

I wish the developer will fix this CTD problem.

anybody there???

[comanche]

I wish the developer will fix this CTD problem.

anybody there???

Which is the problem if FS crash to desk when you close it? Unfortunately CTD occurs changing saved flight or loading a different aircraft.

Mauro

This post has been edited by comanche: 25/09/2010, 10:17

[kdfw]

I wish the developer will fix this CTD problem.

anybody there???

Which is the problem if FS crash to desk when you close it? Unfortunately CTD occurs changing saved flight or loading a different aircraft.

Mauro

not changing saved flight or loading different aircraft. just when closing flight after a flight w/ radar turned on. flight log file probably doesn't get updated with the completed flight.

[NeilC]

For me, it has nothing to do with wx radar (I rarely use it).

It happens after I land, change aircraft to Cessna 152 and save my default flight (so that I start off next time where I landed).

This seems to then cause FS9 to crash on exit.

BUT, this is not a problem to me, as I am leaving it anyway, so it doesn't matter.

Neil