Page 1 of 1
max 2013 scripting in Chinese?
Posted: Thu Jun 21, 2012 4:37 am
by egmehl
I'm running a script that worked in 2012 but now Max complained that it couldn't find gsRenderTime in the renderer parameters. I did a "show renderers.current" to see if there were changes to the variable names, and all of them came out in another language (Chinese maybe, I can't really say). It seems like all renderer related parameters are not accessible right now?
Is this a Max setting or a plugin thing?
Here's a screen shot of part of the output:
thanks
- Eric
Re: max 2013 scripting in Chinese?
Posted: Thu Jun 21, 2012 9:17 am
by Mihnea Balta
Oh, sorry about that, it will be fixed soon. Max 2013 switched everything to Unicode and apparently we've missed a few places where we have to take care about the character set.
Re: max 2013 scripting in Chinese?
Posted: Sun Jun 24, 2012 7:28 pm
by egmehl
Do you know about when the fix will be released? My export scripts and some others don't work until then.
Thanks
Re: max 2013 scripting in Chinese?
Posted: Mon Jun 25, 2012 7:18 pm
by j_man
This is also happening in the "Geographical Location" on the render dialog.
J.
Re: max 2013 scripting in Chinese?
Posted: Sun Apr 07, 2013 11:54 pm
by LEM
I am having the same "chinese" messages everywhere in renderkit .
It is impossible to use the mesher, as I don't even understand what it is saying
the error message.I use Max 2013.
also just instaled the most recent plugin for Maxwell in 3ds Max 2013.
And if I use particles , renders with inverted axis in the Active Shade viewport.
the bug It is still there, dozens of plugins and no fix !!!
It is very annoying for a Render as good as Maxwell.It is not a Beta right ?
Re: max 2013 scripting in Chinese?
Posted: Mon Apr 08, 2013 8:25 am
by Mihnea Balta
Which object is causing this issue exactly? Could you show me a screenshot from Max with the Chinese text?
Re: max 2013 scripting in Chinese?
Posted: Thu May 02, 2013 6:50 am
by LEM
had exactly the same problem.
comented with Luis Miguel .
I think the team is aware of the problem already.