On 18-10-2012 20:42, Christian Froeschlin wrote:
> Vincent wrote:
>
>> and I don't think that there would be something wrong with triangles
>> (though I
>> prefer this one)becuase the STL file is generated by a 3D modeller
>> software.
>
>
> Looking a bit closer I think something is *seriously* wrong with
> your triangles
>
>   <1.35632e-019, 1.35632e-019, 1.35632e-019>,
>   <0.0147179, 0.999892, 0.000199087>,
>   <1.35632e-019, 1.35632e-019, 1.35632e-019>,
>   <0.0147179, 0.999892, 0.000199087>,
>   <0.000173748, 1.35632e-019, 3.35076e+012>,
>
> You don't want vertexs anywhere near z= e+012 ... ;)
>
> And the e-019 is also suspicious although it might just
> be a 0 with numerical errors.

What 3D modeller did you use, and what kind of model did you export to 
POV-Ray? Those answers might help a lot.

Try to model a simple object in your modeller and export it the same way 
to POV-Ray, for example a sphere or a torus. Does it show correctly in 
POV-Ray?

Thomas

Post a reply to this message

> What 3D modeller did you use, and what kind of model did you export to
> POV-Ray? Those answers might help a lot.
>
> Try to model a simple object in your modeller and export it the same way
> to POV-Ray, for example a sphere or a torus. Does it show correctly in
> POV-Ray?
>
> Thomas

The original model has been created using Finite Element method in ANSYS.  It's
a relatively complicated model. I have been given a file of it in STL format,
which  by using stl2pov I converted it to  inc format. It's a huge file (312 Mb)
including over 14E6 triangles!!I exported this inc file in povray. I need to
simulate the light reflection properties of the model has been given to me.
Really need help!!

Vincent

Post a reply to this message

On 20-10-2012 7:10, Vincent wrote:
> The original model has been created using Finite Element method in ANSYS.  It's
> a relatively complicated model. I have been given a file of it in STL format,
> which  by using stl2pov I converted it to  inc format. It's a huge file (312 Mb)
> including over 14E6 triangles!!I exported this inc file in povray. I need to
> simulate the light reflection properties of the model has been given to me.
> Really need help!!

I am not familiar with ANSYS but maybe others here are. My guess is that 
something went wrong at the conversion level or that the original object 
got corrupted. Would it be possible to convert STL to OBJ (or any other 
format supported by Poseray)? Then you could convert to POV-Ray using 
Poseray, with as bonus a mesh2 object.

Thomas

Post a reply to this message

On 20/10/12 07:10, Vincent wrote:
 > The original model has been created using Finite Element method in
 > ANSYS.  It's a relatively complicated model. I have been given a file
 > of it in STL format, which  by using stl2pov I converted it to  inc
 > format. It's a huge file (312 Mb) including over 14E6 triangles!!I
 > exported this inc file in povray. I need to simulate the light
 > reflection properties of the model has been given to me. Really need
 > help!!

   Perhaps something went wrong with stl2pov and such huge mesh... you
may want to try other paths. For example, load the STL into Blender,
export it as 3DS or OBJ and then use Poseray to convert it to POV mesh2.

-- 
Jaime

Post a reply to this message

If all of this doesn't help, why don't you try Poseray to convert your scene to
POV format? I presume your mesh was originally an .obj

Post a reply to this message

"Tjeb" <se.### [at] wolmailnl> wrote:
> If all of this doesn't help, why don't you try Poseray to convert your scene to
> POV format? I presume your mesh was originally an .obj


My guess is that something went wrong at the conversion level or that the
original object got corrupted. Would it be possible to convert STL to OBJ (or
any other format supported by Poseray)? Then you could convert to POV-Ray using
Poseray, with as bonus a mesh2 object.
Thomas

Perhaps something went wrong with stl2pov and such huge mesh... you may want to
try other paths. For example, load the STL into Blender, export it as 3DS or OBJ
and then use Poseray to convert it to POV mesh2.
Jaime


number of triangles is correct, also at the end of .inc file I can see the
statement : }//end of mesh.
And my mesh originally was in .nas format. But have been told that it is just a
sort of STL format.
But as you, Jaime and Thomas are suggesting I have to try other paths, for

preview.

Vincent

Post a reply to this message

On 21-10-2012 1:30, Vincent wrote:

> number of triangles is correct, also at the end of .inc file I can see the
> statement : }//end of mesh.
> And my mesh originally was in .nas format. But have been told that it is just a
> sort of STL format.
> But as you, Jaime and Thomas are suggesting I have to try other paths, for

> preview.

I don't want to nitpick but I have the feeling that your object is 
corrupt, despite the correct number of triangles. The fact alone, as 
Alain also mentioned, that [quote] Your range of values going from 1e-19 
to 1e12 is extreme with a variation of 31 orders of magnitude [/quote] 
makes me think that all is not well.

Thomas

Post a reply to this message

On 10/21/2012 12:07 AM, Thomas de Groot wrote:
> On 21-10-2012 1:30, Vincent wrote:

>> because the
>> number of triangles is correct, also at the end of .inc file I can see
>> the
>> statement : }//end of mesh.
>> And my mesh originally was in .nas format. But have been told that it
>> is just a
>> sort of STL format.
>> But as you, Jaime and Thomas are suggesting I have to try other paths,
>> for

>> give me a
>> preview.
>
> I don't want to nitpick but I have the feeling that your object is
> corrupt, despite the correct number of triangles. The fact alone, as
> Alain also mentioned, that [quote] Your range of values going from 1e-19
> to 1e12 is extreme with a variation of 31 orders of magnitude [/quote]
> makes me think that all is not well.
>
> Thomas
>
Yeah. Its possible for things to go very odd sometimes in a design. Last 
one I had to redo from scratch (not just due to the glitch, but because 
I didn't think the design through very well). It seems, some place in 
the process I deleted, or connected, something wrong and got what I call 
"ghosts". Sides, or faces, which don't connect how they are supposed to, 
and produce non-solid surfaces. The result exported to cae, which I was 
trying to use to import to Second Life, but nothing, not SL, or Blender, 
or even the program that exported it in the first place, would load the 
thing. Most just failed without an error. Second Life said something 
about a value being wrong, or something, when it failed.

Unfortunately, finding these problems, never mind fixing them, in the 
programs that create the meshes, is usually totally impossible. :( 
Maybe, something that let you handle "discrete" points, like Rhinoceros, 
could do it, but most can't handle those, let alone say, curved, without 
at least a single "face". Some won't even allow single faces, and 
instead require solids. So, when you accidentally mangle one of those 
solids, its impossible to correct the problem. Sometimes those things 
will also mess with the exporter, or even, as in my case, create a 
seemingly valid export, which just flat won't import into anything at all.

Post a reply to this message

Guys, many thanks for catching my error. The problem is not solved yet but now I
am more confident that the converted file is corrupt. Working on it!

Best regards,

Behrooz

Post a reply to this message

"Vincent" <nomail@nomail> wrote:
And here is the solution:

As you mentioned there was an error in file converting. Actually, my file with
..nas extension was not a kind of STL format! It was generated by NASTRAN. So, at
first I converted it to the STL using Gmsh. Then using MeshLab i converted it to
OBJ. And now it could be opened (beautifully) using Poseray. without any error.

Thanks to all again.

Post a reply to this message