VRML Import has incorrect orientation #32613

Closed
opened 2012-09-20 22:42:59 +02:00 by Alan Hudson · 8 comments

%%%When importing a vrml file the correction for z up is not correct.

In the attached field the character is facing towards the positive z axis. In a vrml browser this means you see the character facing the default camera.

In order to change from yup to zup you need a 90 degree rotation along the x axis. The axis conversion code is returning something different.

You can see in the blender_before screenshot it shows the character looking down the positive Y axis, this is facing away from the default camera. In the patched version the character is oriented towards the camera.

I can see an argument that the file was originally looking down the positive z axis and now its looking down the positive y axis. But to creator of a vrml file the orientation in blender will seem wrong. Ie usually you'll see the back of objects instead of the front.

It's possible the exported global matrix would need to change to align with this. I'm still examining the output from blender to see if that suggestion makes sense.%%%

%%%When importing a vrml file the correction for z up is not correct. In the attached field the character is facing towards the positive z axis. In a vrml browser this means you see the character facing the default camera. In order to change from yup to zup you need a 90 degree rotation along the x axis. The axis conversion code is returning something different. You can see in the blender_before screenshot it shows the character looking down the positive Y axis, this is facing away from the default camera. In the patched version the character is oriented towards the camera. I can see an argument that the file was originally looking down the positive z axis and now its looking down the positive y axis. But to creator of a vrml file the orientation in blender will seem wrong. Ie usually you'll see the back of objects instead of the front. It's possible the exported global matrix would need to change to align with this. I'm still examining the output from blender to see if that suggestion makes sense.%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%Campbell, could you please check on this?%%%

%%%Campbell, could you please check on this?%%%

%%%Looked at the patch and axis_conversion() isnt acceptable, instead the patch should change the defaults for the axis_forward/up.

Moving to tracker, this isnt an urgent fix for release since the defaults can be changed an moved into a preset.
%%%

%%%Looked at the patch and axis_conversion() isnt acceptable, instead the patch should change the defaults for the axis_forward/up. Moving to tracker, this isnt an urgent fix for release since the defaults can be changed an moved into a preset. %%%

%%%Moved from Blender 2.6 Bug Tracker to Patches%%%

%%%Moved from Blender 2.6 Bug Tracker to Patches%%%
Campbell Barton removed their assignment 2016-08-11 06:37:02 +02:00

Removed subscriber: @ideasman42

Removed subscriber: @ideasman42
Member

Added subscriber: @BrendonMurphy

Added subscriber: @BrendonMurphy
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brendon Murphy self-assigned this 2017-04-15 07:18:31 +02:00
Member

closing as archived, very old task

closing as archived, very old task
Sign in to join this conversation.
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-addons#32613
No description provided.