100% ad-free
Rotordude wrote:QUOTE (Rotordude @ Jan 13 2012,6:39 PM) <{POST_SNAPBACK}>Tried it, if FXAA worked in FS as it does with X3, COD, BF and other games I have it would be brilliant.
Yeah, perhaps even better if in conjunction with DX10 or DX11.--------------------------------------
Adamski wrote:QUOTE (Adamski @ Jan 13 2012,7:48 PM) <{POST_SNAPBACK}>Hmmm ... I've tried everything, but can't get this to work!
Do you run in it before/after/during FSX? I minimise, maximise, hit the pause key ... you name it ... and nothing :-(
Is the DLL the correct one for FSX?
If you just copy everything (In the "somegame" folder) to your FSX directory then once you load up a flight then, by pressing pause/break button, you should see a change. From memory I think you need to enable some features using FXAA_Tool.exe (just create a shortcut on your desktop). If you're having any other issues PM me. Worst case scenario Adam is if you want to use it and it is not working i could always show you what needs to be done seeing as we are only a suburb away from each other.--------------------------------------
Kelvinr wrote:QUOTE (Kelvinr @ Jan 14 2012,6:35 PM) <{POST_SNAPBACK}>If you just copy everything (In the "somegame" folder) to your FSX directory then once you load up a flight then, by pressing pause/break button, you should see a change. From memory I think you need to enable some features using FXAA_Tool.exe (just create a shortcut on your desktop). If you're having any other issues PM me. Worst case scenario Adam is if you want to use it and it is not working i could always show you what needs to be done seeing as we are only a suburb away from each other.
Thanks for that, Kelvin ... it seems there were a couple of steps I'd missed. Here's a part of my post in the (useful) ORBX thread here.
======================================================
What cured it for me was to:
1) Turn AA completely off in nVidia CP, nVidia Inspector (if you use it) *and also in FSX*.
2) Unmap your PAUSE key in FSX, leaving "P" as the default for pausing.
3) Run FXAA_Tool in the background.
4) Maximise/minimise the FSX window once to activate (or to refresh new FXAA settings).
I have a GTX580 and, for some reason, nVidia Inspector and/or the nVidia CP totally refuse to apply any changes to my system. I've tried everything.
When AA is enabled (in FSX and nVidia) it's not FSAA and seems to default to what looks like 2x. FXAA_Tool seems to be the only way I can force my system to do FSAA - and I don't use any of the other effects ... only the AA.
=======================================================
It seems that nVidia may have "dropped the ball" somewhat with FSAA for cards like the GTX580. BoBL has an almost identical setup and has exactly the same problems as me. Googling around finds many users having the same difficulty.
Many people may like all the HDR/Bloom/Sepia toning "feechers" but as far as I can see, that just degrades the image at source. I'd rather have the very best to start with, then add what I need afterwards, in Photoshop.Last edited by Adamski on Sun Jan 15, 2012 1:09 am, edited 1 time in total.


