Blender Importer Up axis selector's Y Up options when selected sets it to X Up #43243

Closed
opened 2015-01-13 22:31:48 +01:00 by guategeek · 16 comments
guategeek commented 2015-01-13 22:31:48 +01:00 (Migrated from localhost:3001)

System Information
Windows 8.1, GTX 570

Blender Version
Broken: 2.73 b4d8fb5

Short description of error
When I tried importing and FBX or OBJ file in blender and I want to change the Up axis of the file when I select the "Z Up" option it changes to "X Up", Likewise with "-Z UP" it changes to "-X Up"

Exact steps for others to reproduce the error
Open Blender.
Select File/Import/OBJ (or FBX, is probably broken with all importers I have only tested these 2)
In the import screen select and OBJ or FBX file, and chose the UP: options of ether "Z Up" or "-Z Up" you will immediately find blender has selected "X Up" or "-X Up"

**System Information** Windows 8.1, GTX 570 **Blender Version** Broken: 2.73 b4d8fb5 **Short description of error** When I tried importing and FBX or OBJ file in blender and I want to change the Up axis of the file when I select the "Z Up" option it changes to "X Up", Likewise with "-Z UP" it changes to "-X Up" **Exact steps for others to reproduce the error** Open Blender. Select File/Import/OBJ (or FBX, is probably broken with all importers I have only tested these 2) In the import screen select and OBJ or FBX file, and chose the UP: options of ether "Z Up" or "-Z Up" you will immediately find blender has selected "X Up" or "-X Up"
guategeek commented 2015-01-13 22:31:48 +01:00 (Migrated from localhost:3001)
Author

Changed status to: 'Open'

Changed status to: 'Open'
guategeek commented 2015-01-13 22:31:48 +01:00 (Migrated from localhost:3001)
Author

Added subscriber: @guategeek

Added subscriber: @guategeek

Added subscribers: @JulianEisel, @Sergey

Added subscribers: @JulianEisel, @Sergey

That is indeed weird.

@JulianEisel, mind having a look? :)

That is indeed weird. @JulianEisel, mind having a look? :)
guategeek commented 2015-01-13 22:44:30 +01:00 (Migrated from localhost:3001)
Author

Doh I'm an idiot, didn't notice that Z Forward was selected so when I selected Z Up it just would jump back to X Up.

Would be less confusing if you could select Z Up and blender would change Z Forward to another value.

The opposite seems to work, For example lets say Its set to:
Z Forward
X Up

If I change "Z Forward" to "X Forward", blender automatically changes the "X Up" Value to one of the other two options.

Doh I'm an idiot, didn't notice that Z Forward was selected so when I selected Z Up it just would jump back to X Up. Would be less confusing if you could select Z Up and blender would change Z Forward to another value. The opposite seems to work, For example lets say Its set to: Z Forward X Up If I change "Z Forward" to "X Forward", blender automatically changes the "X Up" Value to one of the other two options.

@guategeek, yes there's indeed some degree of confusion here. Worth checking for usability improvements here.

@guategeek, yes there's indeed some degree of confusion here. Worth checking for usability improvements here.
Member

So you mean everything works as you'd expect it now?
We could make this change automatically, just as you suggested, but we normally try to avoid such things so it would be really inconsistent on how Blender normally works

So you mean everything works as you'd expect it now? We could make this change automatically, just as you suggested, but we normally try to avoid such things so it would be really inconsistent on how Blender normally works

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2015-01-13 23:59:23 +01:00

Do not see how we could improve this, you can't have same axis for both up and forward, and you cannot make two props update on each other (leads too easily to infinite recursion…).

Anyway, definitively not a bug, you get same behavior in constraints using axes e.g.

Do not see how we could improve this, you can't have same axis for both up and forward, and you cannot make two props update on each other (leads too easily to infinite recursion…). Anyway, definitively not a bug, you get same behavior in constraints using axes e.g.
guategeek commented 2015-01-14 02:09:56 +01:00 (Migrated from localhost:3001)
Author

Ok thanks for the info, and sorry about the mistake on the bug report. UI wise it would be great if the option that's already selected for the forward axis is grayed out in the up axis.

Ok thanks for the info, and sorry about the mistake on the bug report. UI wise it would be great if the option that's already selected for the forward axis is grayed out in the up axis.

Added subscriber: @mont29

Added subscriber: @mont29

@mont29, first ever idea which comes to mind is to let setting whatever value you want to any of those menus and tweak value in unchanged menu to keep orientation consistent. That way you are not forced to use specific order of modifying the settings.

@mont29, first ever idea which comes to mind is to let setting whatever value you want to any of those menus and tweak value in unchanged menu to keep orientation consistent. That way you are not forced to use specific order of modifying the settings.

@Sergey and how would you tweak other setting in a good way? How to choose among the four remaining possible values? Or do we just accept to select first available (possible) value?

Also, constraints & co just let people select whatever axes they want, and go in 'invalid red' status if settings are incompatible… :/

@Sergey and how would you tweak other setting in a good way? How to choose among the four remaining possible values? Or do we just accept to select first available (possible) value? Also, constraints & co just let people select whatever axes they want, and go in 'invalid red' status if settings are incompatible… :/

Mwua. What's wrong with setting first option which doesn't lead to conflicts? That way you're not ending up with setup which doesn't make sense and still don't restrict options set order.

Mwua. What's wrong with setting first option which doesn't lead to conflicts? That way you're not ending up with setup which doesn't make sense and still don't restrict options set order.

Done.

Done.

Changed status from 'Archived' to: 'Resolved'

Changed status from 'Archived' 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#43243
No description provided.