Vertex Transformation, Number Rounding Problem, versions 2.79 and above! #61298

New Issue

Somebody · 2019-02-07T23:17:19+01:00

Somebody commented

2019-02-07 23:17:19 +01:00

System Information
Operating system: Windows 7 x64 Ultimate SP1
Graphics card: onboard Intel HD 4600

Blender Version
Broken:
2.79 (latest) AND 2.80 latest beta

Worked: (optional)
2.77a works correctly!

Short description of error

This problem is happening on blender versions 2.79 and 2.80! It is NOT present in 2.77a.
How to replicate: Selecting a vertex and clicking on its axis transformation on the right pane (N), for example on the Y-axis, enter the number 47.15426 for example.
So far, so good. But after clicking on that same field again (to edit or just copy the value to the clipboard), it gets automatically rounded off (just by clicking on it) to 47.1543 for no reason.
Basically, when I want to select the coordinate of that vertex (47.15426 is its correct value) and just copy it to my clipboard so I can paste it into another program, that number gets changed automatically to 47.1543 inside Blender and it stays that way after de-selecting the Y-axis number field in the Transformation tab!

In 2.77a version, no such thing can happen, I have been using it since 2016 and there weren't any problems with that.
I have tested both the 32-bit and 64-bit versions of the affected 2.79 and 2.80 releases, all have this issue.

Exact steps for others to reproduce the error
Open the attached .blend file: vertex_coordinate_rounding_problem.blend
The vertex is already selected. Just navigate with your mouse to the Y: axis transformation and click on the field with the number. It will change from 47.15426 to 47.1543 (which literally lowers the precision of the float by a decimal point). If you try that in Blender 2.77a, this will not happen.

**System Information** Operating system: Windows 7 x64 Ultimate SP1 Graphics card: onboard Intel HD 4600 **Blender Version** Broken: 2.79 (latest) AND 2.80 latest beta Worked: (optional) 2.77a works correctly! **Short description of error** This problem is happening on blender versions 2.79 and 2.80! It is NOT present in 2.77a. How to replicate: Selecting a vertex and clicking on its axis transformation on the right pane (N), for example on the Y-axis, enter the number 47.15426 for example. So far, so good. But after clicking on that same field again (to edit or just copy the value to the clipboard), it gets automatically rounded off (just by clicking on it) to 47.1543 for no reason. Basically, when I want to select the coordinate of that vertex (47.15426 is its correct value) and just copy it to my clipboard so I can paste it into another program, that number gets changed automatically to 47.1543 inside Blender and it stays that way after de-selecting the Y-axis number field in the Transformation tab! In 2.77a version, no such thing can happen, I have been using it since 2016 and there weren't any problems with that. I have tested both the 32-bit and 64-bit versions of the affected 2.79 and 2.80 releases, all have this issue. **Exact steps for others to reproduce the error** Open the attached .blend file: [vertex_coordinate_rounding_problem.blend](https://archive.blender.org/developer/F6542977/vertex_coordinate_rounding_problem.blend) The vertex is already selected. Just navigate with your mouse to the Y: axis transformation and click on the field with the number. It will change from 47.15426 to 47.1543 (which literally lowers the precision of the float by a decimal point). If you try that in Blender 2.77a, this will not happen.

Somebody commented

2019-02-07 23:17:19 +01:00

Added subscriber: @trashcontainer

blender-admin commented

2019-02-07 23:17:19 +01:00

This issue was referenced by blender/blender-staging@dc6fcb8ecf

This issue was referenced by blender/blender-staging@dc6fcb8ecff41e61fbf31462b068b2ec790760d4

Marcin Zawiejski commented

2019-02-08 14:19:00 +01:00

Added subscriber: @DragMZ

Marcin Zawiejski commented

2019-02-08 14:19:00 +01:00

The reason for this is: UI/floats: Reduce our UI_PRECISION_FLOAT_MAX by one to avoid most rounding issues. used in interface_handlers.c:3052:

ui_but_string_get_ex(but, data->str, data->maxlen, UI_PRECISION_FLOAT_MAX, true, &no_zero_strip);

