I am running FSX in DX10 preview, the reasons for which I won't go into. There are graphics problems with VFR London, and so I started searching the web for a possible solution. I came across this review here at Avsim...

 

http://www.avsim.com...oft/LondonX.htm

 

 

...and scrolling to the bottom of it, found this...( my emphasis )

 

 

When you install the 1.20 patch it recommends that you do not use the DirectX 10 Preview, but if you want to, you can use the included program to change the textures for the DirectX 10 Preview.

 

My boxed copy of London VFR came as v1.2 and I have since installed patch v1.3. However, I am unable to find any program that alters the textures to suit DX10. Has anyone tried the 'included program' mentioned above or can anyone even verify there is such a program ?

 

Here is a screenshot, with the graphics problems arrowed. The trees shimmer too, though that is not apparent in the picture.

 

 

Thanks for any help :)

There's a potential fix for DX10 preview located in this forum - http://forum.avsim.net/topic/376140-dx10-flashing-runways-experimental-shader/. Also make sure in your display driver that you have Texture filtering - Negative LOD Bias Clamped. The default is Allow.

 

Best regards,

Jim

Jim, thanks very much for taking the time to reply. I've already read the thread you kindly linked to, and I've applied the runway flickering fix with success. Unfortunately it has no effect on the Millennium Dome, or the flickering trees.

 

I am using Nvidia Inspector, and have made sure that Texture filtering - Negative LOD Bias Clamped is selected, but I have read somewhere that DX-10 preview over-rides Nvidia Inspector, or at the very least renders it inoperative. Is that true, do you know ?

 

I think I'll put a post on that thread and see if Steve knows of a fix. From his blog, I believe he owns a copy of VFR London.

 

Thanks again !

It overrides the Nvidia Inspector's normal AA, but not the Inspector's FXAA - BUT, personally the FXAA appeared to blur the textures somewhat, lowering the IQ, so I turned it off and now just use the internal AA.

I think I'll put a post on that thread and see if Steve knows of a fix. From his blog, I believe he owns a copy of VFR London.

 

That's a great idea. Steve is very responsive and he worked with me to get my DX10 working (I've since turned it off though). I have VFR London too but never reinstalled it to my current system. It was a FPS killer for me. I can see why you are trying to get more frames by using the DX10 preview. Good luck!

 

Also, not an expert with Nvidia Inspector so Paul's recommendations look good to me! As you can see, FSX is a tweaking machine....

 

Best regards,

Jim

It overrides the Nvidia Inspector's normal AA, but not the Inspector's FXAA - BUT, personally the FXAA appeared to blur the textures somewhat, lowering the IQ, so I turned it off and now just use the internal AA.

 

Ah, thanks very much Paul. Thats another FSX configuration mystery cleared up - only another 2000 to go !

 

Jim, yes it is a tweaking machine. However, I seem to spend all my FSX time tweaking or searching for solutions to problems, and very little actually flying. I have now discovered that some of VFR London's buildings down near the river seem to be floating just above the ground ( in DX9 too! ). No idea why.

Paul sorry I havent got that package. Presumably the problem lies in a texture - is it possible to uninstall it and start again

 

So install and apply the patches in sequence using this "program" if it existed in the original or early patches to correct the problem before applying 1.3? Just a guess and clearly of no use if you no longer have the install say.

Paul sorry I havent got that package. Presumably the problem lies in a texture - is it possible to uninstall it and start again

 

So install and apply the patches in sequence using this "program" if it existed in the original or early patches to correct the problem before applying 1.3? Just a guess and clearly of no use if you no longer have the install say.

 

Steve thanks for your response, and yes I think I'll delete and reinstall. The 'program' might appear when installation takes place - it certainly can't be found on the CD as a separate item.

 

Thanks again for taking the time, and keep up the good work !

 

I think aerosoft have a forum you could try asking there?

Paul, I found the following over in the Aerosoft forums regarding DX10 preview - http://forum.aerosoft.com/index.php?/topic/53242-mega-airport-cdg-and-fra-under-dx10/. None of their scenery is DX10 preview compatible. Have you tried changing resolutions?

 

Best regards,

Jim

