Jump to content
The simFlight Network Forums

simtim

Members
  • Posts

    3
  • Joined

  • Last visited

simtim's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Blame it on user error! After much playing around, I finally solved my CTD problem. Peter, thank you very much for your response. I did not mean to sound like I was blaming you or FSUIPC. The solution actually came to me while writing the original message on this board. When I wrote, “virus protection…is enabled” something clicked in my brain. I completely uninstalled my virus checker. That took care of about 50% of the crashes. The other half was taken care of when I updated the graphics driver. Sounds simple – but I am using a laptop which means there is no support for device drivers from the original device manufacturer. I had to go through the computer’s maker, who had not released a new driver for my graphics since April. I managed to get one anyway through a mod of the desktop version. Not the best solution, but it works. No more crashes, and I can once again enjoy my flights!
  2. First off, I have used Flight Simulator with FSUIPC for years. I love the combination, but lately I have had more problems with FSX than I can seem to solve. Any help would be appreciated. I was having many CTD errors prior to today, and since SP2 was just released, now seemed to be a good time to do a reinstall. First I uninstalled my entire setup including third-party programs and did a reboot. Then, I installed FSX, followed by SP1, SP2, and then FSUIPC4. After that I installed my third-party programs. After each install I ran FSX and rebooted. Unfortunately, after all that I am still receiving crash-to-desktops. All this came about because I decided to reinstall FSX after several months of having it off my system. In my initial installation of FSX without FSUIPC I never received a CTD, which is why I tend to suspect it. I always run FSX in “administrator mode” and have given ownership rights of the directories specifically to me in Vista Ultimate. For virus protection I use “Windows Live OneCare” which is enabled during flights. The CTD occurs during several different occasions. Most often it occurs after I initially load FSX and start making selections within Free Flight mode. Usually it occurs when I select real-time weather, but it has also occurred when I make other selections such as aircraft or origin airport. The CTD happens whether or not I am using a default aircraft or an add-on. On the rare occasion when I get through the Free Flight menu successfully, I have always received a CTD when I am in the cockpit before takeoff. The occurrence appears to be random – sometimes I am just sitting there when it bugs out. Other times I am moving my mouse about to make a selection. The third CTD type I receive is when I am in the cockpit and hit the alternate key to bring up a menu. I can always make the choices within the menu, but it has never failed to CTD once I select “OK” to get back in the cockpit. I have never been able to take off in Free Flight Mode. To be absolutely clear, when I say “crash to desktop” it means I receive a “fatal error” and Flight Simulator exits and restarts. I am also certainly open to the possibility that FSUIPC is not causing my problem; after all, I have used it error-free for years. Granted, it very well may be user error. My setup is FSX Deluxe with SP1 and SP2 under Windows Vista Ultimate. I don’t use Acceleration yet, but I have it on order. For add-ons I use registered FSUIPC4, Level-D Boeing 763, FS2Crew for B763, Ultimate Traffic, Radar Contact, and FSBuild. My computer’s device drivers are all current. I run an Alienware M5790 “Area 51” laptop with 2048 MB RAM, 2.67 MHz clock speed, Intel Core 2 CPU, ATI Mobility Radeon X1900 video with 256 MB video RAM, and a Logitech Extreme 3D Pro joystick.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.