Hola, can someone explain to me why I keep getting microstutters on my updated system. The sim does run alot smoother than my old AMD 3400, with 2gig of sigle channel memory and a 6800GT video card. Now Im running dual channel memory, but for some reason, I still get micro stutters here and there when turning on the ground or banking in the air. I have removed Utimate Terrain to see if that was the issue, but no its still there, I have removed my mesh scenery for most of the USA (the free onces from here at avsim) and the stutters are still there. Hmm, what could I do to have my sim run butter smooth? Like I said, when there are no micro sutters, it runs like a dream with everything cranked and Activesky running on the second core, plus Radar Contact.Thanks all,Bill

> Hmm, what could I do to have my sim run>butter smooth? Like I said, when there are no micro sutters,>it runs like a dream with everything cranked and Activesky>running on the second core, plus Radar Contact.>>Thanks all,>>BillIf you want to get rid of the microstutters you need to uncrank your settings and spend a little time tuning FSX to get to your optimal sweet spot.Also, if you are running SP1 or SP2 FSX is multicore aware. There is really no benefit to assigning ASX or Radar Contact to run on core 2 exclusively.Also, are re you locking your framerates or are you running them on unlimited?

Hi, I'm using FS9 and have the frames locked at 30.Thanks for the reply,Bill

Hi Bill,This is a very complex problem (or perhaps a multitude of problems) with no consistent solutions that have ever been presented here to the best of my knowledge. Oh there are boatloads of personal annecdotes, but they don't always apply. I think this is because there are multitudes of contributing factors.Even so, some stuff seems to repeat and so may apply more often. Here are some:1. Get the cleanest possible boot environment, with all non-critical processes & services stopped. I've had my best luck setting up a new hardware profile that is associated with the very lean boot up, getting services and processes running at boot up down to 17 or 18.2. Be on guard for AV and AS software that might be operating in the background. Some services are tricky to disable. Use a low overhead AV/AS package, even one you can essentially disable by running a new hardware profile that disables the services a Windows initialization.3. Make sure all traces of former video drivers are out of your system. 4. Rebuild the FS9.cfg file. Sometimes there are settings in there, or the video card needs to be resensed, so that a simple delete of this file and auto-rebuild on the next FS9 start can solve some troubles.5. Reinstall DX9.x after you've installed a new video driver.6. Lessen the quantity of autogen. Textures that update can cause microstutters. Using effective texture configuration can help. Here are mine currently:[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=20TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=3TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=9.000000 TERRAIN_EXTENDED_RADIUS=9.000000TERRAIN_EXTENDED_LEVELS=232The problem is, each system is different. According to the sometimes infamous or much beloved Michael at FS-GS.com, it's really a matter of taking YOUR particular system, and "unifying" it so that all timing-dependent settings are maximally coordinated for maximum compatibility and smoothness, and again, all unnecessary services are PREVENTED FROM LOADING in the first place. This is very differernt from using FSAutostart to stop what may be running. A very dangerous downside of using hardware profiles is that it is possible to have a power out, and corrupt the boot sector and have the thing not boot to Windows as a consequence of having more than one profile. Not explaining this very well, but it is an issue. I did try the service from FS-GS.com because truly I was hugely skeptical but couldn't ignore the positive testimonials. I have to say, FS9 ran better than ever after this consult. I've tried to maintain it myself, but much has changed since my use of their service, and I have to say my system is adequate, but it is not as liquid smooth as it was after the service. One reason may be that I use only one hardware profile and use FSAutostart. Dunno!Users of his service claim they may not get much improvement in FPS per se, but the improvements in SMOOTHNESS and even IQ were worth the price of admission.Anyway, good luck. I have heard ATI 1950 Pro users have had more issues with stuttering. I'm not sure that's the case as mine is the same as my old 6800GT.

I just decided to set up another Hardware Profile. This is actually a trick as this Windows feature was implemented to allow people to run different hardware in the different profiles. But by using the services.msc control you can select your other hardware profile and disable whatever services you know you can safely disable from the get go, so that they don't load whatsoever. This is the cleanest way to boot up. As you have probably heard, you must not disable certain services lest you render your system unbootable. FSAutostart gives you recommendations on all the normal services that might load in a typical windows environment, the difference again is with the hardware profile approach these services simply don't load into memory, so there is no need to STOP them in FSAutostart.I have to say, the very taxing flight I just took from SMF to RNO in a PMDG 737 was surprisely smooth. Lotsa clouds and so forth but it looked quite nice. I think I'll continue to use this . . . until the next disaster hits. There are some no no's you must observe to avoid corrupted boot ups using more than one profile, but it's been so long since I tried this . . I forgot what they are!!Cheers,Noel

i think you have your FPS to high, i'd try to lower them to 24. william

Hi Noel, can you point to some instructions on doing this? If you remember how, can you provide a step by step doc on it.Thanks,Bill

Bill, I don't know if we will ever have 100% microstutter-free turns. The lean boot idea is pretty easy to do though so it's worth a try. Follow these steps:1. Go to System Properties > Hardware Tab > Hardware Profiles, where you will see the list of Available Hardware Profiles. The virgin set up shows just "Profile 1 (Current)".2. Click the Copy button, so you will now have a clone of Profile 1:http://forums.avsim.net/user_files/184060.jpgThe default boot option is preselected with the radio button at the bottom as you can see, and when Windows boots give you 30 seconds to choose a Profile, else it will choose the first profile listed. Click OK, and close out the Hardware Profiles dialogue.3. Using the Run command, enter services.msc, and you will see this screen which shows the list of all possible Services running currently (their Status) and their mode of starting (Startup Type):http://forums.avsim.net/user_files/184069.jpgDouble click a service listed, and you will get this dialogue:http://forums.avsim.net/user_files/184070.jpgClick the Log On tab, and you are presented with the opportunity to Enable or Disable that service for each of your two Hardware Profiles:http://forums.avsim.net/user_files/184071.jpgFrom here, it's a tedious case of bringing up each Service, and deciding which Services to Disable for your second, lean profile to boot to. Follow the suggestions in FSAutostart, which gives you safe advice on all the Windows Services. You will see other Services associated with your installed programs, including anti-virus and anti-spyware programs, your video applets, etc. YOU MUST be careful to follow which Windows services NOT to disable else you could leave your machine unbootable. You can rename your new Profile something like "Lean Boot" or something so when you boot up you can choose this one for FS.x, and your current Profile 1 for regular desktop operation.Alternative to FSAutostart, you can use this guide for what to do with XP services: http://www.blackviper.com/WinXP/servicecfg.htmYou may still want to run FSAutostart after booting to your Lean profile, since you can take advantage of the memory defragging capability.The real value of this maneuver is that you can disable services from running that are not stoppable using FSAutostart, such as certain AV and AS programs, etc.Again, there are some risks in this beyond just not Disabling certain critical services (Remote Procedure Call, for example). I'm not sure how that happens, but perhaps it had to do with using msconfig.exe combined with Hardware Profiles, or something, than can cause troubles. The worst case for me has been having to use the Emergency Repair Disk or Recovery Console to fix damaged system files. As I say, I can't remember what I did to cause this, but it can happen.Enjoy!Noel

Thanks NoelBill

I do not think that FS9 is capable of microstutter free turns with the scenery options turned up. I can fly at 30 fps solid (locked) and still get small "hesitations" when turning.On the same system, FSX (locked at 25) is actually smoother in turns.