News:

 

Topic: Crash on Export  (Read 10459 times)

0 Members and 1 Guest are viewing this topic.

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
April 11, 2014, 10:37:19 am


I have a particularly heavy scene that is crashing on export as .obj

754 objects,
9000 meshes

1.2m Polys

any solutions?

  • No avatar
  • Posts: 3713
  • Developer
  • Administrator
  • Polygon
April 11, 2014, 11:15:57 am
The file will be too big for my pc. But I can make debug versions for you to track down why it crashes.

How it crashed?

Select all the objects. Then object mode > Geometry > Combine(Merge Meshes). See if it can be done.

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
April 11, 2014, 11:24:23 am
Its just to much data for it to export.  I could send you the scene file if you want.  I am able to export smaller chunks...but this is less then ideal.

Merging objects will also crash.

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
April 11, 2014, 02:53:30 pm
same problem...even with a great deal deleted.  Crashes even if i try to combine meshes.

  • No avatar
  • Posts: 2102
  • Polygon
April 11, 2014, 03:33:13 pm
Hi Mason,

I am not sure what is causing the crash (only had a quick look up to now). It is not a memory problem(well, not on my setup).

The model will export in .dae
Can you use that format for now?

---------------------------------------

Having a look over the model (the objects that where not hidden), there are a lot of overlapping duplicates(some objects duplicated 2 or 3 times but are in same exact space). There are also various objects that contain 100+ meshes, but only 2 meshes that contain faces/verts

It does look like that is the root of the problem (multiple empty meshes in multiple objects), although I do not know where all(or how many) the problem objects are. I have narrowed an example file down to 21 objects that are reported to contain 993 meshes, which crashes Nvil on .obj export. I will see if I can norrow that down more before posting the example for IStonia to look at.

----------------------------------------




« Last Edit: April 11, 2014, 06:25:40 pm by steve »

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
April 11, 2014, 07:49:10 pm
yeah...just started to notice that.  Looks really ugly...wish there was a way to clean up and optimize empty Meshes/objects

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
April 11, 2014, 07:57:50 pm
Yup...i was able to isolate it to the empty meshes causing the error.  I dont know how i created the empty meshes.

Its bad enough where an object with 200 polygons might have 20 empty meshes and combining that with other objects is enough to crash Nvil.

I think we need a Scene Cleanup feature

  • No avatar
  • Posts: 2102
  • Polygon
April 11, 2014, 08:26:52 pm
Hi IStonia,

I have attached part of the file uploaded by Mason. (19 objects with 633 mesh)
When attempting to export that file as .obj, it causes overflow and Nvil crashes.

It appears the problem is due to the many empty mesh contained in the objects.

Could you please take a look when you can find time.


https://www.mediafire.com/?97stk3amm4assit


  • No avatar
  • Posts: 2102
  • Polygon
April 11, 2014, 08:33:02 pm
Hi Mason,

Yup...i was able to isolate it to the empty meshes causing the error.  I dont know how i created the empty meshes.
I have not seen empty mesh before.

Quote
I think we need a Scene Cleanup feature
Lets see if IStonia can find time to look at the problem. I am sure he will find an answer.


  • No avatar
  • Posts: 3713
  • Developer
  • Administrator
  • Polygon
April 12, 2014, 06:58:36 am
Hi IStonia,

I have attached part of the file uploaded by Mason. (19 objects with 633 mesh)
When attempting to export that file as .obj, it causes overflow and Nvil crashes.

It appears the problem is due to the many empty mesh contained in the objects.

Could you please take a look when you can find time.


https://www.mediafire.com/?97stk3amm4assit



It did not crash on me when I saved it to obj file.

  • No avatar
  • Posts: 2102
  • Polygon
April 12, 2014, 10:18:22 am
It did not crash on me when I saved it to obj file.

Looks like you need to test it on 64 bit system

I just checked with dec-23-13 build (32 bit) and that exports that example to .obj OK, but later builds that I have checked(that run as 64 bit on my setup) all crash (.net framework stack_overflow_exception)

  • No avatar
  • Posts: 3713
  • Developer
  • Administrator
  • Polygon
April 12, 2014, 11:45:10 am
I added two selection tools

object mode > Selection > Select Empty Objects.
mesh mode > Selection > Select Empty Meshes.

http://www.digitalfossils.com/Download/NVil-Apr-11-14.rar

  • No avatar
  • Posts: 2102
  • Polygon
April 12, 2014, 12:22:12 pm
Hi IStonia,

Many thanks for the new selection options.
Would it be possible, when you have time, to add those as shortcut tools, so they can be placed in a composite tool?


  • No avatar
  • Posts: 2102
  • Polygon
April 13, 2014, 03:27:58 am
Hi IStonia,

I have been looking more at this crash.
I am seeing problems(Crash -> stack_overflow_exception) when "combing" or "exporting to .obj" of more than 510 mesh.

When combing objects/mesh, for example 400 box, the display/ui disappears for a split second(not a good sign).

Also, when I attempt to import an .obj file that contains more than 512 objects (512 = interesting number), with one of the .obj import options to divide into mesh/objects, again Nvil crashes.

I am only seeing this on 64 bit version (in the earlier builds I have that run as 32 bit, those do not crash.