[SirKnightly]

Here is the nightly for 06 September 2016 - Revision 60fff3f


Group: Linux
nightly_20160906_60fff3f-builds-Linux.tar.gz
SHA1: 0cbae59b2127dc56b3da94b08ac8094ff46faf14


Group: MacOSX
nightly_20160906_60fff3f-builds-MacOSX.tar.gz
SHA1: d74bb7ff8265a00ea8eed58485bb6b25a843e649


Group: Win32
nightly_20160906_60fff3f-builds-Win32.zip
SHA1: c0721001d050f3ec3f196a9828573ed3433d97e3

Code: [Select]

------------------------------------------------------------------------
commit 1c712a7
Author: asarium <Tue Sep 6 15:19:20 2016 +0200>
Commit: asarium <Tue Sep 6 15:19:20 2016 +0200>

    Fix nightly build configuration
 ci/travis/check_release.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[chief1983]

I would have thought there'd be another commit in this log, since the only reason we saw nightlies were broken is that it had already tried building a nightly with the new commits.

[m!m]

The nightly script can only show the log from the last tag to the current tag and since the "last tag" was the one that failed only the new commit is shown in the log.

[Cobra]

At the very least since the September 4 nightly, it is possible to target ships and objects with the "hidden-from-sensors" flag assigned to them.

[AdmiralRalwood]

At the very least since the September 4 nightly, it is possible to target ships and objects with the "hidden-from-sensors" flag assigned to them.

Looks like Ignore_List (the list of flags that make a ship invalid for targeting, including Hidden_from_sensors) isn't being initialized because set_default_ignore_list() isn't actually called anywhere. Thanks for the report; hopefully we'll have this fixed by the next nightly.

[Cobra]

Late, but was the regular directory for the debug log changed? This nightly isn't generating debug builds where they used to be.

[The E]

Logs are now written to %appdata%\HardLightProductions\FreeSpaceOpen\data\

[Cobra]

I thought I'd read somewhere that they got changed but thought I was mad. Thanks.