Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Regeaj on April 14, 2010, 01:21:02 pm

Title: Black Screen...but only in some campaigns
Post by: Regeaj on April 14, 2010, 01:21:02 pm
Heyho...Currently playing Freespace 1, 2 and Bayblon 5 Project.

From time to time I encounter an user made campaign, which isnt playable. Sometime the first mission, but sometime a later one, just flickers and produces a black screen. I can hear audio, and by press buttons make some lights appear, but have non control whatsoever.

The "original" campaigns works fine...until know.


It looks exactly like what the guy encountered in this thread: http://www.hard-light.net/forums/index.php?topic=68948.0 But as I said, only in some missions / campaigns.
Title: Re: Black Screen...but only in some campaigns
Post by: General Battuta on April 14, 2010, 01:31:30 pm
Debug log, please.
Title: Re: Black Screen...but only in some campaigns
Post by: Regeaj on April 14, 2010, 01:42:29 pm
Quote from: General Battuta on April 14, 2010, 01:31:30 pm
Debug log, please.

Meh, I just read the other thread again and realized its indeed the exact same problem. Im also not able to start the Debug-Version of the Launcher.
Title: Re: Black Screen...but only in some campaigns
Post by: General Battuta on April 14, 2010, 02:20:33 pm
There is no Debug version of the launcher. Just select a debug exe (ends in -d) in the Launcher's select field.

What system are you on? We can't help you with the problem until we have a bit more information.
Title: Re: Black Screen...but only in some campaigns
Post by: Jeff Vader on April 14, 2010, 04:10:59 pm
The Launcher is just a tool for defining settings and ****. And selecting what FSO build to use (for example, fs2_open_3_6_10.exe).

Details on how to "run a debug build" are here (http://www.hard-light.net/forums/index.php?topic=56279.msg1180359#msg1180359).
Title: Re: Black Screen...but only in some campaigns
Post by: General Battuta on April 15, 2010, 07:23:50 pm
We're getting this issue in a reproducible state now.

I think a recent FreeSpace open commit may have caused this problem.