[Echelon9]

Updated to reflect initial testing results of the Valgrind 10.6 patch.

[Echelon9]

Updated to reflect GCC 4.2 is now compatible with Xcode 3.2.1 in certain configurations.

[Echelon9]

• By default, Xcode 3.2 (the latest version of Apple's development IDE) uses GCC 4.2 as compiler. This changes leads to numerous "deprecated conversion from string constant to 'char*'" errors, plus a few others.
• The more complete solution to see the FS2_Open codebase comply with this new GCC 4.2 requirement will take some careful commits to ensure we don't break things cross platform.

That one is known... chief forwarded a (massive) patch to me put together to fix this problem, however it was done against a trunk that was wayyy out of date (don't worry folks, we haven't forgotten!)

Do you still have a copy of this patch portej05/chief1983? I'd like to work on it as free time arises.

[Echelon9]

Updated to reflect the current state of OpenGL on Mac OS X with the new unified shader code.

[Echelon9]

Big update to reflect the fixes with Xcode 3.2.2 and OS X 10.6.3, and that trunk versions of valgrind now build on Snow Leopard.

[blowfish]

GLSL seems to be working with no slowdowns, but there is one strange thing I've found...

In GLSL mode, ships don't disappear as they pass through the subspace vortex warping out

[Echelon9]

GLSL seems to be working with no slowdowns, but there is one strange thing I've found...

In GLSL mode, ships don't disappear as they pass through the subspace vortex warping out

Yes, Mac OS X 10.6.3 has seen big improvements in OpenGL performance from my testing too.

A couple of issues still remain though:

• Environment mapping occasionally displays a patched, corrupted pattern.
• The issue with GLSL float array constructors remains (but we have a workaround in the unified shaders).
• Ships don't disappear as they pass through the subspace vortex warping out (may not be Mac specific)

[chief1983]

Blowfish, I think that's been a bug on all platforms, not just OS X.  But it's good to hear that GLSL performance has been substantially improved.  In fact that's great f***ing news.

[blowfish]

Blowfish, I think that's been a bug on all platforms, not just OS X.

Okay, that's good to hear ... I just assumed that it was probably mac-specific because I hadn't ever heard it mentioned...

[chief1983]

1866  Pretty sure there have been reports of this on Windows, even if not 100% of the time.  May be chipset related?

[neoterran]

Oh I'm so psyched. It was pretty much unplayable for me with GLSL for almost 2 years, so thank god we finally got some love.

Looks real good, and framerate rocks.

[chief1983]

Probably need to clean up some Mantis issues.  And maybe need to tweak the project file.  Are we going to need multiple setups now?  One for Xcode on 10.5 and one for Xcode on 10.6, so we can take advantage of all the stuff in Xcode 3.2.2 that works now?

[blowfish]

I haven't been able to compile under the 10.6 SDK, so I think it's just 10.5 for now.

Also one thing I should probably mention - the ogg framework is out of date.  I belive Goober updated the windows library for the DEM Interlude release, but Mac builds use a different framework, which crashes when trying to open a cutscene in that campaign.

[chief1983]

I believe I remember this being brought up already.  Be nice to get it patched into the Frameworks file, otherwise we could just wait until the unified one we're planning for Windows/OSX.

[Echelon9]

Probably need to clean up some Mantis issues.  And maybe need to tweak the project file.  Are we going to need multiple setups now?  One for Xcode on 10.5 and one for Xcode on 10.6, so we can take advantage of all the stuff in Xcode 3.2.2 that works now?

I've been examining the merits of having two separate Xcode project files for a little while; one the current and one that employs the latest and greatest (as Visual Studio project files have done for VS2005, 2008 and 2010). You may not realise, but the current Xcode project file is still in an old 2.x format.

I'd want to make sure there are real differentiators between the two that could be unleashed, so a bit more testing is needed. But watch this space...

[chief1983]

No, I definitely realized that Echelon

Would love to have a dedicated 3.2.2+ project file, and one we could just use on 10.5 and 3.1.x.  Although I'm not sure how maintained the latter would stay.  I know I can't.

[underwood]

I've compiled and have been running for a while now a 64 bit/10.6 version of FS2 (version 3.6.11). If anyone would like to try it, I've uploaded a copy here; http://www.mediafire.com/file/imc3gmh4nyj/FS2 3.6.11 x86_64.zip

[blowfish]

Wow ... my understanding was that 64 bit would not compile on any platform ... how did you get it to work?

[underwood]

I only had to modify for deprecation, change a couple of lines for 64-bitness, and compile. Quite simple. It consumed about 10 minutes of time.

[The E]

More interesting to me is, which trunk revision is this? Can you upload a .patch or diff of your changes?