If an x, y, or z coordinate is more than 10m (10,000 units), the coordinates in the properties panel (N), do not give the right number #46711

Closed
opened 2015-11-06 13:40:46 +01:00 by Dimitar P. · 7 comments

System Information
Operating system and graphics card
Win 7 Enterprice

Blender Version
Broken: 2.76b

Short description of error

I work in mm for large architectural objects for seamless import/export into other programs. I have noticed a bug in which if a coordinate of an element in edit mode is more than 10m (10,000 units) in any Cartesian direction, the properties panel does not display the correct coordinate.

Exact steps for others to reproduce the error

  • Open new blank file, go to scene tab in properties, change units to "Metric", and set scale to 0.001
  • Add a plane(or any other mesh).
  • Scale it and/or move so the dimensions in either direction are more than 10m
  • With the object selected, go to edit mode, select a vertex, edge, or face that's further than 10m from the origin.
  • Open the properties panel (N), and observe the coordinates for the selected element. They should read 10m for whichever direction is further away than 10m.
  • If trying to change it to more than 10m, it stays back at 10m.
  • If clicking on the number without attempting to change and then pressing enter, Blender appears to be confused and displays 10 instead of 10000.
**System Information** Operating system and graphics card Win 7 Enterprice **Blender Version** Broken: 2.76b **Short description of error** I work in mm for large architectural objects for seamless import/export into other programs. I have noticed a bug in which if a coordinate of an element in edit mode is more than 10m (10,000 units) in any Cartesian direction, the properties panel does not display the correct coordinate. **Exact steps for others to reproduce the error** - Open new blank file, go to scene tab in properties, change units to "Metric", and set scale to 0.001 - Add a plane(or any other mesh). - Scale it and/or move so the dimensions in either direction are more than 10m - With the object selected, go to edit mode, select a vertex, edge, or face that's further than 10m from the origin. - Open the properties panel (N), and observe the coordinates for the selected element. They should read 10m for whichever direction is further away than 10m. - If trying to change it to more than 10m, it stays back at 10m. - If clicking on the number without attempting to change and then pressing enter, Blender appears to be confused and displays 10 instead of 10000.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @Dimitar

Added subscriber: @Dimitar

Added subscribers: @ideasman42, @mont29

Added subscribers: @ideasman42, @mont29
Campbell Barton was assigned by Bastien Montagne 2015-11-06 14:39:43 +01:00

The problem comes from 3DView's view3d_panel_transform which set max input values of those fields to 10000 times grid size, will let @ideasman42 decide whether this is a bit too small or not.

In the mean while, quick hack to fix this is to raise grid scale in 3DView's properties, Display panel.

The problem comes from 3DView's `view3d_panel_transform` which set max input values of those fields to 10000 times grid size, will let @ideasman42 decide whether this is a bit too small or not. In the mean while, quick hack to fix this is to raise grid scale in 3DView's properties, Display panel.
Author

Thanks. The quick fix works. Meanwhile, for myself and other architectural designers that may be working in mm, it would be great to change view3d_panel_transform to something larger, perhaps 1,000,000 times grid size.

Thanks. The quick fix works. Meanwhile, for myself and other architectural designers that may be working in mm, it would be great to change `view3d_panel_transform` to something larger, perhaps 1,000,000 times grid size.

This issue was referenced by 0024306362

This issue was referenced by 0024306362fcf8c6902366c131fc046a0da165bd

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#46711
No description provided.