[niffiwan]

New Linux builds here, the last few platforms should complete soon.
https://build.opensuse.org/package/show?package=fs2open-blueplanet&project=home%3Aniffiwan

[Cyker]

Uh, say, I don't suppose someone could compile the BP 3.6.17 in VC2008 instead of 2010 for me?

Even with DLL substitution and hacking the minor version to not require XP I still get an error saying it's not a valid Win32 exe

Alternatively, is there a 2008-compiled nightly/test build that works with BP?

I stupidly upgraded BP with the complete installer so it no longer works with vanilla SCP

[General Battuta]

Uh, say, I don't suppose someone could compile the BP 3.6.17 in VC2008 instead of 2010 for me?

Even with DLL substitution and hacking the minor version to not require XP I still get an error saying it's not a valid Win32 exe

Alternatively, is there a 2008-compiled nightly/test build that works with BP?

I stupidly upgraded BP with the complete installer so it no longer works with vanilla SCP

Why do you need to compile your own build?

[Cyker]

VC2010 purposefully breaks Win2k compatibility by setting some PE version headers; The official released SCP builds are now done in VC2008 (thankyouthankyouthankyou) but the BP isn't

Usually I can patch the exe myself to make it work but for some reason the usual fixes don't work on the BP exe...

[The E]

I do not care about Windows 2000. Win XP is the oldest Windows I can and will support.

[Cyker]

That's fair enough; Can I assume the BP patch is for the current svn of SCP?

I can try and see if I can get it compiling in VC6 or something

I find compatibility problem of this 'not a valid Win32' ilk is usually due to the compiler/linker and not the code so hopefully it won't be too hard...

[-Norbert-]

Now that the 3.6.18 build is released, should we still use the BP specific 3.6.17 or switch to the SCP release?

[General Battuta]

Now that the 3.6.18 build is released, should we still use the BP specific 3.6.17 or switch to the SCP release?

Pretty sure the 3.6.18 build won't work.

[jg18]

Yeah, 3.6.18 won't work.

[Cyker]

Gave up trying to compile it with VC6 (Couldn't get the STL thing Goober mentioned to work; Many errors, don't know how to fix).

Managed to dig up my VC2005 disc - Compiles much more effortlessly with that \o/
Release exe runs but crashes saying something could not be read.
Annoyingly the Debug exe works which is going to make tracking down the cause of that tricky! A cheap hack way of working around that usually is to fiddle with the optimization settings; I'll try changing -O2 to -O to see if that helps.

One strange anomaly is that the exes are noticeably smaller than the 'official' BP exes; The Release is 4.5MB vs 6.2MB and the Debug is 9.76 vs 10.9!

On a slight tangent, I've always wondered how are you supposed to use the debugger with fullscreen on-top things like this?
Is the only way to have dual monitors??


Edit: Ooops, spoke too soon! Debug build can load the FS2 retail campaign but crashes trying to load the BP campaigns.
Seems to be a problem parsing the .fc2 as it says "Expecting int, found [BP2-Part1End]"

Maybe a mismatch somewhere between the BP.patch and the SVN snapshot I have...? Ugh...  I can see this is going to need more zots than I wanted to spend!

[The E]

The trick is not to do that. Use -window mode.

[Cyker]

*facepalms* I'm such an idiot XD

[The E]

I have updated the builds to the current revision of FSO. This means that they're no longer based on the antipodes branch (since that branch has been merged back into trunk in preparation of 3.7.0). It also means that the filenames have changed; these are no longer 3.6.17 builds, but rather 3.6.19, so adjust your launcher settings accordingly.

[Naxal]

Newb: What exactly does the Patch file do and what do I do with it?

[The E]

The .patch files are provided for developers who want to make their own builds based on the experimental code in the BP builds. As a normal user, they're of no use to you.

[Naxal]

Ah alright, thanks.

[Nemesis6]

I think I noticed a bug... at least I think it's a bug -- Outside of the Blue Planet campaigns, lightshafts do not seem to work. Anyone else having this issue?

[MatthTheGeek]

It's intended behaviour. Lightshafts are to be activated on a per-mission basis.

[Yarn]

Changes from the last released ones:
-Reworked the behaviour of the "Lighting Detail" setting in the options menu for greater granularity. New settings are like this:
0: Only ambient lighting
1: Ambient and Specular lighting from suns
2: Lights from explosions
3: Lights from damage lightning
4: Glowpoint lights, every second weapon light
5: All lights

You have six levels shown there, but the game only lets you choose from five, so either 0 or 5 (probably 5) can't be selected at all. This needs to be condensed somehow to five levels.

[Klaustrophobia]

is the forthcoming 3.7.0 going to be compatible, or will we need to carry on using BP builds?