problem with file and crashing ! #40894

New Issue

Ricky J · 2014-06-30T18:59:30+02:00

Ricky J commented

2014-06-30 18:59:30 +02:00

OS: window 8.1
Video : HD8670 D
AMD A10-6700 APU

Bkender version # 9337574

From Campbel comments on earlier bug report

"""

This file contains many corrupt meshes, likely created by a buggy importer.

Executing this in the py console shows problems:

for m in bpy.data.meshes: m.validate(1)

"""
thread was closed too fast
can you give a bit of time to anwser in thread!

i did run this
for m in bpy.data.meshes: m.validate(1)

but all mesh seem to be ok valid !

if not valid what does it says ?

what do u mean by buggy importer?
what is this buggy importer ?

only details i can give more is that
i only work with official installed version or the latest build !

Now for importing on win
ok i did use a lot of the system copy and paste with Ctrl-c and Ctrl V for copying one or 2 ob from one file to another file

so are you saying that this is buggy method and should not use it ?

thanks
happy blendering

OS: window 8.1 Video : HD8670 D AMD A10-6700 APU Bkender version # 9337574 From Campbel comments on earlier bug report """ This file contains many corrupt meshes, likely created by a buggy importer. Executing this in the py console shows problems: for m in bpy.data.meshes: m.validate(1) """ thread was closed too fast can you give a bit of time to anwser in thread! i did run this for m in bpy.data.meshes: m.validate(1) but all mesh seem to be ok valid ! if not valid what does it says ? what do u mean by buggy importer? what is this buggy importer ? only details i can give more is that i only work with official installed version or the latest build ! Now for importing on win ok i did use a lot of the system copy and paste with Ctrl-c and Ctrl V for copying one or 2 ob from one file to another file so are you saying that this is buggy method and should not use it ? thanks happy blendering

Ricky J commented

2014-06-30 18:59:30 +02:00

Changed status to: 'Open'

Ricky J commented

2014-06-30 18:59:30 +02:00

Added subscriber: @rickyblender

Ricky J commented

2014-06-30 19:12:06 +02:00

I did not use any import export script for these files
if that is what you mean by import thing!

now last week I did report a bug about curves crashing
and It was corrected
and hope this was included in latest 2.71 ?

but then are you saying I need to erase all curves and redo them may be?

thanks

I did not use any import export script for these files if that is what you mean by import thing! now last week I did report a bug about curves crashing and It was corrected and hope this was included in latest 2.71 ? but then are you saying I need to erase all curves and redo them may be? thanks

Sergey Sharybin commented

2014-06-30 19:30:29 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-06-30 19:30:29 +02:00

No need to start new report if your previous one was wrongly closed. Just leave comment in there and we'll see it (this doesn't apply to cases when you want to report new issue tho).

As for the importer -- it's just the most common case when mesh gets corrupted. The thing is: some of your meshes ARE corrupted, if you run the one-liner script from Cambo in the file you've attached you'll see some True in the list. True means mesh had issues which were corrected.

We can't fix crashes of files with corrupted meshes, we only could fix the way to create corrupted meshes (which is the root of the issue). But for this we'll need to know exact steps how to reproduce the buggy mesh from a non-buggy file.

As for the curves issue -- it was done after the release and is not included into the release. You can use builds from builder.blender.org.

I'm merging this report to the original one, please put all the feedback there. Once you find a steps how to reproduce corrupted mesh we'll fix it :) But for until then it's really not much we can do apart from that one-liner script which corrects your file.

No need to start new report if your previous one was wrongly closed. Just leave comment in there and we'll see it (this doesn't apply to cases when you want to report new issue tho). As for the importer -- it's just the most common case when mesh gets corrupted. The thing is: some of your meshes ARE corrupted, if you run the one-liner script from Cambo in the file you've attached you'll see some `True` in the list. `True` means mesh had issues which were corrected. We can't fix crashes of files with corrupted meshes, we only could fix the way to create corrupted meshes (which is the root of the issue). But for this we'll need to know exact steps how to reproduce the buggy mesh from a non-buggy file. As for the curves issue -- it was done after the release and is not included into the release. You can use builds from builder.blender.org. I'm merging this report to the original one, please put all the feedback there. Once you find a steps how to reproduce corrupted mesh we'll fix it :) But for until then it's really not much we can do apart from that one-liner script which corrects your file.

Sergey Sharybin commented

2014-06-30 19:31:01 +02:00

Changed status from 'Open' to: 'Duplicate'

Sergey Sharybin closed this issue

2014-06-30 19:31:01 +02:00

Sergey Sharybin commented

2014-06-30 19:31:01 +02:00

✘ Merged into #40883.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

problem with file and crashing ! #40894