P2 hangs up after mission is over

OK good that's 1 thing ruled out.

No need we understand what it looks like ;)

Well something else is causing it firewall? Unplug from internet. Shutdown firewall (some actually need you to uninstall even when disabled btw).. try that.

Windows Firewall turned off (can't uninstall AFAIK), same thing, added all OFF and CFS3 exe's to the exception list, same thing..
 
I'm allowed one STUPID question per thread, so here it comes:

Please tell me you weren't maxed-out, on terrain & scenery :ernae:
 
Ok, time to get serious.

I'm on XP 32 Professional, you're on Vista 64, so I'm not sure what the equivalent name in Vista is, but in XP I would go to Administrative Tools and look at Event Viewer. When that opens, click on Application. Do you see any Error or Warning messages? If so, do any mention OFF or CFS3? After you have checked that out, click on System and again look for any Error or Warning messages.

To be honest, I'm not sure what messages you might get and whether they might give you any clues as to the true problem, but it can't hurt. Report back and I or someone smarter than me will help you to track down the problem.
 
I'm allowed one STUPID question per thread, so here it comes:
Please tell me you weren't maxed-out, on terrain & scenery :ernae:
No question is stupid. No, the only thing on 5 is Plane detail, everything else on 4 except clouds, which are on 3.
 
Ok, time to get serious.

I'm on XP 32 Professional, you're on Vista 64, so I'm not sure what the equivalent name in Vista is, but in XP I would go to Administrative Tools and look at Event Viewer. When that opens, click on Application. Do you see any Error or Warning messages? If so, do any mention OFF or CFS3? After you have checked that out, click on System and again look for any Error or Warning messages.

To be honest, I'm not sure what messages you might get and whether they might give you any clues as to the true problem, but it can't hurt. Report back and I or someone smarter than me will help you to track down the problem.

It's Event Viewer here in V64 also. There were no warnings or errors at all. I just did a Quick fly and wrote down the time, went into EV under Applications and there were two "info" entries for the exact time it hung up.

First one was "Request to disable the desktop Window Manager was made by process (Microsoft Combat Simulator 3)

Second one was "Desktop Window Manager unable to start because composition was disabled by a running app"..

The PID's of OFF Manager and the temp file were not listed in the details portion of the messages..
 
Normally a temp file should not come into it, very odd. almost like a permsissions thing Still P2 was not designed or tested for Vista.

Longs shots, try different screen res for OFF in CFS3Config?
Latest video drivers?
Try different video settings?

Try backing up configoverrides.xml then running cfsconfig and setting to "yuk" defaults.

Did you try setting OFF NOT to run as admin?


-or- get P3 which is tested on Vista 32/64


Oh yes and the old fix try that... run CFS3 once. Quit. Now goto OFF and fly and see..
 
Hey GaryR try this: after it happens - reboot - run CFS3 for a min or so - start OFF, when u get to where pilot's sitting by the crates go to display options and move all your sliders to 2, clouds to 1 - fly qc. See if it helps
 
"Desktop Window Manager unable to start because composition was disabled by a running app"..
Hmmm, that's a strange message. Typically cryptic Microsloth bull***t. The obvious question is, "Why is OFF still running and not allowed to quit normally?"

I assume you have all of the latest service packs and updates installed and all drivers are up to date. You might try using an older graphics driver version. I've heard that some of NVidia's latest drivers don't work as well as older versions on some sims. Other than that, I'm about fresh out of ideas. Let me scratch my noggin' for awhile and get back to you. Sorry we haven't got it licked yet!
 
Not offering this as a possible solution, merely as information. Prior to 1.9e we had to face the Hang-On-Bug, granted we were on XP, but we had a workable fix, if not permanent, workable.

Prior to entering OFF, we would start CFS3, but never play the game itself, as soon as the intro movie was over, and we were presented with the P47 in front of it's hanger, we'd quit CFS3. Then select OFF, you'd be good to go for that evening, but if you left Off for any reason. You were sure to meet the Hang-on-bug again. Not Perfect by any standard.

But better than a poke in the eye with a sharp stick

Can't Hurt If it WORKS . . . :ernae:
 
As suggested by others, it's the exact symptoms of the hang on exit bug. It was fixed in one of the P2 patches. I know the patch worked because I had the HOE bug on my old pc and the patch fixed it. Maybe the patch didn't "take" for some reason on your pc ?

In any event, first fire up CFS3 to the main menu at least then exit. Then load P2 and see if that stops the hang.

Otherwise a vista issue perhaps ? Can't help there sorry.

edit: Dang ! Gimp beat me to it :bananalama::costumes:
 
As suggested by others, it's the exact symptoms of the hang on exit bug. It was fixed in one of the P2 patches. I know the patch worked because I had the HOE bug on my old pc and the patch fixed it. Maybe the patch didn't "take" for some reason on your pc ?

In any event, first fire up CFS3 to the main menu at least then exit. Then load P2 and see if that stops the hang.

Otherwise a vista issue perhaps ? Can't help there sorry.

edit: Dang ! Gimp beat me to it :bananalama::costumes:


Not proposing that I know what the issue is yet but its not exactly the same as the HOE bug as this tmp file that Gary talks about is new to me and suggests some AV etc is monitoring and halting execution - but I am guessing.

Bottom line is that P2 was not released as Vista compatible however many seem to have gotten it running on Vista 32 and 64 so it is worth persisting.

HTH

WM
 
Another point, which I would have seen earlier had I ran CFS3 more than the one required time before installing OFF P2. Upon exit of CFS3 it goes to the desktop normally but if I look in Task Manager both CFS3.exe *32 AND ~f1d055.tmp *32 are still running. If I kill the temp file CFS3 dies also. I've looked in MS Technet and the Windows Desktop Manager process can be disabled, which I did. Same result except the Info notation in Event Viewer doesn't come up. You can also (which I missed) disable it in Compatibility. I was running with UAC off, which greys out the "Run as Administrator" checkbox. I was running the exe in "XP Compat mode" and using the "Run as Administrator" selection in the drop down (which I doubt does anything). I have a program called TweakUAC" that allows me to run UAC in "Quiet" mode (disables all the stupid popups but retains UAC protection). Tried running with "Run as Admin" checked, same results.

Also tried all the other suggestions above, samo samo. I even disabled "ReadyBoost" to see if that's an issue, it isn't.
One other quick point, ~f1d055.tmp is in the Appdata\Local\Temp folder and created by CFS3. Deleteing it did nothing. Also, in CFS3, even though I quit by ending the process I am able to save my campaign before doing so..
Thanks for all the suggestions!

Leaving for the PO now, maybe P3 is there waiting! The sad reality is that as this is an issue with CFS3.EXE I believe it will still be there with P3, rendering it useless to me.
 
P3 arrived!! Installed right over P2 with no issues, then installed 1.1 patch, then ran a Quick Mission. Knocked down an Albatross, landed, then exited mission... went directly to Pilot records!! I then left the game. Guess what? NO ~f1d055.tmp process!!! AMEN!

Newbie thing, but quick mission results don't show up in your Pilot Dossier, correct?

Time to go try the 1st Campaign mission... looks GREAT!
 
Did we mention p2 isn't tested in Vista :) it works for many but obviously not for some.

P3 is tested in Vista and weeee it works.
Good news GaryR

Your question -yes default is not to log QC stuff.. you can change it in ... workshop
 
Not proposing that I know what the issue is yet but its not exactly the same as the HOE bug as this tmp file that Gary talks about is new to me and suggests some AV etc is monitoring and halting execution - but I am guessing.

Bottom line is that P2 was not released as Vista compatible however many seem to have gotten it running on Vista 32 and 64 so it is worth persisting.

HTH

WM

Fair point WM. perhaps I was too hasty with using the word "exactly". I should mention that I used to get the P2 exit hang (before the patch fixed it woohoo !) and also got the ~f1d055.tmp *32 file at the same time if that's of any use to you. That's why I thought Gary had the same issue I had (apart from the fact the patch fixed it for me but not for Gary). But that was all on my old pc (XP home). My new pc has no such problems and no unusual temp files (XP pro) :) so it's all good :bananapowerslide:
 
Glad you got OFF3, GaryR, and that it works! :jump: Now, go out and get some kills! :karate:
 
Back
Top