Most of the V-Ray specific number input boxes don't accept my decimal seperator, or numbers after the decimal seperator

V-Ray for 3ds Max V-Ray for 3ds Max :: Issues
1

EDIT:

So the problem is a lot worse than I thought. The problem I describe below is actually valid for most of the number input dialogues that are V-Ray. So this applies to numbers in material settings, modifiers, render settings,…

I tested a couple of input boxes from VrayDisplacemenMod, some work, some don’t. I tested some numbers in a VrayLight, and for instance the multiplier input has the same problem. I’m not going to test further because I have work to do, but I’m using latest Vray on latest 3dsMax. This is extremely annoying and I would appreciate a quick fix.

In the VFB when I try to type for instance 0.5 in in any number input that takes these values, the . is not registered. So I would type 05 instead. If I try to change a number that already has this dot. For instance 0.000, and I select the decimal digits 000, it doesn’t allow me to type after the dot. This is not an issue with regular text boxes.

FYI my decimal symbol in Language > Number format in Windows (11 Pro - 25H2) is set to a dot. This is a lot easier for me as 3dsMax takes a dot as decimal separator. I did not have issues before that except for that the VFB doesn’t take -.5 for instance it requires me to type -0.5 completely, this was an issue that was introduced a couple of years ago that I already reported, because before that it worked. But now it doesn’t even take the dot anymore.

Edit: I was talking about this issue: Numeric input field VFB - #2 by vladimir_krastev

This is still not resolved by the way.

2

@hermit.crab Sorry to tag you but I’ve edited my post and title because it’s a lot worse, something must have changed in the way V-Ray accepts floating numbers and its decimal seperators.

3

This works fine on my end. I also use a dot as a decimal separator. Also using Win 11 Pro 25H2.

As I just confirmed, it indeed depends on the Windows Regional settings, so I would take a second look there.

EDIT: By the way, check your active language, because that also affects it. Works fine with English (United States). Bulgarian, for example, seems to override the numlock dot with a comma.

4

I checked on both my workstations and issue is on both. They are set up with Windows Display Language set to English (Belgium). Keyboard is Belgian (Period) - AZERTY (yeah I know we use French keyboards in Belgium).

I did not have issues before the latest update, except for the .5 without a leading zero, untill now. No other software has this issue so something must have changed.

I’m going to install English (US) as default language and see what that does.

5

Ok installed English (US) as default language but with Belgian Keyboard and that fixes everything also the older bug with omitting the zero. Thanks Aleksandar. Bit weird that language messes with the units, but whattayagonnado.