Exporting Units Incorrectly #106334

Closed
opened 2023-03-30 20:38:22 +02:00 by Matt Barlow · 2 comments

System Information
Operating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: Mesa Intel(R) HD Graphics 520 (SKL GT2) Intel 4.6 (Core Profile) Mesa 22.2.5

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
[I have my scenes setup to metric and in millimeters scaled to 0.01 All other versions of Blender worked flawlessly with exporting my models as an STL in the correct size and units. Since the automatic upgrade to version 3.5.0 PrusaSlicer and SuperSlicer give an error that my model is in inches and not millimeters. No matter what I change the units to in the scene properties the STL comes out the exact way each time, in inches.]

Exact steps for others to reproduce the error

[Please describe the exact steps needed to reproduce the issue: I add a mesh, cylinder, and set the size to 10mm radius 2mm depth. Export the model as a STL. Import the STL into PrusaSlicer and receive an error message about the model being in inches instead of millimeters]

**System Information** Operating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.35 64 Bits Graphics card: Mesa Intel(R) HD Graphics 520 (SKL GT2) Intel 4.6 (Core Profile) Mesa 22.2.5 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** [I have my scenes setup to metric and in millimeters scaled to 0.01 All other versions of Blender worked flawlessly with exporting my models as an STL in the correct size and units. Since the automatic upgrade to version 3.5.0 PrusaSlicer and SuperSlicer give an error that my model is in inches and not millimeters. No matter what I change the units to in the scene properties the STL comes out the exact way each time, in inches.] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue: I add a mesh, cylinder, and set the size to 10mm radius 2mm depth. Export the model as a STL. Import the STL into PrusaSlicer and receive an error message about the model being in inches instead of millimeters]
Matt Barlow added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-03-30 20:38:23 +02:00

Is it same as this? https://forum.prusa3d.com/forum/prusaslicer/saved-in-inches-warning/

I have used random online print service and it reports that object is 2 x 2 x 0.2 mm when exported with both versions. This is same as stl file provided, though I don't know if this was supposed to be good or bad one.

When I tick "Scene Units" box when exporting the service reports 0 x 0 x 0 mm in both cases...

I assume you tested this on same slicer version, is that correct? Would be good to know how exactly they determine whether to use mm or inches. Do you know if this information is public?

Is it same as this? https://forum.prusa3d.com/forum/prusaslicer/saved-in-inches-warning/ I have used random online print service and it reports that object is 2 x 2 x 0.2 mm when exported with both versions. This is same as stl file provided, though I don't know if this was supposed to be good or bad one. When I tick "Scene Units" box when exporting the service reports 0 x 0 x 0 mm in both cases... I assume you tested this on same slicer version, is that correct? Would be good to know how exactly they determine whether to use mm or inches. Do you know if this information is public?
Richard Antalik added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-03-31 21:32:23 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-04-16 18:56:17 +02:00
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
2 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#106334
No description provided.