casinoroyal

Fellow sufferers of fsx freezing, I think I've found my own solution. It took me over a month (5 weeks) of diligent and tiresome effort to discover this, but now I finally have the information that I believe has solved my problem. I apologize in advance, because this will very likely have absolutely no application to your own problems, although it might. For me the issues I was experiencing derived from two separate sources. The first causative factor for me, and by far the more serious had been an incompatibility between my game and my VA's tracking system. This freeze would typically manifest within about 2-3 hours of game play and was never recoverable (never "unfroze" itself). The second type of freeze was caused by my adjusting the cloud draw and frame rate sliders far beyond what my machine is capable of handling. This problem would usually initiate within 2 hours of flight time, manifest recurrently throughout the duration of the flight at regular intervals (every 15-30 minutes) and would always unfreeze within 5-10 minutes. The fact that it did unfreeze has led me to believe that this issue has some bearing on our common dilemma and hopefully my personal solution (adjusting the cloud draw and frame rates downward) has some relevant application for others out there. Anyways, as I said before, I wanted to return to advise everyone of when I found a solution for my problems and what it consisted of. I urge you all to do likewise, that way we will have a collective knowledge base of problems and corresponding solutions, which will hopefully provide assistance to those in distress with fsx freezing issues. Good luck to all of you and I hope that this helps someone.

Yes sir I have tried using that file, but it apparently has no effect for me. I know that I've had multiple freeze inducing issues occurring simultaneously, so while that may address one of the causes, there has always been something else in the background which I've never really been able to identify. I could try using that file again though, but I think this is something to do with that simconnect.dll file. Whenever I used to get information from event viewer, it would typically cite that as one of the faulting files. Unfortunately, in the course of my more recent freezes, event viewer has never logged any errors or messages which correspond with fsx problems. Thanks again.

Well thank you again for your informative contribution. I will certainly report any progress I've made toward achieving a workable solution. Now I'm thinking it has something to do with the virtual airline tracking system that I run in the background, as I flew about 2 hours last night an then the game froze once again. After that, I started fsx independent of any other ancillary programs and came back over 8 hours later to find the game running just fine (also after having turned up cloud draw and increased frame rates). I can't say for certain whether its the ACARS system thats inducing my freezes, but its beginning to seem so. Best of luck on your continuing journey to achieving your own final resolution to any fsx issues yet outstanding and thanks again for the advice.

Jim, you're very right about the sliders having significant bearing on performance, with even high end machines such as mine. I know for me the cloud draw distance appears to have a dramatic effect on the frequency of the freezes I have experiences, and likewise, the frame rate has an impact as well. I might have solved my particular problem last night actually; after a month of contending with this nonsense. With me, since this all derived from a reinstallation of the game as a consequence of what I wrongly interpreted as performance issues that has resulted from an ineffective virus repair/restoration, the real fundamental and underlying issue was whether my reinstallation was a causative factor in this. It turns out that it possibly was. I had been imprudently attempting to transplant various game modifications the quick and dirty way by just copying and pasting folders and files into the fsx main directory. Obviously this was risky and foolish in terms of its potential for causing subsequent compatibility issues. I'm not entirely certain that this was the root cause of my problem, but after having completed a DTW to RKSI long-haul in conjunction with an ACARS program and without any incident, I'm inclined to think it may have been. Thanks again for your continuing help and I will be sure to return here in the next few days and post my findings after more test flights.

Jim, thank you for your insightful and helpful comment. I never thought the problem could have derived from a hardware type issue, but what you say is very sensible. I lack the technical expertise to make the types of adjustments which you speak of however. I have been told by various people familiar with my particular problem the best option in terms of guarenteeing restoration of fsx to full functionality would be to just reformat windows. I should mention that I do not experience freezing with other graphically intensive games (Rome and Empire Total War), and that is why I suspected this was related to some anamoly in fsx. Thanks for your assistance.

Gentlemen, I feel your agony, as I too unfortunately suffer from these aggravating and inexplicable crashes. After having carefully read this thread in its entirety, it appears as though my particular problem does differ slightly from the one which is recurrent throughout. It began about a month ago after I unwisely permitted Best Buy to work on my rig for virus repair/restoration issues. Prior to that, I had been enjoying fsx nearly without incident for about 2 years. When I got the machine back, I noticed that typically after about 1-2 hours of flight time, my screen would just freeze. The program would be completely unresponsive to any inputs and the freeze would affect all visual rendering, yet the ambient/background sound would continue. One month later and after innumerable attempts to solve this problem (4 reinstallations of fsx alone), it persists. Others have mentioned the frame rate adjustment having bearing on it, but in my experience this has no discernable impact. With my particular rendition of this issue, the game doesn't appear to reset or continue after a delay, but rather it is perpetually stuck in the frozen limbo. I have to access task manager to shut down fsx. Furthermore, a tracking program I use in tandem with fsx is also unresponsive after the freeze occurs. I have Win 7, 64 bit, 6 gigs ram, quad core and a Radeon 5800 HD card. I'm thinking this is a graphics issue, as lessening the cloud draw has seemed to reduce the incidence of this problem. Finally, unlike the majority of those here, for me the issue manifests at much more regular intervals say, every 2-3 hours and occasionally even more often than that. Obviously, it is hugely detrimental to my enjoyment of fsx, as I'm sure it is with you all. To reiterate what someone else has already stated; if anyone out there has found a solution, please share it and deliver us all from this horrid blight.