[Kolgena]

This is getting to be a pretty common question. We should have little tags like

"Recommended for CPUs made after 2001" or whatever, with disclaimers to default to the normal executable if your computer seizes up.

[The E]

You mean like what I added to the first post of the thread?

[Fury]

Idiot proofing your edit more by adding a link to CPU-Z.

[Kolgena]

You mean like what I added to the first post of the thread?

I just felt that a few extra choice phrases is better than a wiki article that after a 20 second cursory read doesn't really help you choose the right build.

[The E]

Which is why CPU-Z was mentioned as well.

[Iss Mneur]

What are pdbs anyway?

Program Database.  They contain the mapping of the source code to the machine code in the .exe.  They are what allow the debugger (for the coder types) and the stack traces (that appear on Asserts, Errors, Warnings, etc) to be meaningful.

[Macfie]

I thought r6340 was supposed to get rid of the pdb files.  They are still included in the release.

What gave you that idea? 6340 got rid of pdbs for release builds, debug builds still need them.

I've never seen the pdb files in the final release before.

[FUBAR-BDHR]

They never existed before 3.6.11 so you would never have seen them in a release.

[Mobius]

Wow! Downloading now.

[chief1983]

I should mention, this is to my knowledge the first final release ever to not have been built with Visual C++ 6.0.  We instead moved to using Visual Studio 2008.  Who knows, next release might even be Visual Studio 2010 as I've already acquired a license for it.

[sigtau]

I should mention, this is to my knowledge the first final release ever to not have been built with Visual C++ 6.0.  We instead moved to using Visual Studio 2008.  Who knows, next release might even be Visual Studio 2010 as I've already acquired a license for it.

Either you're a lucky son of a ***** or you've got deep pockets. 

Regardless, great job guys, downloading now.

[chief1983]

Either you're a lucky son of a ***** or you've got deep pockets. 

The former

[TParis]

Congrats to the team for the release. 

I could need some support here, even though I have no idea how the new owners of Xfire are handling their new program:
http://de.xfire.com/forums/182627/topic/2077772/

[Jessnec]

Yeaaaaaaah! thanks for this final releaseeeeeeeeeee!

[chief1983]

Congrats to the team for the release. 

I could need some support here, even though I have no idea how the new owners of Xfire are handling their new program:
http://de.xfire.com/forums/182627/topic/2077772/

I've commented on that thread.

[TParis]

Thanks.

What about the new shaders? Anything I gotta do to get those working? Just wondering, because the required files have always been included as links in the old RC threads...

[chief1983]

They will be included with the new MediaVPs, so I intentionally left them out of this post.  You don't want them present in your root FS2 folder, as any mod that wants to utilize them should include them itself.  Any mod that depends on the MediaVPs 3.6.12 will have them by default then.  There will be a standalone release for other mods/TCs to use, but it won't be for general consumption, so I omitted it.

[Klaustrophobia]

As it stands now, is everything going to come crashing down if I have the "Enable Postprocessing" box ticked and I don't have some other files?

[Iss Mneur]

As it stands now, is everything going to come crashing down if I have the "Enable Postprocessing" box ticked and I don't have some other files?

No, it shouldn't.

If the postprocessing files are not present the engine should just silently turn off post processing (it will log to the debug log that is has disabled postprocessing but it will not show an error or a warning box).  This has not changed from RC2.

[karajorma]

Be warned that if you do have those files it may come crashing down anyway. There is a reason why PP was moved to Experimental after all.