ply2vrmesh seg faults

[bhenriksson]

I get crashes when using .ply2vrmesh on a bunch of frames (but not all) in a sequence. Any takers?

Terminal output:

[bjhe@comp01 v004]$ vrm tempTrailFoamGeo_v004.0033.geo -smoothNormals
Coverter of .ply .obj .bin and .geo files to .vrmesh files
Copyright (C) 2003-2011 by Chaos Group Ltd. All rights reserved.
Build from Apr 28 2011

Converting file "tempTrailFoamGeo_v004.0033.geo"
Output file is "tempTrailFoamGeo_v004.0033.vrmesh"
Reading .geo fileGeo file format version: V5
Number of points: 328104
Number of primitives: 546840
Number of point groups: 0
Number of primitive groups: 0
Attributes info: point 0, vertex 0, primitive 0, global 0
Reading run 0 to 65535
Reading run 65535 to 131070
Reading run 131070 to 196605
Reading run 196605 to 262140
Reading run 262140 to 327675
Reading run 327675 to 393210
Reading run 393210 to 458745
Reading run 458745 to 524280
Reading run 524280 to 546840
Reading .geo file... done
Calculating vertex normals... done
Number of faces: 546840
Number of vertices: 328104
Number of texture vertices: 0
Number of vertex normals: 328104
Reading voxel... done
Subdividing voxel... done
Segmentation fault

[vlado]

Which V-Ray build is this? There was a bug with this in the official build, which was fixed since then.

Best regards,
Vlado

[bhenriksson]

Hey Vlado!

Thanks for the info. I've asked our tech department to update to latest. We're currently on version 2.00.04.

/Bjorn

[vlado]

Ok then; if you still have issues with the nightly builds, let me know.

Best regards,
Vlado

[bhenriksson]

The nightly build works fine except from some segfaults on certain bgeo's. bgeos that chrashes can be outputed to geos and then to vrmeshes. As an example, here's a bgeo and its faulty vrmesh brother.
www.bhenriksson.se/temp/threads/baseSim_surfaceWaveChrashMesh_v001.1015.bgeo
www.bhenriksson.se/temp/threads/baseSim_surfaceWaveChrashMesh_v001.1015.vrmesh

[vlado]

Thanks for the pointer; will look at this.

Best regards,
Vlado

[t.petrov]

Hi,

This bug should be fixed in the next nightly build.
Please test it and report if there are any problems with it.

/Teodor