[portej05]

Fury: The real limit is that it's 31 characters all up, including the full path to the file. We really should change this to _MAX_PATH, but then the question becomes what else will break if we do that

[Spicious]

Besides that should be possible to handle with fredding means.

Without using a heap of fire-beams?

[chief1983]

Hmm that doesn't actually seem like too long of a filename either.  How many extensions were tacked on to the end?  Just .dds or something?

[Angelus]

Hmm that doesn't actually seem like too long of a filename either.  How many extensions were tacked on to the end?  Just .dds or something?

Just .dds, converted to a DXT5 from a .tga

[Wanderer]

Besides that should be possible to handle with fredding means.

Without using a heap of fire-beams?

Well.. i never considered there to be a need to able to define ship by ship cases for turret targeting.. assumed game engine logic would be enough for that. I'm rather FRED disabled though (i lack ATL/MFC libs required to build and compile fred builds) i have no real idea what, how and where such things should be defined

[Spicious]

It's fine as long as you don't mind turrets acting like morons at times. I did some sexps for this sometime last year.

[Fury]

Has anyone else experienced that 3.6.11 r-builds won't load missions sometimes, stops at the first loading bar and then crashes to generic "has stopped responding" error while d-build loads every time? My success rate with r-build loading missions seems to be about 25%.

[Echelon9]

Do you have fs2_open.log's for these crashes? They could be problems uncovered by the safe_strings changes.

[Fury]

As you probably know, r-build does not write to fs2_open.log and as I said, d-build works fine every time.

[Echelon9]

Whoops, yeh late night posting for the loss. My bad