Bug: send Backburner job with non ASCII characters...

[jens.diemer]

In the past, submitting a backburner job can't contain Non-ASCII characters. The job will not be created...

Now, with 2015 i can send a job with e.g. ß

I get a error submit error:

The most times, this submission will be ignored and no job submitted.

Sometimes the Job will be created and the ß was converted to ss but the job is broken. The manager display: There is no valid server to process job

Then i submit the same max file with job name test äöüß and then i get no submit error.

The Job is named correclty in Queue Monitor under "Show All"... But under the Server list at the bottom is displayed as :

This job works fine...

Maybe my other job results in a too long UTF16 String and this breaks something?!?

Does anybody at AD really test the develomplent?!?

[VishnuR]

Hello Jens, 

This issue seems to appear / return every once in a while.

I've gone ahead and logged this with 3ds Max engineering for you.

For now the only workaround I see is to avoid using the Non ASCII characters
​when possible and keep file names short.

Its important we log these when they pop up.

Thank you for taking the time to report this to us.

VR

[jens.diemer]

Will this be somedays fixed?!?

EDIT: This is logged 03.2015 with BSPR-19159, MAXX-22201 and after one year, nothing done?!?

[Anonymous]

Yes, this is an annoying thing. Especially as 3dsmax and backburner have localized versions this "missing ASCII-feature" doesn't make sense.

[jens.diemer · Accepted solution]

Seems that AD has enhanced the NON-ASCII Characters in backburner a little bit...

But you have to live with some "UTF16-ASCII" representation of the job name. e.g. in the server list:

This is: "testäöüß" ... But finally it render the sequence...