[FreeSpaceFreak]

Small heads up: none of the individual-download packs for the AoA re-release includes a mod.ini or launcher picture.

[Ranger1]

Do you mind using the same build, but playing the regular FreeSpace 2 campaign, with or without the MediaVPs? This'll let us know if it's something in the BP data causing the problem for you, or something in the build.

Because this error is somehow peculiar to your software or hardware setup, do you also mind making sure all your drivers are up to date? Hopefully we can close in on what's doing this.

I will try that when I get the opportunity and let you know.  As far as drivers.  They are the latest nvidia drivers from their sight.  I did a driver update when the problem originally came up with no change.

[Master_of_the_blade]

Do the custom flags override the generated ones in wxLauncher? If not, how do I modify the flags?

[pecenipicek]

Do the custom flags override the generated ones in wxLauncher? If not, how do I modify the flags?

the last flag on the commandline is the one that gets used, the preceding ones are ignored, i think.



also, as a general note, the BP patch does not apply to latest antipodes. if you are getting patching failures on files other than the vxproj/vcproj files, revert the antipodes to r9504 and patch that.

(i used it on 9504 that is, dunno with which others it works, but i think one of the trunk sync's after broke it)

[FreeSpaceFreak]

Additional Linux compile instructions are on the way.

Since the way appears to be quite long, I took the liberty of writing my own

Linux: Compiling FSO for BP in 12 easy steps
(Note for Linux users: feel free to improve or correct me where appropriate)
(Note for non-Linux users: no it's not cumbersome. The Windows instructions have over 20 steps and take way longer to complete )

1. Open a terminal; on Ubuntu and its brethren, Ctrl-Alt-T should do it.
2. Install the required dependencies for your system
3. Install SVN if you don't have it yet. On Ubuntu, Mint and other Debian-based systems, the command is sudo apt-get install subversion
4. Go to the place where you want to put the FSO code: cd ~/directory/to/put/the/code
5. Check out the code: svn checkout svn://svn.icculus.org/fs2open/branches/antipodes (a ./antipodes directory will be created, containing all of the required code).
6. Get the most recent version of the patch from here; extract the file BP.patch to somewhere near your checked-out code.
7. Open BP.patch (any old text editor will do); line 3 should end with (revision 9485). The number (here 9485) is important.
8. Go inside the directory you checked out: cd antipodes
9. Update your code to the version against which the patch was generated: svn update -r 9485 (replace 9485 with the number from step 7).
10. Apply the patch: svn patch ~/path/to/BP.patch
11. Configure the build files with ./autogen.sh - build the code with make
12. Copy the ./code/fs2_open_3.6.17 file to your FSO directory, select it in wxLauncher and you're good to go!

[niffiwan]

Since the way appears to be quite long, I took the liberty of writing my own

nice work 

[Phantom Hoover]

Do the custom flags override the generated ones in wxLauncher? If not, how do I modify the flags?

There's a button to turn off the lighting preset and copy the current settings to the custom flags. Use that.

[Master_of_the_blade]

Do the custom flags override the generated ones in wxLauncher? If not, how do I modify the flags?

the last flag on the commandline is the one that gets used, the preceding ones are ignored, i think.



also, as a general note, the BP patch does not apply to latest antipodes. if you are getting patching failures on files other than the vxproj/vcproj files, revert the antipodes to r9504 and patch that.

(i used it on 9504 that is, dunno with which others it works, but i think one of the trunk sync's after broke it)

Confirmed. The last flag overrides the preceding ones.
Also, I never quite understood .patch files. Are they used to generate complete .exe builds or can they be used to add to the existing builds? I know this isn't the right thread to ask to is there a thread that tells me about patch files?

[The E]

Also, I never quite understood .patch files. Are they used to generate complete .exe builds or can they be used to add to the existing builds? I know this isn't the right thread to ask to is there a thread that tells me about patch files?

Patch files contain information about all the changes from the source code in the SCP code repository. A coder can get the "official" code from the SCP svn, apply the patch, and then build his own BP builds. (In short, it's one of those "if you do not know about them, they're useless to you" kind of deals.

[EvidenceOfFault]

Additional Linux compile instructions are on the way.

Since the way appears to be quite long, I took the liberty of writing my own

Linux: Compiling FSO for BP in 12 easy steps
(Note for Linux users: feel free to improve or correct me where appropriate)
(Note for non-Linux users: no it's not cumbersome. The Windows instructions have over 20 steps and take way longer to complete )

1. Open a terminal; on Ubuntu and its brethren, Ctrl-Alt-T should do it.
2. Install the required dependencies for your system
3. Install SVN if you don't have it yet. On Ubuntu, Mint and other Debian-based systems, the command is sudo apt-get install subversion
4. Go to the place where you want to put the FSO code: cd ~/directory/to/put/the/code
5. Check out the code: svn checkout svn://svn.icculus.org/fs2open/branches/antipodes (a ./antipodes directory will be created, containing all of the required code).
6. Get the most recent version of the patch from here; extract the file BP.patch to somewhere near your checked-out code.
7. Open BP.patch (any old text editor will do); line 3 should end with (revision 9485). The number (here 9485) is important.
8. Go inside the directory you checked out: cd antipodes
9. Update your code to the version against which the patch was generated: svn update -r 9485 (replace 9485 with the number from step 7).
10. Apply the patch: svn patch ~/path/to/BP.patch
11. Configure the build files with ./autogen.sh - build the code with make
12. Copy the ./code/fs2_open_3.6.17 file to your FSO directory, select it in wxLauncher and you're good to go!

Thank you for providing instructions for Linux users! I have a bit of a noob question though, SVN doesn't recognise the command "svn patch", and it's not listed in the help file either. I don't use SVN much, what am I doing wrong?

[FreeSpaceFreak]

Thank you for providing instructions for Linux users! I have a bit of a noob question though, SVN doesn't recognise the command "svn patch", and it's not listed in the help file either. I don't use SVN much, what am I doing wrong?

Hmm, are you sure you're calling it from inside the antipodes directory? Could you post your exact command-line input and the response it gives?

[EvidenceOfFault]

Scratch that, found the issue already:
Looking at the SVN docs, "svn patch" is a new feature in svn version 1.7. The Ubuntu 12.04 repositories only have version 1.6, so I had to build subversion from source. What a pain.
After that, everything went fine. Played blue planet a bit, seems to work alright. Looks neat, framerate is a bit low occasionally, but I'm not complaining.
Thanks for the instructions, they set me on the right track.

[qwadtep]

Do you mind using the same build, but playing the regular FreeSpace 2 campaign, with or without the MediaVPs? This'll let us know if it's something in the BP data causing the problem for you, or something in the build.

Because this error is somehow peculiar to your software or hardware setup, do you also mind making sure all your drivers are up to date? Hopefully we can close in on what's doing this.

I will try that when I get the opportunity and let you know.  As far as drivers.  They are the latest nvidia drivers from their sight.  I did a driver update when the problem originally came up with no change.

I'm having the same problem with Catalyst 11.12. It doesn't seem necessarily tied to capships; looking at the fleet in Universal Truth was fine but it blacked out when facing an incoming bomber wing.

I suspect it has something to do with the lighting code, as in Fallen Angel the blackout only occurred when the Sathanas opened fire, but not before when it and the Keeper were onscreen and not after the Keeper exploded.

Haven't had the opportunity to check with just MediaVPs yet--hang on.

e: ran through Massive Battle 2 and Grizzly Bearbaiting on MVPs without issue. Seems specific to BP. Also, even though I said I suspect the lighting code, changing the lighting detail has no effect.

[General Battuta]

Welp uh oh

[pim]

Hi.
 Code compiles well but doesn't start at all (Even without any cmd opt.). Debug build starts OK with mod BP, with mod BP2 crashes immediatelly. Log is attached. Any ideas?
 Where can I get actual checksums for vp files? On http://www.hard-light.net/forums/index.php?topic=70511.0 are fs2_open.log checksums for 3.6.14 Release Build, not for 3.6.17, so I cannot verify file corruption.

[attachment deleted by a basterd]

[The E]

You are using an Intel HD chip. You need to run the executable with -no_glsl, as those chips are too crap to handle the shaders we're using.

Secondly, all BP parts require the MediaVPs, so in order to start AoA, you need to use -mod blueplanet,mediavps_3612
WiH requires both AoA and the MVPs, so the -mod commandline should read -mod blueplanet2,blueplanet,mediavps_3612

[pim]

Thanks for your answer.
Regular build crashes anyway:

Code: [Select]

[nabuko@nabuko mediavps_3612]$ ./fs2_open_3.6.17 -no_glsl -mod blueplanet2,blueplanet,mediavps_3612
ATTENTION: default value of option force_s3tc_enable overridden by environment.
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
System log says

Code: [Select]

Jan 14 17:45:39 nabuko kernel: [ 6998.810555] fs2_open_3.6.17[1287]: segfault at 70 ip 00000000004c9a78 sp 00007fff57afc8e0 error 4 in fs2_open_3.6.17[400000+5c0000]
On the other hand

Code: [Select]

./fs2_open_3.6.17_DEBUG -no_glsl -mod blueplanet2,blueplanet,mediavps_3612 works.

I haven't checked any other cmd options yet.

[FreeSpaceFreak]

I haven't checked any other cmd options yet.

... is there a reason you're not using the launcher?

[qwadtep]

Welp uh oh

It may help to note that parts, but not all, of the GUI black out. See attached. Not pictured is that normal comms also black out, but internal dialogue (I can't feel my body, etc.) is fine.

e: found that in WiH, the HUD sometimes disappears without the whole screen blacking out, though the latter does still happen.

[attachment deleted by a basterd]

[pim]

... is there a reason you're not using the launcher?

Yes: Info from Arch linux AUR package.
I haven't digged for details but it does not work as expected because it allows to select either mod or executable, not both at once.
Actually simple symbolic link helps to see both mods and executable at the same time but no build starts for me this way even with the same cmd options as in previous post.