Mode=2560x1600x32
AntiAlias=1
Anisotropic=1
MultiSampleQuality=4
MultiSamplesPerPixel=16

 

Thanks Rob. A few questions if you have the time.

What video card do you have.?

What version of NVIDIA or AMD driver are you using? 

Do you use SweetFX?

 

I note in NVinspector that you have enabled anti aliasing as such but because your settings are not set to NONE but rather to "allow programme to use" hand off control to the FSX Software limit of 4 x ... anything else is superfluous according to the Forum. I did indeed look at your Lockheed flight over London and it looks spectacular. But again I have this issue with DX10 that will not go away. anti aliasing is not fully applied and I get tearing because VSYNC command in the FSX.CFG appears to be ignored.

My Card is the latest GTX 770 2Gigabyte Overclocked video card and I am running the lastest WHQL Nvidia 320.49 Drivers.

 

Ray

 

 

What video card do you have.?

What version of NVIDIA or AMD driver are you using?

Do you use SweetFX?

 

Hey Ray ... video cards I'm running are a Titan 6GB OR GTX 680 4GB -- it's complicate, but I just have the GTX 680 4GB in now (having some issues with the Titan but it's nothing to do with FSX, another work related product).  The settings I listed are what I used for both Titan and the 680. 

 

For the 680 I'm using the 314.07 driver.

 

I don't use SweetFX but "I think" Paul does??

 

 

 

but because your settings are not set to NONE but rather to "allow programme to use"

 

As I understand it, there are two approaches to getting AA in FSX under DX10.

 

Unlimited Frames (what I'm using)

 

I think the key to AA is SGSS along with your native resolution(s).  You also have to create a NEW profile, do NOT use the existing "Microsoft Flight Simulator X" and make sure it's associate with FSX.EXE.  AND (very important) remove the FSX.EXE application association on the existing "Microsoft Flight Simulator X".  I don't have a problem with VSYNC other than sometimes during rapid panning in cockpit.

 

Locked Frames

 

If you want VSYNC DX10 then I think you'll have to do the other approach to FSX with locked frames and have nVInspector handle all the AA.  I tried this approach but didn't like the results, but to be fair I didn't experiment with it that much since I was happy with my Unlimited frames approach.

 

On a side note:  you can remove VSYNC issues and even make FSX look like it has higher frame rates via post editing (1/4 sec recording).  What I've posted on YouTube (in my link) is as close to "as is" with just basic edits for titles and organization ... no other special post production processing that you see in many other FSX videos.  Not that there is anything wrong with post production video work, I'm amazed at how others have made FSX look better than it really is.

Thanks Paul I will wait to see if KBOS is fixed with this new program before purchase

The mystery will be ansewered when we DX10 fans purchase Steve's fix and post which airports work to a new thread that could open for this reason. 

I would have been helpful if they allow me to beta test it like PMDG doing.

 

 

Does anyone know if the new DX10 Fixer will do anything to address the FSX water settings to HIgh 2.X  and correct the land shimmering?

 

Hi Paul/ All -

 

I never did hear a response about the DX10 water and if it will be usable on High .X with the new DX10 fixer. Either way, I already have my credit card ready to go to purchase as soon as it is released. 

 

Thanks!

Hi Paul/ All -

 

I never did hear a response about the DX10 water and if it will be usable on High .X with the new DX10 fixer. Either way, I already have my credit card ready to go to purchase as soon as it is released. 

 

Thanks!

 

Hi Dan; There's probably been no response because no-one sees either of these as a problem with DX10.

 

Shimmering is present in both DX9 and DX10, and can be a pain in either,Dan, but it's fixed by various combinations of Inspector settings, mainly controlled by SGSS, and I have never heard of 2x High water as being a problem. Here's my current Inspector, and here's the snip of the Settings --> Scenery, and below is taken straight from the cfg.

 

[TERRAIN]

LOD_RADIUS=6.500000

MESH_COMPLEXITY=100

MESH_RESOLUTION=23

TEXTURE_RESOLUTION=28

AUTOGEN_DENSITY=4

DETAIL_TEXTURE=1

WATER_EFFECTS=6

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376

SWAP_WAIT_TIMEOUT=3    

 

I just did a slew of pics around Orcas Island, and did notice some small amount of shimmering in the water under some islands, but it was very dependent upon height, angle and distance, and it's probably there because I'm only running 4xSGSS at this moment. I'll try again, later, with the higher setting.

Thank you Paul !

 

I will verify my setting with your post and retest the water.

 

I was going off the recommendation from the DX10 how to guide(aka DX10 bible). I never had the water shimmering issue in DX9 on High 2.X. It may be a bad description because it is actually the land reflection in the water that create the visual shimmering...

 

"Settings ->Customize-> Scenery->Mesh Resolution-> 2M:  Water Effects-> Low 2.x, Med 2.x or High 2.x :

 

 Low and Med look pretty good, and don’t cause any shimmering, whereas High 2.x causes land reflection shimmering on some pc’s…"

I do not post often as I use to, but I must say Paul J. you really impress me as one top notch guy. You keep the excitement going in a positive refreshing way. With regards to FSX. For that I Thank You!

 

+1!

"Settings ->Customize-> Scenery->Mesh Resolution-> 2M:  Water Effects-> Low 2.x, Med 2.x or High 2.x :

 

 Low and Med look pretty good, and don’t cause any shimmering, whereas High 2.x causes land reflection shimmering on some pc’s…"

It happens to me.

 

Also High2.x can be a FPS killer.

 

Just Yesterday, with the new FTX Global (DX9 or DX10)  at dusk and stormy weather I was getting 9-14 FPS over Paris, changed it to Mid 2.x and went back to 30 FPS solid.

Have some problems with undock panels to multi monitors. They appear black and fsx crash.

 

Is this a DX10 issue?

Yes, though others may give you some help here, as I run TH2Go, and then only in fullscreen mode. I found it was easier to just get another pc and link it for PlanG or other app.

Hi folks..

 

Just to ask here...  I have 2 additional monitors which i use to run my gauges from... i usually undock them (Black-box or AXE) and drag them to the monitors below...

 

(Just so you know, i have 2 x 27" monitors linked via a Zotac splitter so they act as one, then 2 x 18" monitors which are below these to use for the instruments)

 

Am i to understand that (i use windowed mode by the way) that this setup will NOT work in DX10? If so i will have to re-think heading down this exciting path!

 

Any advice?

 

Cheers

Yes, though others may give you some help here, as I run TH2Go, and then only in fullscreen mode. I found it was easier to just get another pc and link it for PlanG or other app.

Can or is rhis fixed by Steve scenery fixer?

Have some problems with undock panels to multi monitors. They appear black and fsx crash.

 

Is this a DX10 issue?

This will help Doug, too: You can run TH2Go in a faux-windowed mode connected to one port on the gpu, with your GPS, FMC (both undocked) - and also any other app, such as PlanG on the second - or third monitor attached to one or more of the other ports. The secret is the faux-windowed mode, which allows the window borders to disappear, giving the impression of fullscreen mode. Sorry - I don't have a link at this moment, but I will dig it up in a short while.

 

I would expect that Nvidia Surround will also have this facility, such that gauges, FMC's, etc., can be moved over.

 

(I just grabbed the monitor from my wonderful wife's pc to do this, so I know it works!)

 

ATB!