HI I decided to post it here as oppose to video card forum as i followed the how-to-dx10 from here.

I am wondering why nvidia insector setting seem to have no effect on Fsx in my set up?

Atleast it seems like they dont smetimes i wonder if i am running in dx10 :-) , but i have to be its checked in dx-preview and i had to install shaders as originally they would flicker, so it seems its all good.

ok to mention everything works good for me, but i cant help but feel i might bemissing on something here...

i do have AA can see clearly that it works exct in Welcome screen with indiana jones theme well almost :-) in this screen the aircraft does not have any AA very juggy but honestly i dont care, yet in game all is nice and smooth.

the vsync 1/2 refresh has no effect either set to unlimiter runs unlimited i even set it in default profile and it did nothing yet other software for example Minecraft was affected by it! frames were locked to 30 normally game runs in high 60+

for now i just treat it on bases IF IT AIN'T BROKE DON'T FIX IT :-)

yet on the other hand .... could it be better could it be pretier yet ... :-)

as another example earlier today following to a T info from other post about doing driver clean up i installed newest nvidia driver drivers check that fsx works them redone settings in nv-inspector fired up fsx again and could not tell there was any difference visual or performance like from before

any suggestions are welcome :-)

thanks for your help

Andy

 

info about doing

Yeah - most of the time the spinning aircraft will likely display big jaggies, yet the sim runs just fine!

 

NI Pics and an fsx.cfg, Andy!! On the fsx.cfg - see if you can rename it to fsx.txt and "attach" it here as a file, instead of copy/pasting... something's not quite right somewhere.... :Thinking:

Here are my Nvidia Inspector settings

 

 

Page 1 and 2 of Nvidia Inspector

www.creepercitycraft.com/JPEGs/pg1.png

www.creepercitycraft.com/JPEGs/pg2.png

 

And Here is my fsx.CFG

http://www.creeperci...PEGs/fsxCFG.txt

 

Thanks

Hi Andy! Thanks for posting;

The cfg looks fine, and nothing jumps out at me except that the Vsync = "1/2 Refresh Rate" / "Standard" settings and [Display] Texture_Bandwidth_Mult =120 are all ignored when you set your fps to unlimited within FSX. This normally leads to fsx jumping, or hesitations happening, followed by fairly high 60 - 80fps, and then plunging back down - sometimes into the teens, depending upon the scenery loaded. The vsync is noticeable only when one is banking into the turn and then throughout the turn - appearing as a couple of wavy lines or bands across the middle of the screen, perhaps not wider than 1/4 of an inch.

 

Your 670 card is a powerhouse, but personally - I would move the proc to 4.7-9 in order to get the best results from it. It's a matter of balance, and that card will take all the proc can give.

The NI settings - I only note that the "Multi-display/mixed gpu acceleration" is set to "Multi Display performance mode" instead of "Single display Performance Mode".

Just my 2 cents. I face issues when using the default "Multi Display performance mode" instead of "Single display Performance Mode".

The latter works really well on my GTX680 GFX card.

 

Cheers,

Marz

OK - that's fine - I've had it in both settings, and I don't think it made any difference either, but I do get jhesitations, for sure, when frame rate is set to unlimited...

 

But - like you say "If it ain't broke......"

 

:lol:

ok, thanks for your input

what i have biggest problem with that i guess i should have mentioned is screen tearing i think that is what that is anyhow i took your sugestions and changed to SingleDisplayPerformance

I also changed the vsync to A... shoot i forgot what is caled and instead of using 1/2 refresh rate i set it to aplication controled and it did help somewhat... for sure the screen tearing did not dissapear 100% but its much better mainly see it in spot view or low altitude flying fast also where the load demand on cpu is greater seems to show more this tearing.... i think that is what i see.... sometimes looks like big wave as if there was a nuclear explosion underground anyhow using 1/2 refesh did not help as much as setting aplication controled also i locked the frame to 60fps... locking to 30 or 60 no difference....

well i am starting to feel like this topic belongs more on video board then here... :-)

ok if you have anyideas pls let me know

and i will also crank up the cpu later as Paul sugested mine runs only at 45 deg max with fan bearly doing anythig so i sure can give it some more

Thanks

ADAPTIVE is the one i chose instead of STANDARD

and with tearing seems th higher Fps the less tearing effect... tearing does seem misterious to me i dont quite get it ... seems to vanish the higher fps i get...yet it is speed dependant too so i guess it has to do with refresh rate of monitor too.... idk i just leave it alone for now i dont use spot view to land anyways :-)

@ Paul - For Anisotropic filtering mode, he has Application Controlled. Shouldn't this be User-defined / Off as recommended by Word Not Allowed's guide? Anyway, that's my setting.

 

Best regards,

jim

Nope - Texture Filtering Section:-

Application Controlled, 16x, Off, Off, 0.000, Clamp, High Quality, Off... is correct, Jim, but I would not say it's right or wrong, just that App-Cont'd or Off was the original setting at the end of July, and all since have been recommended to use that. I know your config is non-standard against the original, so it must work for you, as do other configs for other folks.

 

She's a "work in prigress, Jim, and so not everything I post can be gospel, and many parts of my documentation have been altered as the testing progressed. The heaviest was done at Vancouver - ~September 5th, with three days of circuit after circuit, in order to get a handle on BP and TBM, and ended up with my BP being changed to use an RT instead of "0".

 

Generally one of the three NI's posted here will give the user the best setting, but there's also no harm in someone having their own ideas!

Thanks Paul. I'll try that too.

 

Best regards,

Jim