Combustion : illegal characters in file name

Hi,
Something very similar to the AE illegal characters issue a little while ago, but in Combustion instead!
An artist copying an output filename from a HTML formatted document into the render output data field in Combustion, carries over an illegal character in the Combustion output filename (but could also be in its output file path). Within the Combustion application, this is accepted, but Deadline/network “shellrenderer.exe” doesn’t work. Could we get a submission script check for this potential issue as well which also includes a message box warning highlighting the exact character issue(s) in the file/path?

Here’s the similar AE submission checking code, which it may be worth including these symbols to check against as well as the specific HTML issue I had:

var outputFolder = trim( layersDialog.outputPanel.outputFolder.text ); // \ / : * ? " < > | var fixedLayerName = currLayer.name.replace( /([\*\?\|:\"<>\/\\%£])/g, '_' ); //replace invalid path characters with an underscore

See attached zipped up file containing a HTML file for an example dodgy character in the html document.(It’s the second hyphen character, which HTML seems to convert into a dash??)

Mike
example.zip (195 Bytes)

Hey Mike,

I copied and pasted that path into a new text file using Windows Explorer, and Windows accepted it. Also, if I copy and pasted it into a text editor, both characters are identical hyphens, so we really can’t check for that second dash character. So I’m not sure what we can do about this special case…

Cheers,

  • Ryan

Thanks Ryan.
You’re right, its fine in windows ‘normally’.
Just did some more testing and its actually in the save path/browse to render output directory window within the Combustion application that the error is created when you “create” a new folder and NOT the actual file name which I was originally informed about :unamused:
It renders fine locally, but in shellrenderer.exe mode it doesn’t work.
The present ‘non existing file path’ submission checking code is catching this error so it might be best to leave it in the hands of the artist to resolve.
Mike