Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: pokoy on 2016-06-10, 12:51:14
-
I consider this a really high priority bug that needs to be fixed as soon as possible.
This is what happens on my system:
- My OS is set to use german keyboard layout, using comma as decimal separator which never was a problem in Max
- If Corona is installed, Max 2017 will display comma as decimal separator but will not accept floating point values using a comma and expect a dot instead
- However, when using a dot, it'll first accept the value but display a comma. When leaving the numerical field, it'll re-evaluate the value and accept only the digit(s) before the comma
- Now the value will change to integer
Attached is a gif where I type in a value, leave the filed and the value gets reset to integer.
This makes it impossible to use floating point values in Max for me in the entire UI. It'll work correctly only if I uninstall Corona for Max 2017 which means I can't use Corona with 2017.
-
Bump - So there's either no interest in max 2017 or I haven't made clear that once Corona for 2017 is installed Max is unusable in comma based OS environments.
Please, we really need a fix.
-
Hey, I think your thread originates from another one started by me, where Ondra suggested that this is caused by Corona. So it is definitely acknowledged and high priority. Don't worry, I am sure our brave developers will solve this asap.
-
Hey, I think your thread originates from another one started by me, where Ondra suggested that this is caused by Corona. So it is definitely acknowledged and high priority. Don't worry, I am sure our brave developers will solve this asap.
I didn't see any bug report on this, hence the thread.
Thanks Maru, looking forward to a hotfix or something.
-
fixed
-
Thanks - will this be a hotfix for 1.4 then? I'd rather not have to wait until 1.5.
-
maybe, as more people start using 2017... but we first need to test it in daily builds to make sure there are no other problems introduced with it
-
Sounds reasonable, thanks.
-
I've just found this bug in 3dsMax2016 using Corona1,5 daily build 2016-06-12. So it's not only related to v2017.
BTW - using Windows 10 (updated from 7)
-
same problem with max 2014 here... i hate it... a lot.... i use numerical keyboard all the time and it's frustrating when settings reset to previous values...
-
Corona 1.5 Daily Jun 12 2016, same problem on Max 2017, no difficult with Max 2016.
Please find a solution asap, is impossible to work with this problem
Edit: on Windows 7 pro sp1
-
it will be fixed in the next daily released
-
My issues seems to be fixed I 2016 with today's daily build.
Thanks :)