[General Battuta]

I don't want a bunch of people to be unable to play on older hardware, especially because of an option that can't be disabled.

[knossosfs2]

Luckily I saved the older BP. I just placed the newer one in a different folder, so don't worry too much about it. I was just curious as to whether I could fix it myself.

[An4ximandros]

The missing song reminded me of something... have you guys already considered a replacement for the Antarean Theme from AFF? Last time I talked to the team they didn't appreciate having their stuff used on non-AFF material. This came after a bajillion people stole or modified assets from the HW2 mod.

[General Battuta]

We'll contact them right away. Fair use is really important to us.

[[Wolf]Maverick]

Hi, playing WiH1 with the new BP Build, i get an error during mission "Post Meridian", during the Maxim Strike and right before the end, i tried it several times, always the same error

Cannot find a dock path for ship Indus Alpha 2, dock index 0.  Aborting dock.

ntdll.dll! NtWaitForSingleObject + 21 bytes
KERNEL32.dll! WaitForSingleObjectEx + 67 bytes
KERNEL32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_SSE2_BP.exe! <no symbol>
KERNEL32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

[Klaustrophobia]

i thought the general feeling was "never again!" last time you guys released something that required newer than the latest official release?

[General Battuta]

That was the feeling! We didn't anticipate the SCP release cycle being so slow and now our campaign doesn't work on the current stable release or the next planned stable release.

[[Wolf]Maverick]

Sorry to say, same error twice in "Darkest Hour", don't know if it helps.

[General Battuta]

We're checking it out.

[General Battuta]

Can't repro it. Really want to fix it before the Act 3 release in the next day or so.

[General Battuta]

Sorry to say, same error twice in "Darkest Hour", don't know if it helps.

Hey [Wolf]Maverick, are you using one of the new Kentauroi models released by Steve-O in the last couple days?

[Echelon9]

Something is wrong with the 7z package.
Have downloaded the non-executable archive (for Linux/MacOS) from FSMods, and getting the files and folder structure but all zero kb files.

Still having this issue Echelon?

Yes, unfortunately. Have tried with a different Mac 7zip decompresser (7zx) and still seeing the same problem.
I don't suppose any Linux users have tried? Is there a command line equivalent of untar -xvzf that support 7zip?

Managed to uncompress the 7zip archive with a Mac program called Keka. Looks like the other 7z Mac programs haven't been updated in a few years, and for some reason couldn't support the settings used in your compressed archive.

Worth noting this for other Mac users, as Keka is reasonably new but also a very nice piece of software. Gets my recommendation.

[[Wolf]Maverick]

@General Battuta
No, only the original BP Stuff. As far as i can tell, the error only occurs when i'm flyring really close to a frigate, don't know if this is helpful.
Please don't hesitate to release Act 3 because one guy has an error you can't reproduce

[Veers]

Just posting my settings, which are based mainly to play BP with. I tried going very dark, light from weapons or natural sources. And highlighting lights on ships for example.


-ambient_factor 35 -ogl_spec 80 -spec_exp 20 -spec_point 1.5 -spec_static 1 -spec_tube 1.5 -no_emissive_light  -fxaa_preset 6

Also haven't encountered any issues that I am aware of. Things are fantastic, as always.

[Yarn]

Before playing any missions, I noticed two problems:

• The build that's provided displays an error message saying that there's no disc in the CD drive. I am able to click "continue" to play the game, but this message gets annoying.
• The problem mentioned in this thread still isn't fixed. Here are links to the fixed files:
  Blue Planet 1 species.tbl fix
  Blue Planet 2 species.tbl fix Looks like this one has been fixed. However, species.tbl in BP: AoA still has undisplayable non-ASCII punctuation.

[Solatar]

Is there any way to turn off the lighting setting that makes each primary bolt a lightsource?  Simply firing weapons near a ship drops my framerate by half at best (in addition to a consistent 20fps hit compared to older builds) using this build.  My machine's kind of old and not great by today's standards, but I can run the 3.6.15 nightlies just fine.  That said, the still images that result are really nice, if unplayable. 

I love the new intro "cutscene", it adds a lot.

[Ryuseiken]

Is there any way to turn off the lighting setting that makes each primary bolt a lightsource?  Simply firing weapons near a ship drops my framerate by half at best (in addition to a consistent 20fps hit compared to older builds) using this build.  My machine's kind of old and not great by today's standards, but I can run the 3.6.15 nightlies just fine.  That said, the still images that result are really nice, if unplayable. 

I love the new intro "cutscene", it adds a lot.

In whichever launcher you're using, add -spec_point # to your custom flags, it sets how much light is generated by your primaries. The default value is 1 (i.e -spec_point 1) so try lowering it down to something like -spec_point 0.5 and see how much that helps.

[Solatar]

Lowering that changes the brightness of the lights, but I think my computer is choking on the number of them. For example, a Balor being fired near a destroyer (first mission) brings me from 30 to 15 fps, but the Prometheus stays in the mid 20s (fewer shots). 

[Phantom Hoover]

Lowering spec_point won't do a thing, the engine's still doing the same calculations anyway. Setting it to 0 might work if the code's smart enough to realise it doesn't need to bother with weapon lighting.

[knossosfs2]

I'm having the same problem as Solatar, and my fps drops from 30 to 10 at the lowest.