Rotordude wrote:QUOTE (Rotordude @ Jan 15 2012,5:23 AM) <{POST_SNAPBACK}>The sepia I do not like but the rest after fine tuning looks fantastic.
Adam ya dont need the FXAA tool running in the back ground, it's just a interface for setting up ya prefs.
Raw from FSX no AA.
RAW from FSX using FXAA anti aliasing (yes got it working) and fine tuning all except Sepia which is turned off.
Over all very happy with the outcome. Big bonus no fps hit when flying in heavy clouds. Love the bloom and the ground textures look a little more natural.
Great to hear Pete. I run FXAA with very minimal settings, just enough to give a bit of "flare" to the clouds and ground. I do however us the sharpening feature as you can get it to the point where it will sharpen aircraft edges to bring it more to the foreground and contrasts well with the land and clouds, makes for a more immersive experience IMHO.
Adam,
It's a pity you can't get it to how you want it. I have the GTX 570 card and have no real issues like the one's you are having. What I do recommend you doing though is to empty your shader cache and try that. This was a problem I experienced some time ago and this was one of the fixes. When you much around with the shader in FSX the cache can get screwed up a little, see link below for steps to do this, and don't worry you should have any problems as a result because it is only the shader cache not the texture folder or some other critical folder. If you use shade then you may need to run the program again to inject the shader changes. Hope it fixes your issue.
Cheers,
Kelvin--------------------------------------
Adamski wrote:QUOTE (Adamski @ Jan 17 2012,1:23 AM) <{POST_SNAPBACK}>Thanks for the correction/tip, RD ... I'm now getting the hang of this thing!
I'm getting to like FXAA more and more. Apart from the AA (which is certainly less of a framerate hit than using the nVidia CP settings), I like the fact that you can quickly toggle the effects on and off. I have a joystick button set up for this, but hitting the "Pause" key is pretty easy as well.
It's handy for setting up a temporary gamma "fix" which you can apply if your time of day or weather is washing things out too much (or over-saturating things at mid-day) - also for when you're zoomed into instrument view and want maximum legibility.
One question though ... is the FXAA dll quite happy working alongside the external FPS limiter one?
Related to that ... does anyone know if the in-built FPS limiter available via nVidia Inspector is any better than the external FPS limiter?
Hi Adam,
I used FPS limiter but found it did jump from the fixed setting I used. I now use nvidia inspector framerate limiter and found a slight difference in frame control where I believe it does control the frames alot more kepping it within a respectable limit to my selected number. The DLL should have no issues with the limiter. I have tried many combinations without too many problems. However, I have found when you have the right combination of settings in the FXAA_Tool it can cause dramatic FPS drop. This generally comes with the tone settings.--------------------------------------
Kelvinr wrote:QUOTE (Kelvinr @ Jan 17 2012,2:07 PM) <{POST_SNAPBACK}>I used FPS limiter but found it did jump from the fixed setting I used. I now use nvidia inspector framerate limiter and found a slight difference in frame control where I believe it does control the frames a lot more keeping it within a respectable limit to my selected number. The DLL should have no issues with the limiter. I have tried many combinations without too many problems. However, I have found when you have the right combination of settings in the FXAA_Tool it can cause dramatic FPS drop. This generally comes with the tone settings.
Thanks for that, Kelvin. I think I'll keep my FPS limiter at nVidia level then. Seems to work fine.
At the moment, all I'm running FXAA with is anti-aliasing, a tiny bit of post-sharpening and a tiny bit of gamma darkening (which helps to show that I have FXAA toggled on). I'm a happy camper!Last edited by Adamski on Tue Jan 17, 2012 1:36 pm, edited 1 time in total.
AndrewJamez wrote:QUOTE (AndrewJamez @ Jan 18 2012,9:50 AM) <{POST_SNAPBACK}>Has anyone had this working with DX10. Would be interested to know as i cannot seem to get nvidia inspector to run FSAA in DX10. Maybe this new app could help.
I'm not sure whether the version of FXAA I have supports DX10 (Kelvin???). There are DX10 versions around.
I had difficulty in persuading nVidia Inspector to apply FSAA settings in FSX - for either DX9 or DX10. 2x and sometimes 4x work work, but nearly all the other moes (up to 32x) just wouldn't get applied. I have Counterstrike Source running as a test bed for GFX settings and they [all] get applied in that OK, so it must be something to do with the way I have FSX set up.
Are you sure you want to run in DX10 mode though? I used to be a great fan of DX10 preview mode as it gave me much better water effects - and some cockpits looked better - but I got fed up with missing textures and other graphics glitches.
After having bought the PMDG 737, I read their comments on DX10. They said "forget it". Considering what an amazing job they did on the NGX, I'm inclined to take their advice!

AndrewJamez wrote:QUOTE (AndrewJamez @ Jan 18 2012,9:50 AM) <{POST_SNAPBACK}>Has anyone had this working with DX10. Would be interested to know as i cannot seem to get nvidia inspector to run FSAA in DX10. Maybe this new app could help.
Prepar3d I don't believe has native DX10 support at this stage but have integrated the shader3.0. I would not recommend using DX10 in FSX as it causes FPS hits. if not all the time, then intermittently. It is poorly coded in FSX.
Hope this clears things up for you.
Kelvin--------------------------------------
LawnDartLeo wrote:QUOTE (LawnDartLeo @ Jan 23 2013,3:42 AM) <{POST_SNAPBACK}>Greetings,
Is there a trick to getting FXAA tool to work in full screen mode? It works just fine in a window but as soon as I go full screen, all the effects are negated.
I guess a better question might be.... what happened to FXAA tool that it fell out of favor? I just discovered it and find it to be most effective at delivering desired visuals in FSX. What replaced it?
Here's a newer version of the FXAA tool. I have put it in my dropbox. What you need to do is make sure your anti aliasing is disabled inside FSX and set to full screen as this only works in full screen.
https://www.dropbox.com/s/yuh3lbxzqem9o ... SVN101.zip
What's good with this updated version is that you don't need to copy files to FSX/Prepar3d main folder just link it but searching the executable. Any problems just post back and I'll help where I can.
cheers,
Kelvin--------------------------------------
LawnDartLeo wrote:QUOTE (LawnDartLeo @ Jan 23 2013,8:34 PM) <{POST_SNAPBACK}>The issue is dual monitors.
Any ideas? I want my second screen!!! Sure I can just turn it on and off.... but really, that is a pain.
Worse yet, when I switch views via EZDock, the shader reloads EVERY TIME. I get a bright flash then all is well.
The more I mess with this, the more I wonder if it really is not worth the hassle.
Multiple screens is not really something I have used so never had that issue. My patience with FSX/Prepar3d has almost expired and I am waiting for an earth moving update that will spring me back to life again. There are still alot of bugs.--------------------------------------
Users browsing this forum: No registered users and 13 guests