Cannot import PLY file generated by Rhinos3D 6.0 #78278
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#78278
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
Operating system: Ubuntu 18
Graphics card: Integrated Intel
Blender Version
Broken: 2.79b
Short description of error
Blender can not open a PLY file exported from Rhinos 6.0. Here the file: https://github.com/cnr-isti-vclab/meshlab/files/3330082/Box.ply.zip
When run through console, it reports:
I checked with a hex editor, and the end_header line is there. Maybe there is a problem with carriage return vs newline?
Exact steps for others to reproduce the error
Open Blender from a terminal/console. Import into Blender the file linked above. Check the output in the terminal.
Related:
https://github.com/cnr-isti-vclab/meshlab/issues/463
https://github.com/google/draco/issues/613
Added subscriber: @ferdymercury
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Confirmed'
Will confirm for now, apparently there is an issue with line termination, yes.
Not sure if it is against the specs, but using
line in plyf
[plyf is open(filepath, 'rb')] will not separate lines properly.Tried using
plyf.read().splitlines()
- that separates them properly - but has issues later on.Needs more investigation...
Thanks. In case it helps, Meshlab uses the following chars as possible separators:
" \t\n\r"
a8e87662b6/wrap/ply/plylib.cpp (L987)
Added subscriber: @jesterking
FWIW: current stable version of Rhino is v6 (SR 27 I believe).
Importing the PLY file into Rhino v6, then re-exporting as PLY, then importing in Blender works just fine. Also an export from a clean Rhino file (with just that a box) work just fine.
Even a complex model exported as PLY with Rhino 6 imports fine in Blender (2.83.1)
box_v6.ply
box_from_v3_reexported.ply
Thanks. The files you provided are in ASCII format, whereas the original one is in binary format. Can you see if you can select the export option as binary in 6? Otherwise we do not know if the bug is still there in 6.0. Thanks!
Right, binary format indeed fails.
Upon a bit further inspection it turns out the PLY file you provided is exported with Rhino 6.
So binary PLY also fails in 2.83.1
Added subscriber: @rjg
This comment was removed by @rjg
Cannot import PLY file generated by Rhinos 3.0to Cannot import PLY file generated by Rhinos 6.0Cannot import PLY file generated by Rhinos 6.0to Cannot import PLY file generated by Rhinos3D 6.0Thanks Nathan. Sorry, I had a mind shortcut and transformed Rhinos3D 6.0 to Rhinos 3.0. Indeed, it is Rhinos 6.0 the original file.
Concerning line endings:
https://www.graphics.rwth-aachen.de/media/openmesh_static/Documentations/OpenMesh-5.2-Documentation/a00002.html
https://github.com/PointCloudLibrary/pcl/issues/1256
https://github.com/dranjan/python-plyfile
Added subscriber: @mont29
Boils down to python expecting only
\n
as newline char in binary files... Truing to work around the issue currently, but it's a bit tricky :|Note that it would fail as well with a text version of it if it was not using
\n
as return char.This issue was referenced by
04c0573ee7
Changed status from 'Confirmed' to: 'Resolved'