As the title says, the numeric input fields (Pressing tab while moving, scaling, etc) doesn't read "," as "." as 1.5.4 did, this means things get moved/scaled/etc. "wrong".
Would it be possible to have Wings3D read it the same way as it did before? Being able to use the numpad greatly increases my speed, but if I can't use the numpad "," key, it's quite disruptive to my workflow.
Would it be possible to have Wings3D read it the same way as it did before? Being able to use the numpad greatly increases my speed, but if I can't use the numpad "," key, it's quite disruptive to my workflow.