[chief1983]

Here it is! The final 3.6.12 build! Included below is the commit history since RC4.
Previous 3.6.10 Release Thread

Important!!
As always, you need OpenAL installed.  Linux and OS X come with it but Windows users will need to get Creative's OpenAL installer.

Important!!
Also, since the internal code linking for TrackIR was revised, an external DLL is now required for FSO to use TrackIR functions.
The following DLL is simply unpacked in to you main FreeSpace2 root dir.
TrackIR is only supported on Windows.
TrackIR SCP DLL

Launchers, if you don't have one already:
Windows:  Launcher 5.5g (new launcher version! (Mirror) Support for all nightly builds as well as <= 3.6.12) or wxLauncher (ongoing project for a unified launcher on all platforms)
OS X:  Soulstorm's OS X Launcher 3.0 or wxLauncher (ongoing project for a unified launcher on all platforms)
Linux:  YAL or by hand or whatever you can figure out.

Known issues:

• None! (other than those already in Mantis )

WINDOWS Builds

Inferno Builds (HIGHLY RECOMMENDED)
If you don't know which one to get, get the first one.  If you don't know what SSE means, read this: http://en.wikipedia.org/wiki/Streaming_SIMD_Extensions
You can use freely available tools like CPU-Z to check which SSE capabilities your CPU has.

fs2_open_3_6_12_INF.zip (Mirror)
MD5: 00fc51c444391228b43b67c0ab4afe9c

fs2_open_3_6_12_INF_SSE.zip (Mirror)
MD5: ee465086a3d8ac51f1d440b6a74a9afb

fs2_open_3_6_12_INF_SSE2.zip (Mirror) (Mirror 2)
MD5: c026d6165dd456344097b6a64a7e4591

What are those SSE and SSE2 builds I keep seeing everywhere?
Your answer is in this topic.

Standard Builds (USE ONLY AS DIRECTED)
These are provided only so that any problems encountered can be checked
to make sure that it is not being caused by the INF_BUILD settings.

fs2_open_3_6_12.zip (Mirror)
MD5: 821989d0c122d8dcc6a9b3c277efdf34

fs2_open_3_6_12_SSE.zip (Mirror)
MD5: 778180075f9faddab108a464e41df264

fs2_open_3_6_12_SSE2.zip (Mirror)
MD5: 2549b60d9f4cdf2f7efc6275cebd1f82

Visual Studio 6 Builds (USE ONLY AS DIRECTED)
These are provided for compatibility with Windows 9x systems, but the SCP team generally prefers the above builds created with Visual Studio 2008.

fs2_open_3_6_12_INF.zip (Mirror)
MD5: A6EF8309A20E91D6143464E636A42AEC

fs2_open_3_6_12.zip (Mirror)
MD5: 53E9020936E227490B3A03B27A1B3B3E


OS X Builds

Inferno Build (HIGHLY RECOMMENDED)
FS2_Open_Inferno-3.6.12.dmg (Mirror)
MD5: 1abdd914369738f7ea672f7bbbe4340e

Standard Build (USE ONLY AS DIRECTED)
This is only provided only so that any problems encountered can be checked
to make sure that it is not being caused by the INF_BUILD settings.

FS2_Open-3.6.12.dmg (Mirror)
MD5: 156117a8e8d9c1ff29a95c6500f3e397


LINUX Builds

Inferno Build (HIGHLY RECOMMENDED)
fs2_open_3_6_12_INF.tar.bz2 (Mirror)
MD5: d23808d48981bfa6b88cb0696160df86

Standard Build (USE ONLY AS DIRECTED)
This is only provided only so that any problems encountered can be checked
to make sure that it is not being caused by the INF_BUILD settings.

fs2_open_3_6_12.tar.bz2 (Mirror)
MD5: 0e5c941955652f44bc7e5bd31fe44eaa

Source Code Export
fs2_open_3_6_12_src.tgz (Mirror)
MD5: afcbcc42de56db0e5942e4551e5865e9


Changelog since the last RC:
( Additionally, see here: 3.6.12 Changelog (since 3.6.10) )

Code: [Select]

------------------------------------------------------------------------
r6346 | taylor | 2010-08-03 03:30:46 -0500 (Tue, 03 Aug 2010) | 11 lines

various FS2NetD fixes:

 - increase sleep time during reconnect
 - better handling of disconnects from connection errors
 - proper disconnect in case of login failure
 - log stats request calls
 - don't try to read stats from packet when there aren't any to read
 - allow proper connection resetting with standalone
 - change auto-reconnect timeout from 30 minutes to 5
 - count server traffic among activity instead of just client traffic
 - reduce uneccessary client->server traffic
