I have spent a good 2 days trying Steve's fix. It does not work for me - I get nothing but problems with it.

 

1) I have run the registry files from avsim library

2) Remove the shader 10 folder

3) Enabled FXAA from nvidia inspector

4) Made sure the fiber setting is set to 0.1 in fsx.cfg

5) I use the widely accepted FSX.cfg tweaks with affinity masks, and so on. I have every single option updated/added/removed from my config file.

6) In nvidia inspector I have AA set to 32x, AA Transparency set to 8x Sparse Grid, AF set to 16x, and vsync set to 1/2.

 

Problems:

 

1) I get weird artifacts all over the place. They are quite colorful and originate from ground/air/autogen objects/etc

2) My FPS is absolutely HORRIBLE, it's at least 30-40% below DX9 values.

 

Computer:

 

3930k 4.75 Ghz

16 GB 2333 Mhz RAM (4 x 4 GB) 9-11-11-31-2

ASUS RIVE

GTX 680 4GB

Samsung 840 Pro 512 GB

Windows 8 64 bit Pro

 

I right now get around 10-12 FPS in virtual cockpit in la guardia with all sliders at max including airport and road traffic, boats, etc except the water is at 1 notch below max. When I'm airborne, flying above manhattan at 3000 ft, I get around 18-20 fps. With DX10, in addition to the problems noted above, I get almost half of these frames with the bloom enabled.

Set your Nvidia Inspector settings as per the how to doc. My 6 year old rig is running rings around your much superior rig and this can only be down to your settings.

Yes you can lose the FSAA setting (set to disabled) - I get 30 solid with the rest of your settings. If running REX use the DX10 optimized texture values and make sure to use a wave setting of DXT1 (not 32bit). Cheers jja

Turn down your AA, and turn your sliders down. All traffic at max and airport vehicles at max is a killer. It would appear to me that you have not followed any guides on how to properly tune FSX. Widely accepted also does not mean works for all.

 

I would recommend you start by carefully reading Word Not Allowed's guide.

 

http://forum.avsim.n...-guide-for-fsx/

 

Regards,

 

Bob

^{Bob - DX10 mode does not abide by most of the traditional DX9 advice. It really is a different bird. That said I still get excellent performance with most of my DX9 settings with the DX10 patches applied. Cheers jja}

Can you guys define "excellent"? I get constant 30 fps as well flying in friday harbor or at 30,000 ft. Problem is airports like la guardia or flying 2000 ft over downtown manhattan with REX and heavy weather in PMDG 737 NGX virtual cockpit. A lot of these "30 fps" claims I see here is with flying default C172 aircraft which does not even come close to PMDG.

Post your fsx.cfg as fsx.txt, fill out your system specs in the profile settings so we can see what we can do - OK? :smile:

 

pj

I am attaching my fsx.cfg file as a text file. I have also updated my profile with my computer specs. Please let me know if there is anything else I can do. I am hoping I can resolve this issue:)

 

Another thing that might be working against me is the fact that I'm using a 2560 x 1600 resolution which is a lot (GPU-Z is reporting 1950MB video memory being in use on average during flight). I also use FSX in windowed mode because I have another monitor which I use for flight plans and charts and with full screen, its not possible to utilize the second monitor (I don't see any FPS increase/decrease using windowed mode vs full screen mode though).

The only things that Steve's FSX 10 fixes don't address are the ugly preview in the startup screen and wave action. Other than that it has been a great experience. Cheers jja

Thanks, Mehmet. You have a pretty decent machine, and it should run both flavours of FSX perfectly well.

 

That being said, I've downloaded, saved and begun looking at your cfg - thank you for posting it in this fashion!

 

It's an hour past my bedtime here, but at first glance I can promise you that setting rour FreewayDensity to 100, along with Ships, Ferries and Liesure boats is guaranteed to give you the most incredibly "fireworks display" of artifacts, flashing, black skies, spikes and other nasty-looking things. But more tomorrow!

 

All the Best,

 

pj

Here's the file, Mehmet: You will need to play with the BufferPools to find the "sweet spot". I would recommend you spend a good number of hours flying a single exactly the same, one "heavy" flight, in, perhaps a 1/2-mile circle at low altitude in and around some dense scenery, Newy York, London, Seattle, etc., slowly changing one setting at a time, until you can fly it without any frame drop. THEN you will have your "sweet spot". This might take several days to get it right - but there is a sweet spot, and you will find it if you take the time to do this. Exercise moderation in all of your settings, clean up the pc's processes before starting FSX. Once you've got it right - save the cfg somewhere safe, so that you can go back to it later. Incidentally - the default Cessna 172 is fine to do this work - you don't need a 737.

 

 

 

Read it first, as there are a number of comments - OK? Get back here if you have any problems.

 

Here are the tested Inspector settings.

 

All the Best, :smile:

 

pj

Paul,

 

I really appreciate this, thank you for your time. I'm going to give this a try and report back here with questions I might have. See you soon!

 

EDIT: I actually have my first question, I never understood this bufferpools setting. Who needs to set it to 0 and who needs to set it to a number? I have 4 GB of VRAM on my video card, should I be setting this to 0? My regular RAM is also quite fast at 2333 Mhz and 9-11-11-31 timings, so should I prefer that over VRAM? I'm confused:(

Your GPU (yes - I'm jealous!) has 4 GB of physical ram. Your mainboard also has 16 GB of physical ram.

The operating system also has the ability to combine the mainboard's physical ram with a "special" file on one (or more) of the hard drives in the pc. This special file is called a Page File, and it will be seen by the OS as another chunk of memory. The sum of those two entities is called "VRAM" - for Virtual RAM, and any time that the normal system's RAM becomes short of space, it begins to move the least-used data in memory into "pages", and then sends them to the hard drive - into the Page File. It will sit there until recalled.

This has nothing to do with BufferPools. Those referred to in the fsx.cfg are directions, (DX9 & DX10) telling the gpu how it will accept and store all graphics data as it comes from the main processor. For an explanation of the subject, go to Steve's site and get a much better insight (than I can put here) as to what BufferPools are, and how they work in the flightsim.

 

Your ram timings are fine!

 

All the Best,

 

pj

DerStig: Since I am having a very similar PC, I am interested in results as well. And I know there are more simmers with 6-core 3930k as waiting weather to digg-in into DX10 or stay on 9 and enjoy.

Hi just tried using dx10 for the first time to see what its like so far it good but i noticed that all my a1 aircraft are all white in color with no markings at all, wonder if anyone else has seen this before