bobterri

I followed Jordan King's removal suggestions via: https://steamcommunity.com/app/314160/discussions/0/537405286656508298/

Ieydis, Here's the thing! I understand I need to update to a newer monitor and will within a month or so. Finances do not allow me to do so at the moment. BUT, FSX-SE ran perfectly fine on Windows 7 on my old computer before it died. I don't think the monitor is the issue. kirk_johnson, No, I did not change anything in Nvidia Control Panel. All, I nuked FSX-SE last night...removed it and everything associated with it (planes, sceneries, etc.). Now I am deliberating between re-installing FSX-SE and going through the headache of setting everything up again with no assurance it will improve or making the leap to P3D v3. I was going to go through the process that SteveW suggested but with my RW commitments I just don't have the time, and with no guarantees I'd ever find what was wrong...well...it just wasn't worth it. If I don't report back it's because I have chosen P3D. If I reinstall FSX-SE I will report back to let you know the outcome. Lastly, thank you, thank you to all who tried to help.

Ok. Thanks. I'll shut up now and get to work.

This is all so new to me. I have never had a problem like this ("persistent" as you put it.). I have been simming, first with FSX boxed and now with FSX-SE and I guess I've been fortunate. I've had problems, but nothing like this. Buying this new computer, I thought I was going to be in Sim heaven, instead I've been in Sim hell. So, I'm struggling a little bit with terminology. It's not your fault, it's just that I've never had to get a baseline, etc. So, if you could just bare with me, when you say "stock settings," what exactly are you talking about? All sliders to the left? I just need a little defining of your terms. Again, I want to say "thank you" for your help. It is greatly appreciated. Steve, I'm sorry! You're probably referring to your post #52. Right?

What I mean is, about two weeks ago I ran the the "verify cache" option in the Steam menu, but, at that time, I did not rename exe.xml and/or dml.xml. So, are you saying that I should forget verifying the cache again, but rename dll.xml and exe.xml and then taxi at a stock airport with a stock plane?

Also, I forgot, but I have a rather bizarre problem with installing scenery. Maybe it has something to do with the stuttering, who knows? All payware scenery installs and looks good. But, if I add freeware scenery by adding it to C:\Steam\steamapps\common\FSX\Addon Scenery\scenery, it will not show up in FSX. If I install one of Ray Smith's sceneries that require an .obj file to be added to /Scenery/Global/Scenery, that files shows up in FSX but not the ones added to the \Addon Scenery/scenery location. I don't bring this up to ask how to fix it (I started a separate thread about it), but simply to ask if this has anything to do with the stuttering? I'm beginning to grasp at straws. I wonder, at this point, whether I should remove FSX-SE and everything associated with it and reinstall everything? (sigh!)

SteveW, The stutters occur primarily when turning, but not exclusively. I have run the "verify cache" option in the Steam menu, but I did not rename exe.xml and/or dml.xml. The monitor is the same one I used with the old computer, which, again, worked wonderfully with no stutters. Through all of this, I have tried the Target Frame Rates of 20, 21, 29, 30, and 31, all by using the slider inside FSX, besides the higher ones of 40 and 41. My current setting is 29 and it does seem to help. I could bring home my office monitor and try that. Fppilot, I swapped out the new GTX 970 with the old GTX 460 last night and it didn't help at all. Same stutters. Also, I made sure the SSD was AHCI enabled and TRIM was on. They are. Bjoern, Are you talking about: [GRAPHICS] ForceFullScreenVSync=1

I still have the video card, a GTX 460. I said it was a GTX 470 earlier. Might be worth a try. I also thought of installing the free version of X-plane to see if it too would stutter.

I bought this new computer from Cyberpowerpc and it was delivered in January this year. The specs are: Asus-Z97-E MOB; i7 4790k 4.6Ghz; 8gb DDR3 1866; Zotac GTX970, Corsair H110i GT liquid cooling, EVGA 750w Supernova power supply. It was overclocked by Cyberpowerpc.

Stop and start for a split second. Jerky. Especially when turning during taxiing. I'm beginning to REALLY hate Windows 10.

The following entry in .cfg did not change anything. Still stuttering. With HT enabled, set in the .cfg: [JOBSCHEDULER] AffinityMask=116

You lost me here! You mean vsync in NI works even though you're in Windows mode in FSX in Windows 10? I'm confused.

