Simviation Forums

Hello fellow FSX fans. I have set up this poll to use it to make my mind up whether to reinstall FSX to hope to cure my microstutter problem or whether to wait for SP1 and hope that fixes it. I have tried everything in the book to try solve my problem and it hasn't worked (eg. reinstall drivers, run virus/malware scans, run defrags and other software cleaners, reduce background processes, try different cfg lines and using a new one, trying different display settings in FSX and GPU drivers etc.).

Hello fellow FSX fans. I have set up this poll to use it to make my mind up whether to reinstall FSX to hope to cure my microstutter problem or whether to wait for SP1 and hope that fixes it. I have tried everything in the book to try solve my problem and it hasn't worked (eg. reinstall drivers, run virus/malware scans, run defrags and other software cleaners, reduce background processes, try different cfg lines and using a new one, trying different display settings in FSX and GPU drivers etc.).

Ususally its caused by a list of items all out of sync. Your hardware seems like it can handle the job assuming the sliders and config numbers are not exceeding the abilities of the hardware. NickN and I just went through a setup with a person http://www.simviation.com/cgi-bin/yabb2 ... 72157609/0 on a core2 and 8800 card. He is locking between 20-24 frames so if you are trying to run a 7950 at 28+ frames and high sliders/AG values, you are fighting a loosing battle.

Assuming the motherboard drivers are in order and you have set up Windows and FSX even somewhat correctly, in the Nvida driver panel, set Threaded Optimization to OFF and see if that may make a difference.

WindowsXP needs the Microsoft Dual Core Hotfix installed http://www.simviation.com/cgi-bin/yabb2 ... 1157795837 with the throttle registry key set to turn it on unless you are running an intel non-hyperthread based processor such as an E6300, Windows Vista or WindowsXP x64 (SP2 only also Win2k 2003 Server 64-32 SP2) which has been upgraded to incorporate the fix in the service pack. All A64 processors should have that installed along with any Intel that uses hyperthread technology.

I read Intel processors also have speed step and power save features that can cause stutters sometimes. I noticed in that thread NickN had Black ZR-1 shut down all that stuff but that may have been so the procesor would clock better too. I know when Black ZR-1 turned off Threaded Optimization in the Nvidia drivers it made a big difference but the E6300 is not a hyperthread processor too.

Setting up the system right and assuring the BIOS is running the processor and memory correctly along with setting up Windows for performance, http://www.simviation.com/cgi-bin/yabb2 ... 53;start=0

Hello fellow FSX fans. I have set up this poll to use it to make my mind up whether to reinstall FSX to hope to cure my microstutter problem or whether to wait for SP1 and hope that fixes it. I have tried everything in the book to try solve my problem and it hasn't worked (eg. reinstall drivers, run virus/malware scans, run defrags and other software cleaners, reduce background processes, try different cfg lines and using a new one, trying different display settings in FSX and GPU drivers etc.).

Ususally its caused by a list of items all out of sync. Your hardware seems like it can handle the job assuming the sliders and config numbers are not exceeding the abilities of the hardware. NickN and I just went through a setup with a person http://www.simviation.com/cgi-bin/yabb2 ... 72157609/0 on a core2 and 8800 card. He is locking between 20-24 frames so if you are trying to run a 7950 at 28+ frames and high sliders/AG values, you are fighting a loosing battle.

Assuming the motherboard drivers are in order and you have set up Windows and FSX even somewhat correctly, in the Nvida driver panel, set Threaded Optimization to OFF and see if that may make a difference.

WindowsXP needs the Microsoft Dual Core Hotfix installed http://www.simviation.com/cgi-bin/yabb2 ... 1157795837 with the throttle registry key set to turn it on unless you are running an intel non-hyperthread based processor such as an E6300, Windows Vista or WindowsXP x64 (SP2 only also Win2k 2003 Server 64-32 SP2) which has been upgraded to incorporate the fix in the service pack. All A64 processors should have that installed along with any Intel that uses hyperthread technology.

I read Intel processors also have speed step and power save features that can cause stutters sometimes. I noticed in that thread NickN had Black ZR-1 shut down all that stuff but that may have been so the procesor would clock better too. I know when Black ZR-1 turned off Threaded Optimization in the Nvidia drivers it made a big difference but the E6300 is not a hyperthread processor too.

Setting up the system right and assuring the BIOS is running the processor and memory correctly along with setting up Windows for performance, http://www.simviation.com/cgi-bin/yabb2 ... 53;start=0

But the draw back is that its not as good as 30FPS if you know what I mean.. but the stutters are gone which is good.

PS: Will turning TO off in the drivers affect performance in games which use 2 cores well?

That TO setting may have different influence depending on the game. Like anything else you have to experiment.

Ace, what miltest said. I too came to a conclusion that you don't need 30+ FPS to enjoy this sim. I have my frame locked at 20, and with all the eye candy you can't even tell it's at 20 because it runs so smooth. Don't get the impression that you need 30 FPS to enjoy this sim. It's not true. If you take a look at my video, you're seeing 20 FPS with the exception of FRAPS stealing 4 - 6 and I also have my frame rate counter off as well. That's another 2 - 3 frames right there.

Look at the start of my thread and where it ends for now. It took me over a month to get this right. You have to follow the directions word for word. Do NOT skip anything! If it tells you to boot, boot. Do not skip any defrag steps, even if it takes 13 hours (like mine did).

But you have to keep in mind that I'm over-clocked. So my numbers might not work for you or others on this board. You have to mess with the #'s according to your system specs to achieve what you're aiming for.