3ds Max 2013 mixed interface language Backburner Problem

[Bechstein]

Hi!

I faced with a problem occurred in mixed interface language environment in our firm. The render server and the most of the workstations use English language in 3ds max 2013. One 3d artist work in German language. If this workstation send an render job to backburner no image will be saved. No error massage is given all the English workstations continuous the render process but don't save any images. This only occurs if the vray framebuffer is used to save the rendered image. With the max framebuffer all is fine. If i send a render job from a English language max the German one is the only one who not save the images.


Our Setup:

3ds max 2013 64bit (pu05)
VRay 2.30.01 64bit

Renderserver: max with English interface + Backburner manager + Backburner server
Workstation one: max with German interface + Backburner server
Workstation two:max with English interface + Backburner server

It seems that the language in the max which saved the max file ist the point. You save it under a German interface language only German interface render clients save the rendered image and vice versa.

Is it a known problem?


Thanks for helping!
Axel

[vlado]

Thanks for the pointer; will try to reproduce this here.

Best regards,
Vlado

[windowlicker]

I think the problem might be in the actual backburner. Since we updated to 2013 we've noticed a lot of problems when using Swedish characters (åäö) in scene names, camera names and output files. We'll try to revert to 2012 as soon as it is possible and see if that helps. Can't recall ever having this problem with any of the earlier BB versions.

[Bechstein]

@windowlicker:
but when i use the 3ds max framebuffer everything is fine. so the backburner is not the problem.

@vlado
could you reproduce this issue?

[vlado]

Yes, we could reproduce the issue and we are working on a fix.

Best regards,
Vlado

[Bechstein]

Good news! As always i like the fast and direct support ... Thanks for that!

[Bechstein]

Hi Vlado!

Is this fixed in the latest official build? (2.40.01)


Best regards,
Axel

[alexander.kazandzhiev]

Hi Axel,

We have found a way to work around it. The fix will be present on the next Monday, in the official build and the nightbuilds too.

Best regards,
Aleksandar

[Bechstein]

Thanks!

Best regards,
Axel