Switching back to Windows 7 is tempting, but with Dovetail announcing something new for Windows 10 I will probably just stick it out. I ran almost the identical set up on my old computer with Windows 7 including running FSX-SE in windows mode. and things ran very well for years. No stutters and minimal screen tears. Incidentally, I am not getting any screen tearing now, just stutters. I might try the AVIRA option for antivirus, even though I ran Windows Defender (or Security Essentials, whatever it was called) on Windows 7 and it never caused a problem. Tonight I will try: With HT enabled, set in the .cfg: [JOBSCHEDULER] AffinityMask=116 Oh, and by the way, I checked in Task manager while flying last night and my CPU was cranking at 28 - 34% throughout the flight. If I understand those numbers correctly, I would interpret the stuttering is NOT because of a performance issue. One more thing. I did try flying a test flight in full-screen mode and it still stuttered.

OK. Thanks, Steve. I'll try this tomorrow.

I have used the settings of 20, 30, 40 and 42 with the 1/2 vsync in NI. The stutters remain the same. No better, no worse. The only improvement I had was when I used the 4xS antialiasing setting in NI. One other thing, I cannot fly in full screen mode because I fly on Vatsim and need to keep Vpilot in view. I use a VGA adapter to connect to the DVI-I port on my graphic card. On my old computer I used 1/2 refresh rate in NI and set my frame rates at 42 in FSX. All was good. I've tried two Nvidia drivers. No change. I'll try this next, but it will be tomorrow before I can try it. Also, I tried: [bufferpools] UsePools=1 Poolsize=2000 And [bufferpools] UsePools=1 Poolsize=1500 Neither helped. And by the way, thanks for all your help folks. It means a lot. I'm extremely frustrated and your support is much appreciated.

I have set the AA settings down in NV Inspector to 4xS for Antialiasing and 2x Supersampling in the Antialiasiing Transparency Supersampling setting.

I've already done that.

I'm desperate! I'll try removing Windows Defender and install AVIRA. Nothing to lose! Funny thing is, I used Windows Defender on my old computer (Windows 7) for years with no problems.

The frame limiter isn't on in NV inspector. I tried it with it on and it didn't make a difference.

Most of these tweaks that you all have suggested I have tried. Some I have not, so I'll get back to you about results. It will take a while with RW commitments. By the way, I have an ancient 19 inch CRT monitor that has a refresh rate of 85mhz. Also, my CPU is also overclocked to 4.6 GHZ and is Corsair Hydro Series H110i GT water cooled.

Oops! That's a gtx 970 not a 470 in the new computer.

Just got a new computer. I7-4790K, GTX 970, 8 gigs ram, SSD hard drive. I've been on an I7 950, GTX 470 computer until the mobo fried. FSX-SE ran smooth as can be on the old box with Aerosoft Airbus, IFly 737, with lots of add-on sceneries. Installed FSX-SE on the new computer, installed Aerosoft Airbus, IFly 737, etc., and I get very noticeable stutters. I've tried every setting I came across on Google including Word Not Allowed's, NickN's, some from FSX-SE forums and others. Nothing seems to help. I am at my wits end. I've started with a new FSX.cfg 4 times, installed Nvidia Inspector and tried several different settings. Same old thing. I've turned down sliders in FSX...nothing. Any suggestions?

I do have FSDreamTeam's KLAX and KDFW installed, but at KDTW it's just Ray Smith's. And by the way, you're right, it was the jetways not gates. The tarmac from the default scenery was also bleeding through. I agree I'm just putting a bandaid on a problem. I just don't know what else to do. Somehow, apparently, FSX is recognizing the KDTW_OBJ.BGL file in /scenery/global/scenery but not KDTW_RS.BGL and KDTW_CVX.bgl in /Addon Scenery/scenery. I still suspect it's because FSX-SE is installed on Windows 10. I never had this problem before when FSX was installed on Windows XP and Windows 7. Oh, and it was doing it before I had any payware scenery installed.

Doggone it, I wish I had taken a picture! Let me describe an example. I installed Ray Smith's KDTW scenery just as he said to. KDTW_RS.BGL and KDTW_CVX.bgl in /Addon Scenery/scenery. KDTW_OBJ.BGL file in the /scenery/global/scenery. What I had after doing so, after loading up KDTW in FSX-SE parked at D8 at the new D-terminal was the new terminal from Ray Smith's Scenery but the gates and tarmac bleeding through from the default scenery. The old terminal was gone, but as I said, the gates were still there.

I'd like to post some pictures, but as I stated above I've found a way to deal with it. So far the method I related in my second post is working and I am getting zero bleed through. It's certainly not the way the authors of these sceneries intended but it's working.