VRML import issues #45195
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#45195
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
OS X 10.9 on MacBook Pro 13 (Intel Iris graphics)
Blender Version
Broken: 2.74 (2015-Mar-31)
Problems importing VRML files generated by the popular chemistry tool JMol
Exact steps for others to reproduce the error
First problem:
1.) Start with the default empty project
2.) Try to import test.wrl.
3.) Obtain no error message, but also no imported objects. Viewing the file with e.g. "view3dscene" gives the correct result and no warnings.
Changed status to: 'Open'
Added subscriber: @mpik
Added subscriber: @Blendify
Added subscriber: @mont29
First of all, please do not report several issue in a single thread, we want one report per issue (much easier to handle).
Split this one in two (#45203).
VRML and X3D import issuesto VRML import issuesThis issue was referenced by
7051ad3028
Issue is with long lines like this one:
Current code would end up reading whole
translation 1.262 1.293 .184 children DEF _0 Shape
at once and miss the new child node defined at the end.For now, solution is to separate each property (field in vrml slang) on a single line during our pre-process step. That way, fields implying a new node or more (like
children
one) are correctly handled, even if they do not explicitly have their- [ ]
braces (this is valid vrml syntax, ifMFNode
field has a single node,- [ ]
are not mandatory…).Changed status from 'Open' to: 'Resolved'