Author Topic: Corona causes decimal separator problems in Max 2017  (Read 7824 times)

2016-06-10, 12:51:14

pokoy

  • Active Users
  • **
  • Posts: 1850
    • View Profile
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.

2016-06-13, 10:22:04
Reply #1

pokoy

  • Active Users
  • **
  • Posts: 1850
    • View Profile
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.

2016-06-13, 14:41:32
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12711
  • Marcin
    • View Profile
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.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2016-06-13, 14:45:55
Reply #3

pokoy

  • Active Users
  • **
  • Posts: 1850
    • View Profile
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.

2016-06-13, 17:33:24
Reply #4

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
fixed
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2016-06-13, 17:37:57
Reply #5

pokoy

  • Active Users
  • **
  • Posts: 1850
    • View Profile
Thanks - will this be a hotfix for 1.4 then? I'd rather not have to wait until 1.5.

2016-06-13, 17:54:09
Reply #6

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
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
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2016-06-13, 17:55:34
Reply #7

pokoy

  • Active Users
  • **
  • Posts: 1850
    • View Profile

2016-06-15, 17:25:46
Reply #8

PROH

  • Active Users
  • **
  • Posts: 1219
    • View Profile
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)

2016-06-15, 17:32:50
Reply #9

Matej Ovsenek

  • Active Users
  • **
  • Posts: 30
    • View Profile
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...
----------------------------------------------
matej.ovsenek - Skype
matej.ovsenek@gmail.com
https://www.facebook.com/matej.ovsenek

2016-06-16, 12:16:29
Reply #10

Alessandro

  • Active Users
  • **
  • Posts: 323
    • View Profile
    • DotLab Srl
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
« Last Edit: 2016-06-16, 14:10:56 by Alessandro »
My Ducati or a render with Corona.....mmm, hard question!

2016-06-20, 14:01:45
Reply #11

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
it will be fixed in the next daily released
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2016-06-20, 20:20:18
Reply #12

PROH

  • Active Users
  • **
  • Posts: 1219
    • View Profile
My issues seems to be fixed I 2016 with today's daily build.

Thanks :)