Hi all

 

like paula, I got the link about Steve's DX10 and wanted to give it a try.

First of all, I would like to Thank PJ and Steve for this amazing experience!

 

The problem I am having is VSYNC(screen tearing) and AA. Paula suggested some changes to Inspector but same results.

 

System:

2600k @4.8, 8GB 1600 7-8-8-24-1, EVGA580SC, VelociRap HD, Win7 64

 

The thing with AA is that in FSX menu, whatever aircraft is selected, notice how the texture is:

 

 

Although in game, it looks normal but still notice and you know how it is when panning at times:

 

 

 

I downloaded V3.2.2 and the only file I ran is the setup.bat and thats it, didn't do anything else

 

Inspector settings like so;

 

 

 

FSX settings:

Graphics: All enabled, Anisotropic filtered, 1920x1080, Target at 30

Scenery: all to the right except for mesh res at 5 and water at low 2.x (no difference higher than that)

 

cfg file:

HIGHMEMFIX

TBM=120

LOD=6.5

FFTF=0.10

 

Although I am very happy with the results considering the DX10 option, with those 2 minor issue, it will be perfect for me! Any suggestion, comment is much appreciated!

 

 

With all the settings maxed within FSX and the UTX tool features enabled including the lights and what not, GEX, REX, OpusFSX, etc.. the results are :Whistle:

 

 

THANK YOU!!

Edited February 17, 201313 yr by firehawk44
One image removed. Exceeds 1600W and far exceeds 400KB weight limits. Yours was over 800KB.

Hi Mobsky - Welcome to the club!!

 

Put these two lines into the...

 

[Graphics]

 

MultiSamplesPerPixel=4 // Must have for good AA. Using 8 is a huge performance killer for a very small improvement

 

MultiSampleQuality=8 // This enables Nvidia 8x AA, but one can use 4x for better performance, or 16x AA if the system can handle it.

 

Vsync: - You have Inspector correctly configured - along with "30" frames set within the FSX settings.

A further improvement is to be found when "DisablePreload=1" is added to the [Main] section.

 

All the Best!

wow, nice video. Makes we want to try DX10...

 

A further improvement is to be found when "DisablePreload=1" is added to the [Main] section.

 

Hi mobsky, the missing piece for me was DisablePreload=1 which Paul suggested.

Hello mobsky. I watched the video. I'm new at this but I think what I was seeing as far as image degradation with the pixelated patches showing up at times was the CPU overloading the GPU? Just a guess please don't laugh if I'm way off with this. (Anyone's feedback appreciated on this)

 

The other thing I see is the size & brightness of the vehicle/street lights below. I think they are too big & bright. I don't run any payware night lighting but the look of yours reminds me of the airport night-lighting problem that I did experience after first changing over to DX10. A replacement halo.bmp file & adding/adjusting the scalar settings in the .cfg file has pretty much fixed the night airfield lighting issue for me in DX10. I wonder if there might be a similar way to fix your night scenery lights. Point may become moot in the near future with a new release. At least I hope it does.

I have a nice configuration at the moment and it runs great even with gray and rainy.

I use instead of 8xs now 4x4 3d3 and 4xgrid etc.

lod at 4.5 and water 1x high

[bUFFERPOOLS]

UsePools=1

Poolsize=8388608

RejectThreshold=262144 according NN

TBM 80

main section

Disablepreload=1

Fiber_Frame_Time_Fraction=0.1

 

my question would be: does it make a difference when i put in

MultiSamplesPerPixel=4

MultiSampleQuality=8

in the cfg file too??

 

 

Good Morning, paula - this is covered in the pinned "How-To" doc on page 4.

sure i know that but the question was more why do i have to put this in the cfg file if in the nvidia inspector it is already set? by means of

antialiasing setting 4x4 and transparency 4x sparse grid?

 

Because AA doesn't work properly in DX10, and must be set in-game, and 4x SGSS is an enhancement to AA - it is not AA. See Steve's Blog here.

well i dont understand it it is tech i am a user only

so what should i do

 

Paul,

 

in game i already have AA clicked

in nvidia inspector i have set antialiasing setting 4x4(3d3) and transparency 4x sparse grid

and what do i have to set in the cfg file according to the ones above

 

MultiSamplesPerPixel= 4 or 8

MultiSampleQuality= 4 or 8

 

pls let me know then i can change it.

It should be like this

 

MultiSamplesPerPixel=4

MultiSampleQuality=8

Thank You all for your comments and suggestions!

 

Hi Mobsky - Welcome to the club!!

 

Put these two lines into the...

 

[Graphics]

 

MultiSamplesPerPixel=4 // Must have for good AA. Using 8 is a huge performance killer for a very small improvement

 

MultiSampleQuality=8 // This enables Nvidia 8x AA, but one can use 4x for better performance, or 16x AA if the system can handle it.

 

Vsync: - You have Inspector correctly configured - along with "30" frames set within the FSX settings.

A further improvement is to be found when "DisablePreload=1" is added to the [Main] section.

 

All the Best!

Hi mobsky, the missing piece for me was DisablePreload=1 which Paul suggested.

 

Yes it completely solved the VSYNC problem! It does work! Thank You!

 

For the MultiSamples Lines:

 

MultiSamplesPerPixel=4 ===> changing this to 8 didnt effect performance, but since its a small improvement i kept it at 4

MultiSampleQuality=8

 

Although there is an improvement but Paul, since you mentioned that AA doesn't work properly in DX10, I think the results are very good considering DX10, right? and you know in VC, there is absolutely no issues at all!

 

Like you said read "The How to" PDF a couple of times which i never did! :p0304:

 

Thank you Paul!

 

wow, nice video. Makes we want to try DX10...

 

Thanks! Yes you should give it a try!

 

Hello mobsky. I watched the video. I'm new at this but I think what I was seeing as far as image degradation with the pixelated patches showing up at times was the CPU overloading the GPU? Just a guess please don't laugh if I'm way off with this. (Anyone's feedback appreciated on this)

 

The other thing I see is the size & brightness of the vehicle/street lights below. I think they are too big & bright. I don't run any payware night lighting but the look of yours reminds me of the airport night-lighting problem that I did experience after first changing over to DX10. A replacement halo.bmp file & adding/adjusting the scalar settings in the .cfg file has pretty much fixed the night airfield lighting issue for me in DX10. I wonder if there might be a similar way to fix your night scenery lights. Point may become moot in the near future with a new release. At least I hope it does.

 

There is no problem with CPU/GPU at all

 

Temps for CPU are 62C 67C 65C 65C

for GPU= 60C MAX .... GPU Usage 31% .... Fan Speed ... 54%

 

one note: only while recording, FPS jumps up and down but still in the range of 24-30 with no issues and for example a 9 min recording is a 13GB file, so when i put a couple of clips together, which is either 13GB, 7Gb, etc ,, I end up with a 900Mb file which I can upload to youtube and by that it might reduce the visual quality a bit or whatever you are seeing, maybe i should use something other than winodws movie maker, but you get the idea of what I mean.

 

For the lights, UTX has 3 brightness options, 100%, 50%, 25%... I have it on 50%, I might try the 25% which I never did and see what I get, plus maybe that bloom effect gives it that brightness. There is a note about bloom setting that can be changed in the cfg which I read in the HOW-TO pdf file

 

Any tips/suggextions for lights is appreciated, but again this is my first time with DX10 so I will playing around with settings check out the other files for DX10 as well.

 

Here's a clip from an outside view:

http://youtu.be/26eppG_jxhs