The reason for this is: [UI/floats: Reduce our UI_PRECISION_FLOAT_MAX by one to avoid most rounding issues. ](https://developer.blender.org/rBSdc6fcb8ecff41e61fbf31462b068b2ec790760d4) used in interface_handlers.c:3052: ``` ui_but_string_get_ex(but, data->str, data->maxlen, UI_PRECISION_FLOAT_MAX, true, &no_zero_strip); ```

Sebastian Parborg commented

2019-02-08 14:44:17 +01:00

Added subscribers: @mont29, @ZedDB

Sebastian Parborg commented

2019-02-08 14:44:17 +01:00

@mont29 is there anything to do here as this seems to be a intended change?

Somebody commented

2019-02-08 16:05:55 +01:00

What was the reasoning for this? Version 2.77 didn't do that, what prompted the change?
Me, personally, I'd be thrilled to have an option to turn that feature off, I don't want it to round off things on its own.
Maybe put it as an option (toggleable on/off) for people who want to round off their vertex coordinates by X amount of decimals?

What was the reasoning for this? Version 2.77 didn't do that, what prompted the change? Me, personally, I'd be thrilled to have an option to turn that feature off, I don't want it to round off things on its own. Maybe put it as an option (toggleable on/off) for people who want to round off their vertex coordinates by X amount of decimals?

Bastien Montagne self-assigned this 2019-02-08 19:40:54 +01:00

Bastien Montagne commented

2019-02-08 19:40:54 +01:00

Issue is due to bug in code generating string for edited numeric button. Tried a quick fix, but there are actually more issues in our handling of float precision in UI code, so will check further to properly unify/fix the whole mess.

Somebody commented

2019-02-08 20:52:34 +01:00

Edit: Any ETA on a fix for this?

Somebody commented

2019-07-02 16:43:37 +02:00

Any news on whether this has been fixed?

Bastien Montagne was unassigned by Dalai Felinto

2019-12-23 16:35:14 +01:00

Richard Antalik commented

2020-01-23 22:37:23 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-01-23 22:37:23 +01:00

Changed status from 'Confirmed' to: 'Needs User Info'

Richard Antalik commented

2020-01-23 22:37:23 +01:00

I have re-triaged this report and can not reproduce it.
Can you please check if this is still an issue in latest build?
https://builder.blender.org/download/

I have re-triaged this report and can not reproduce it. Can you please check if this is still an issue in latest build? https://builder.blender.org/download/

Somebody commented

2020-01-25 21:07:41 +01:00

@iss Just tested on 2.81.16

For testing, I used the OP posted value of X: 47.15426 for a vertex on a starting box.
Here is what happens - the value is now correctly written in the coordinate field menu (N), but it rounds up to 47.1543 when you select the value in the Transform Vertex menu.

What needs to change (in my opinion) is that this rounding up is not needed (there is simply no reason for a value to change just because you selected the numbers in the N vertex transform menu).

After the value changes, if you hit ESC, it will revert back to the correct 47.15426. But if you de-select the field with the auto-changed value (when you select it, it goes from 47.15426 to 47.1543) then it will remain 47.1543, which essentialy moves your vertex for no apparent reason. This became an issue since blender 2.78 up to this day with the newest versions. Last known version that doesn't have this is 2.77a

Hope you guys can make it so that this auto-switching with values just stops happening, thanks for your hard work!

P.S this happens in 2.82 Alpha too

@iss Just tested on 2.81.16 For testing, I used the OP posted value of X: 47.15426 for a vertex on a starting box. Here is what happens - the value is now correctly written in the coordinate field menu (N), but it rounds up to 47.1543 when you select the value in the Transform Vertex menu. What needs to change (in my opinion) is that this rounding up is not needed (there is simply no reason for a value to change just because you selected the numbers in the N vertex transform menu). After the value changes, if you hit ESC, it will revert back to the correct 47.15426. But if you de-select the field with the auto-changed value (when you select it, it goes from 47.15426 to 47.1543) then it will remain 47.1543, which essentialy moves your vertex for no apparent reason. This became an issue since blender 2.78 up to this day with the newest versions. Last known version that doesn't have this is 2.77a Hope you guys can make it so that this auto-switching with values just stops happening, thanks for your hard work! P.S this happens in 2.82 Alpha too

Richard Antalik commented

2020-01-25 21:34:12 +01:00

Changed status from 'Needs User Info' to: 'Confirmed'

Harley Acheson commented

2020-01-26 00:36:06 +01:00

Added subscriber: @Harley

Harley Acheson commented

2020-01-26 00:36:06 +01:00

Isn’t 6 digits of precision exactly what is expected from our floats? Put in a number with 6 digits of precision or less and get the exact number out. Try using more precision and you will lose some.

Somebody commented

2020-01-26 11:07:38 +01:00

@Harley the issue is not with the 6-digits of precision, it's with the interface code that "rounds up" just because you selected that field (you manually input something, hit enter - its correct, but if you then select the same field you did the manual input to, it rounds up and you have to hit ESC or else the vertex will move to the rounded up value)

Somebody commented

2020-02-25 18:53:40 +01:00

Hi guys, any chance this gets patched in for the 2.83 final release? Thanks, hope it's not too much work to get that resolved

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Vertex Transformation, Number Rounding Problem, versions 2.79 and above! #61298