------------------------------------------------------------------------
r6345 | taylor | 2010-08-03 03:30:43 -0500 (Tue, 03 Aug 2010) | 1 line

fix debug message
------------------------------------------------------------------------
r6340 | chief1983 | 2010-07-30 14:57:53 -0500 (Fri, 30 Jul 2010) | 1 line

Remove /DEBUG in 3.6.12 builds like r6335 and r6336
------------------------------------------------------------------------
r6339 | chief1983 | 2010-07-30 11:30:16 -0500 (Fri, 30 Jul 2010) | 1 line

Backport of r6334: Patch for issue with ai-waypoints not working correctly. The ship's goals were accidentally cleared after a single run through the waypoint path.
------------------------------------------------------------------------
r6338 | chief1983 | 2010-07-30 11:28:43 -0500 (Fri, 30 Jul 2010) | 1 line

Backport of r6329: Fix/Workaround for Mantis 2272 (Int3() in hudtarget.cpp)
------------------------------------------------------------------------
r6337 | chief1983 | 2010-07-30 11:27:42 -0500 (Fri, 30 Jul 2010) | 1 line

Backport of r6325: Fix for reinforcement menu bug - Mantis 2246
------------------------------------------------------------------------

Zacam: Added link to 3.6.10 Release Thread, continuity.
Chief: Added Hunter's sectorgame mirrors for the builds 3/17/11

[Jabba]

Wow! That was quick 

[Jeff Vader]

Awesome sauce. Installation instructions and the FAQ updated to correlate with this fact.

Edit: Oops, there was an announcement already. Well, if anyone has a better highlight picture, please deliver it ASAP.

[Madcat]

Thanks a ton! 

[Macfie]

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

[T-Man]

Huzzah! To the download page!

Hats off to the FSOpen team for all their work! Pat on the back for you lot.

[The E]

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.

[T-Man]

just to quickly ask, what are the SSE builds for? This is my first time upgrading to an Inferno build so i'm not really clued up on it all.

Also, will i need to do anything special or can i just swap out the exe's and use all the existing files?

Thanks

[The E]

For an explanation regarding SSE, read this: http://en.wikipedia.org/wiki/Streaming_SIMD_Extensions

As for switching to Inferno, the only thing you'll be losing are your savegames.

[T-Man]

For an explanation regarding SSE, read this: http://en.wikipedia.org/wiki/Streaming_SIMD_Extensions

As for switching to Inferno, the only thing you'll be losing are your savegames.

Cheers. I will likely not need them as i run 32-bit.

[The E]

Umm.

SSE has nothing to do with x86 or x64. You really should try the SSE2 builds, as they'll probably give you a performance boost (Provided your CPU was manufactured after 2001).

[T-Man]

Oh i see. Sorry i must've misread the wiki. Shall give the SSE2s a try then.

[Colonol Dekker]

Good stuff,
 
I'll try the EVA S2 engine builds out. My Q6600 should gobble them up like slices of code pie.
 
 
I'm guessing MVPs to follow soon'ish then?
WiH Squeeeeeee.

[Commander Zane]

I thought this was the MVPs, I saw SCP 3.6.12 on the Highlights image and was bouncing off the walls.
Well, at least the rest should be very close at this point.

[chief1983]

SCP shouldn't make you think MediaVPs, as it's the Source Code Project.  FSU or MediaVPs will likely be in their highlight image

Also, they kind of depended on the SCP release so that was always going to be first.

[Droid803]

What are pdbs anyway?

[Nehemiah]

With regard to SSE1 vs SSE2, I read that your processor has to be a 64 bit x86 in order to use SSE2, whereas SSE1 just has to be an X86 machine.

[General Battuta]

With regard to SSE1 vs SSE2, I read that your processor has to be a 64 bit x86 in order to use SSE2, whereas SSE1 just has to be an X86 machine.

Hrm...really? 64bit, you sure?

[Colonol Dekker]

May as well be talking swedish to me. I'll try them later in the month. If it works it works. If not. . . . 3.6.5 reversion with zeta MVPS ahoy!

[The E]

With regard to SSE1 vs SSE2, I read that your processor has to be a 64 bit x86 in order to use SSE2, whereas SSE1 just has to be an X86 machine.

Nope, that's simply wrong.

Whether or not your CPU runs in 32 or 64 bit mode makes no difference regarding your ability to use SSE2.

Now, by the purest coincidence, most CPUs capable of executing SSE2 code is also capable of running 64bit code (because SSE2 is part of the x86-64 spec), but one feature does not need the other.