[Zacam]

Test Build (Windows): 16 Dec 2009 - Based on Revision 5720

Now includes (By Request): Voice Recognition, Text to Speech. (EDIT: Apparently -voicer is still broken, my apologies)

z-WIN-20091216_r5720-INF-SSE.7z
MD5Sum: 7207F4570CFA287722BFCBD2C0801733

z-WIN-20091216_r5720-INF-SSE2.7z
MD5Sum: A6F6473B137EBBACB1B1D9BE00A38EC4

The following patches were applied to this Test Build. They were applied and are dependant on being applied in the following order:
#1 5720-Warnings.patch
      Resolves under MSVC 2008 compiler Warnings for the /code/ directory. This requires the most testing under other platforms to make sure this introduces no breaks in compiling.
      Includes Hery's data for hopefully resolving Mac OS X compile issues (but does not include xcode updates, so please SHARE!)

#2 5712-PNG-Full.patch
      Adds .PNG file support. Now modified for generating no warnings under MSVC 2008. Also needs serious testing in other platforms, specifically operational testing for EFF support.

#3 5712-Brief_Text_Crayola.patch
      This one is entirely optional and is related to this post: Re: Briefing text coloring bug fix
      It does not contain pedros changes, it just merely adds more color string cases to the Briefing texts, and removes the Int3() crash for an unknown value.
      It will give a warning pop-up as well as an entry in the debug log for any undeclared or unused '$c' value being used.

Also: For testing with this build or in case folks don't already have them:
MediaVP SVN Unified Shaders with Hery's Post Processing shaders and default TBL.

All *.sdr files go in to either Freespace2\Data\Effects or Freespace2\Mediavps\Data\Effects
TBL goes in either Freespace2\Data\Tables or Freespace2\MediaVPs\Data\Tables
(or whatever your path setup is, you could even multi-mod if you want)

[Fury]

Zacam had updated shader link in above post, I would suggest everyone to overwrite their shaders with those. Now works properly in Radeons too.

[Fury]

FYI, to avoid possible confusion. Anti-aliasing does not work if post processing is enabled. I've heard this may work on some NVIDIA cards, but details are sketchy. On Radeons it doesn't work on 4000 series and earlier. 5000 series is unconfirmed.

[pecenipicek]

antialiasing doesnt work with postprocessing (referred to as PP in my post), from my experience. tested with an nVidia GTX260, pretty much no AA when using "enhance application settings" instead of "override app settings". tested only on windows and not as thoroughly as i'd like. to any who can help in this area, get the nHancer app first, and do all the AA and AF options through there, not through the nvidia CP. (this is on windows only, i cannot test on linux atm, since i'm not at home....)

this is probably due to the new FBO's used by PP, which the AA algorithm fails to catch, ergo... no AA. also needs further detailed testing, however AA and PP on ATi is right out of the question. the drivers are simply that crappy, sorry folks

[Zacam]

I have it working only when I don't use the -bloom command line option to set bloom intensity. That may be the reason why.

[Rodo]

antialiasing doesnt work with postprocessing (referred to as PP in my post), from my experience. tested with an nVidia GTX260, pretty much no AA when using "enhance application settings" instead of "override app settings". tested only on windows and not as thoroughly as i'd like. to any who can help in this area, get the nHancer app first, and do all the AA and AF options through there, not through the nvidia CP. (this is on windows only, i cannot test on linux atm, since i'm not at home....)

this is probably due to the new FBO's used by PP, which the AA algorithm fails to catch, ergo... no AA. also needs further detailed testing, however AA and PP on ATi is right out of the question. the drivers are simply that crappy, sorry folks

same here, never mind what kind of setting you select from the nvidia control panel, it doesn't work with bloom on, haven't tried with the other PP options so far.

[Herra Tohtori]

Based on my experiences, anti-aliasing itself works, but post processing has some lighting effects that dismiss anti-aliasing and in some situations show up jagged edges against, say, thruster glows or some such. But I definitely didn't have jagged edges all over the place. I've seen similar situations in Mass Effect, where anti-aliasing did not affect the shader effects either if I recall correctly.

This was with 3.6.10+patch MediaVP shaders (plus post-processing shaders) though, not the new ones.

EDIT: Didn't use bloom command line switch either.