DF-21 Forums

[GrandAdmiralThrawn]

I tried DarkXL Alpha 9.01 now, and found it strange that no FSAA seemed to work on my nVidia cards. Usually this is only the case with engines using either FP16 or FP32 HDR render targets (or mixed render targets including either FP16 or FP32 precision).

Platform:
WinXP Pro x64 Edition, SP2
DirectX 9.0c
2 x nVidia 285 GTX, NV Driver Version 195.62

nVidia Drivers feature so-called compatibility flags or bits which can tell the driver to perform some dirty tricks to get FSAA to work in such cases. This enabled me to run FSAA in several games like Fallout 3, Unreal Engine 3 games, EVE online, etc.

I did some experimentation, and found that the compatibility flag setting "0x80000000" works for DarkXL. With that flag set, both Multisampling FSAA and Supersampling Transparency AA seem to work perfectly.

To set that flag, you need the tool [nHancer], which only works for nVidia cards (8000 series and newer).

You can either set the flags manually, or import my nHancer Profile readily configured for DarkXL:

[nVidia/nHancer Driver Profile, DarkXL+FSAA] (This profile sets 8xQ FSAA + SS TAA as well as 16xAF, enables SLI and AA compatibility flags).

Please let me know if this helps you, or if you did not even encounter that FSAA bug, thanks!

_________________
[XIN.at Homeserver Project]

[lucius]

When Bloom is enabled, DarkXL renders the scene into 2 render targets (one for the scene itself and one for "emissive" luminance), does some post processing and composites the results into the backbuffer. So standard driver based MSAA will have trouble with this setup. I could do MSAA render targets to fix the problem on my end but I haven't done it yet.

_________________
DarkXL....http://darkxl.wordpress.com