I think aerosoft have a forum you could try asking there?

 

Yep Steve, already asked there, but since my last post here, I've reinstalled London VFR and found that elusive little program I mentioned - it was in the London City airport scenery folder that accompanies the main city scenery. In the end, it only affects the airport, and so made no difference to the flickering trees or Millennium Dome at all. The only problem I have now is buildings that seem to float a few feet in the air !

 

 

Paul, I found the following over in the Aerosoft forums regarding DX10 preview - http://forum.aerosof...fra-under-dx10/. None of their scenery is DX10 preview compatible. Have you tried changing resolutions?

 

Best regards,

Jim

 

Jim, I think VFR London scenery is largely compatible with DX10, its just the flickering round the base of the Millenium Dome and the shimmering trees that are problems. The rest works fine. No I haven't changed resolutions yet, but thats certainly another avenue to explore. Thanks again !

Paul - did you change this (below) in the Shaders folder yet?

 

If not - edit the file "Terrain.fxh" in the fsx folder: \{Your_FSX_root_folder}\ShadersHLSL\Terrain\

 

Change this from:

 

sampler BaseSampler = sampler_state

{

Texture = (BaseTexture);

AddressU = Clamp;

AddressV = Clamp;

MinFilter = D3DTEXF_ANISOTROPIC;

MagFilter = D3DTEXF_ANISOTROPIC;

MipFilter = (State_MipFilter);

MipMapLodBias = -2;

};

 

to:

 

sampler BaseSampler = sampler_state

{

Texture = (BaseTexture);

AddressU = Clamp;

AddressV = Clamp;

MinFilter = D3DTEXF_ANISOTROPIC;

MagFilter = D3DTEXF_ANISOTROPIC;

MipFilter = (State_MipFilter);

MipMapLodBias = (State_MipMapLodBias);

}

 

Also you could alter the AA settings to SuperSample - try FXAA (in the latest Inspector series). This is a known (contributing) fix for shimmering textures.

Paul J

 

 

Here's what I have in that section of Terrain.fxh

 

sampler BaseSampler = sampler_state

{

Texture = (BaseTexture);

AddressU = Clamp;

AddressV = Clamp;

MinFilter = (State_MinFilter);

MagFilter = (State_MagFilter);

MipFilter = (State_MipFilter);

MipMapLodBias = (State_MipMapLodBias);

};

 

The bit you say I should alter is already as you recommend...the rest of it is a bit different however.

 

As for Nvidia Inspector, here are the settings I have and they are exactly as Nick Needham suggests in this thread;

 

http://www.simforums...topic36586.html

 

 

 

 

 

 

 

You say alter AA to Supersampling...which Supersampling setting ? There are a load of them in the dropdown menu.

 

And FXAA...do I simply toggle it ON, or is there more to do ?

 

Thanks for your help in all this. By the way, I've added my system specs to my signature - it might help

Quick bump. Paul J, any thoughts on the above post and the Nvidia Inspector settings shown ?

 

Thanks in advance.

Hey Paul! Transparency SuperSampling: - play with it, particularly SparseGrid SS. I've played with the FSAA, and have abandoned it, as it doesn't give the picture quality which the more 'manual' settings have.

 

Here's one setup that you might start with: Also - you might not be aware - the graphics driver and Inspector you're using are both replaced by newer versions - the 300 series - and this will give you a little better performance. Particularly note the settings at the bottom of the pic: this setting - Vertical Sync - being set to 1/2 Refresh Rate is used in cahoots with the Frame Settings in the FSX Display window, which you set to 30fps. This will completely get rid of any need for Vsync control set within the fsx.cfg, or the use of any other external frame limiting software, such as FPSLimiter02 for e.g.

Take a look at Ryan Maziarz's instructions over at the PMDG General forum > This is the most up-to-date - and readable - site to follow vis a vis Inspector setup.

 

Re the MipMapLodBias - I think the original author has it backwards: I hadn't used this in a couple of years or three, and had cut/pasted it from his post, but in checking my default FSX on my spare pc - the file is exactly as you said it was - it is already (State_MipMapLodBias); , so I think it should be set to -2; Duh!

 

Hope this clears a bit more mud!