Crash with Stanford PLY Format import script #39883
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#39883
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
windows seven 64, ATI HD6970 Catalyst 13.12
Blender Version
Blender 2.70 19e627c
Short description of error
crash when executing import PLY file
log file: http://www.pasteall.org/51101
Exact steps for others to reproduce the error
file > import > Stanford PLY
i don't know if the file.ply is corrupted
Changed status to: 'Open'
Added subscriber: @Stony
Added subscriber: @mont29
Uh… Using coma instead of dot in floating number sounds horribly french and corrupted PLY… :P
We need that PLY file, in any case!
here is the suspicious file :>
Changed status from 'Open' to: 'Archived'
Bah… Stupid MS, they probably use locale data to write their floats, which ends to commas-separated floats, which is not and will never be and has never been a legal way to represent numbers computer-wise!
It would be easy to support this corrupted kind of ply files, but honestly, I’d rather not. This is a MS kinect stuff bug, not Blender’s, and I’m pretty sure you won’t find much programs reading that kind of file.
Note that as workaround, you can simply make a search & replace from
,
to.
on the file (it’s an ASCII text one), should work then.ok thanks ;)