...The frames, that is...

 

So I've done a vanilla OS, overclock, and fsx install with DX10. Tweaked and tuned as per the latest hardware/software guide, and other articles by PJ. It runs like a dream, without a stutter in the world. That is until today, while doing some test flights in default Seattle..

 

Flying various default aircraft, I would circle the downtown area several times, with frames locked and holding at 30, then head away from the city, turn around and repeat.

 

On the second or third time doing this, my frames began to plunge. First to about 25-27, and then with each pass and circle, down even further, sometimes jumping down to 12-18. I can fly away from the city, and eventually my frames go back to 30. But as soon as I turn around, and get to a certain point, they plunge yet again, and the stutters get worse.

 

Even stranger, if I quit the flight, and load it back up right away, if I get anywhere near downtown, the FPS drop way down. Only if I restart FSX, and load a new flight will I be able to fly around downtown once or twice before it starts stuttering again..

I guess I'd like to know why FSX doesn't simply stutter from the get-go on my first two passes or so..

 

I started with BP=0, then tried several combinations of BP=1 and different RTs. Same result.

 

 

As far as I know, my machine, under DX10, should more or less eat up DEFAULT scenery in DEFAULT aircraft. 4.7OC, GTX680 Superclock 2GB, 1600mhz ram OC 8-8-8-24..

 

 

I should also note, that I didnt have UIAutomation fix in properly (forgot to change the name)...and a suffered a few BSODs because of it. I can't recall having these stutters before those BSODs...Not sure if that has anything to do with it, but either way I'm probably going to do another vanilla OS and fsx.. super excited to do it again.

 

 

If anyone has any insight on this, please share... I would like to finally get this right.

 

 

Thanks.

......As far as I know, my machine, under DX10, should more or less eat up DEFAULT scenery in DEFAULT aircraft. 4.7OC, GTX680 Superclock 2GB, 1600mhz ram OC 8-8-8-24......

 

You're absolutly right that FSX should run well with your rig. I guess you tweaked something in the wrong direction.

 

Rename the fsx.cfg and start FSX so a new fsx.cfg will created. There are many advices how to tweak. Did you read "How-to.."? Start tweaking again but step by step and do your test flights in between.

Spirit

I created a fresh CFG, no change. I even reinstalled FSX. The frames are great, locked at a solid 30.0/30.1, and there is no stuttering. 

 

Until I fly into a downtown area, and circle around skyscrapers a few times, then they plummet.

 

To be fair, I plan on flying commercial, so I won't be doing that obviously, but I also don't want this to mean underlying problems with other sceneries/addons later down the road.

 

As for the tweaks, I followed the AVSIM HW/SW Guide, as well as the DX10 how-to, exactly. I applied the tweaks one by one, and did testing around Seattle. Flying low and fast over the suburbs yielded great results, a smooth and stutter-free experience. Just not over downtown.

 

If you get a chance, try this experiment out, see what kind of results you get. Just fly into downtown Seattle, at a high rate of speed, and just circle downtown about 3 times. Then fly out in any direction, turn around, and fly back over downtown. See if your frames drop.

Sounds like a memory leak. Better check your ram's fluid level if its too low add a quart of mustard perferbly spicy. But seriously it does sound like a memory leak

welp, I'm not an expert on RAM, haha.. So what is memory leak? and how does one solve it?

As far as I know, my machine, under DX10, should more or less eat up DEFAULT scenery in DEFAULT aircraft. 4.7OC, GTX680 Superclock 2GB, 1600mhz ram OC 8-8-8-24..

 

I've got bad news for you, Daniel:  The Seattle area will pull all rigs down, some more than others, dependent upon lots of different parameters. Your rig is not so great that "it should manage it easily". 

 

If you need this solved we will need you to publish your full system specs in your profile - including the overclock, attach a copy of your fsx.cfg - renamed as "Daniel_fsx.txt" using the "More Reply Options" (bottom-right corner) and along with a screenshot of your Inspector settings. Then we can give you some educated opinions and suggestions as to how to make FSX more robust - ok!   :wink: 

 

Thanks,

 

pj.  

 

Edit: see Daz's post below.

Ah...just the man I wanted to talk to.

 

Yeah I figured Seattle was brutal on even high-end rigs, It's just curious to me that the frames were great until I flew a third or fourth circle around downtown. I tried the same test in my hometown of Denver, and it's the same story. Other than that, DX10 is the bee's knees for sure.

 

that would be great if you could take a crack at it, I'd much appreciate it. 

 

 

 

Oh, and with inspector, I can't seem to get the aircraft shadows AA working. In the "SLI Compatibility Bits" section, the value that you have in your settings isn't present in my inspector. But I'm not incredibly worried about it right now.

 

 

 

Thanks Paul!

 

 

 

4.7-gig with a 680 is a good balance, and I think that UsePools=0 is "probably" correct - but you may want to try UsePools=1 with a RejectThreshold of 262144 (or slightly bigger).

I found that the 580 with a 4.9 and 5.0-gig proc was somewhat overwhelmed, and the 680 isn't a huge jump from the 580. It's worth a try. Here's some more info on setting the BP, and here is a list of known frame killers.

 

You have a very good fsx.cfg, and so there are no changes. Your procspeed number (19864) reflects that you have a good, fast system.

My only changes to the fsx.cfg would be to drop the FFTF to 0.1 (mine is 0.07) and Cloud Coverage Density to 7 from 8. That's it.

In Inspector I would suggest removing the "Texture Filtering - Anisotropic sample optimization".

 

For a quick hint - you can get all of the Inspector settings on one page, Danie; - count to the tenth icon along the top, and you will see a filter "funnel" thingy. Click on it, and the screen jumps to the settings which you can/have change.

 

The second hint, (if I can call it that) - is - what proc do you have? A 2600K can hit 5.0 gig with good cooling, and a 2700k slightly higher, with the 4xxxk-series hitting 4.5 & 6 and giving the same benefit as the higher clocked 2xxxk-series. You need to put this into your profile settings, so that it appears under your pic at the left side of the screen. OK!

 

I hope this all helps,

 

All the Best,

 

pj

I have a I7, 3770k, which I've read that they max out 4.7 or 4.8. I might try and push my luck haha.

 

I've been testing some more, and I really am happy with the results, I'll just refrain from flying circles around skyscrapers...Since I'll be doing mainly commercial flights. But I'll apply those changes, see if it bumps it up a notch.

 

Thanks for all your help Paul!