"And" <49341109@ntnu.edu.tw> wrote:
> I downloaded a sketchup 3d model on the 3d warehouse. Last week I processed it
> to a section view, and output to povray, then rendered this picture.
>
> I put the dissection model with an original model(not cut) with "no_image" in
> the scene to give an indoor lighting, so it can..., you see
> The model itself is good.
>
> The original imagine of mine is playing small dolls in the house...

In my point of view Povray is nice to render such an image. I feel it is a good
tool. I original thought that placing a repeat object(one with syntax
"no_image") is a bad idea. I assumed it will take very long time to render. But
just... in the range that can be.


But there are some bugs in the image. Why the small wardrobe is not completely
dark, it should be black but instead it appears dark red? Because I have checked
that there is no any open or window to the outside, and the only major light
source in the scene is the sunlight and the sky_sphere light.

Post a reply to this message

Attachments:
Download 'strange point.png' (922 KB)

Preview of image 'strange point.png'

Am 11.10.2017 um 16:19 schrieb And:

> But there are some bugs in the image. Why the small wardrobe is not completely
> dark, it should be black but instead it appears dark red? Because I have checked
> that there is no any open or window to the outside, and the only major light
> source in the scene is the sunlight and the sky_sphere light.

Maybe `ambient` is to blame?

Also, radiosity sometimes leaks light in places where it shouldn't.
Careful tuning of the parameters might help.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 11.10.2017 um 15:19 schrieb And:
> > clipka <ano### [at] anonymousorg> wrote:
> >> Am 11.10.2017 um 09:53 schrieb omniverse:
> >>
> >>> I got the STL file too, and converted to OBJ then exported to POV but that won't
> >>> show the interior via CSG difference.
> >>
> >> You'll have to add an `inside_vector` statement (unless your converter
> >> software already does that for you).
> >
> >
> > So I see that it states an "inside_vector <0,0,1> "(from poseray) in the last
> > item in each mesh2 object. It does not contain sufficient information.
>
> With that statement, the mesh should work fine in CSG difference (or
> intersection or union, for that matter).
>
> Not sure what you mean by "it does not contain sufficient information".

Because there is just one vector <0,0,1> at the end, I suppose that it should
be a lot of vectors. Maybe each face have one vector, and should vary from face
to face, I don't know。。。 I suppose it should look like
that.

Post a reply to this message

Am 11.10.2017 um 16:35 schrieb And:

>>> So I see that it states an "inside_vector <0,0,1> "(from poseray) in the last
>>> item in each mesh2 object. It does not contain sufficient information.
>>
>> With that statement, the mesh should work fine in CSG difference (or
>> intersection or union, for that matter).
>>
>> Not sure what you mean by "it does not contain sufficient information".
> 
> Because there is just one vector <0,0,1> at the end, I suppose that it should
> be a lot of vectors. Maybe each face have one vector, and should vary from face
> to face, I don't know。。。 I suppose it should look like
> that.

No; there is only one `inside_vector` per mesh; it tells POV-Ray that in
order to test whether a given point is inside the mesh or not, it should
shoot a ray in the direction specified by that parameter, and count the
number of surfaces encountered in that direction. If the count is odd,
the point must be inside the mesh; if the count is even, the point must
be outside.

Post a reply to this message

One of view. 3f master suit.

Post a reply to this message

Attachments:
Download 'home scene 15 1h8m39s.png' (488 KB)

Preview of image 'home scene 15 1h8m39s.png'

> clipka <ano### [at] anonymousorg> wrote:
>> Am 11.10.2017 um 15:19 schrieb And:
>>> clipka <ano### [at] anonymousorg> wrote:
>>>> Am 11.10.2017 um 09:53 schrieb omniverse:
>>>>
>>>>> I got the STL file too, and converted to OBJ then exported to POV but that won't
>>>>> show the interior via CSG difference.
>>>>
>>>> You'll have to add an `inside_vector` statement (unless your converter
>>>> software already does that for you).
>>>
>>>
>>> So I see that it states an "inside_vector <0,0,1> "(from poseray) in the last
>>> item in each mesh2 object. It does not contain sufficient information.
>>
>> With that statement, the mesh should work fine in CSG difference (or
>> intersection or union, for that matter).
>>
>> Not sure what you mean by "it does not contain sufficient information".
> 
> Because there is just one vector <0,0,1> at the end, I suppose that it should
> be a lot of vectors. Maybe each face have one vector, and should vary from face
> to face, I don't know。。。 I suppose it should look like
> that.
> 

There is never more than a single inside_vector par mesh.
I think that, if you have several vectors, then, only the last will be 
used, each new one replacing the previous one.

You may need to slightly change it if there are triangles that are 
parallel to it. But nothing else.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 11.10.2017 um 16:35 schrieb And:
>
> >>> So I see that it states an "inside_vector <0,0,1> "(from poseray) in the last
> >>> item in each mesh2 object. It does not contain sufficient information.
> >>
> >> With that statement, the mesh should work fine in CSG difference (or
> >> intersection or union, for that matter).
> >>
> >> Not sure what you mean by "it does not contain sufficient information".
> >
> > Because there is just one vector <0,0,1> at the end, I suppose that it should
> > be a lot of vectors. Maybe each face have one vector, and should vary from face
> > to face, I don't know。。。 I suppose it should look like
> > that.
>
> No; there is only one `inside_vector` per mesh; it tells POV-Ray that in
> order to test whether a given point is inside the mesh or not, it should
> shoot a ray in the direction specified by that parameter, and count the
> number of surfaces encountered in that direction. If the count is odd,
> the point must be inside the mesh; if the count is even, the point must
> be outside.

Well, that it seems poseray adds a symbolic vector, because <0,0,1> does not
inside my model in fact. And it shouldn't get such an information because the
mesh was output from sketchup it does not contain that, moreover most of the
mesh 3d model does not have a well construct that contain a inside/ outside
distinction.

Post a reply to this message

On 11-10-2017 7:46, And wrote:
> I downloaded a sketchup 3d model on the 3d warehouse. Last week I processed it
> to a section view, and output to povray, then rendered this picture.
> 

Nice!! Didn't know the site, but I am sure to visit in future

-- 
Thomas

Post a reply to this message

On 12/10/2017 07:36, And wrote:
>> No; there is only one `inside_vector` per mesh; it tells POV-Ray that in
>> order to test whether a given point is inside the mesh or not, it should
>> shoot a ray in the direction specified by that parameter, and count the
>> number of surfaces encountered in that direction. If the count is odd,
>> the point must be inside the mesh; if the count is even, the point must
>> be outside.
> Well, that it seems poseray adds a symbolic vector, because <0,0,1> does not
> inside my model in fact. And it shouldn't get such an information because the
> mesh was output from sketchup it does not contain that,

That is probably because PoseRay was designed to create mesh2's for 
PovRay. So when things change in PovRay FlyerX updates PoseRay to 
reflect that.

> moreover most of the
> mesh 3d model does not have a well construct that contain a inside/ outside
> distinction.
> 

Which is probably because Sketchup was designed to upload content to 
Google Earth. Not to a quality renderer.
Which is not a criticism of Sketchup. It produces good results as your 
images show.

-- 

Regards
     Stephen

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
>
> Which is probably because Sketchup was designed to upload content to
> Google Earth. Not to a quality renderer.
> Which is not a criticism of Sketchup. It produces good results as your
> images show.
>
> --
>
> Regards
>      Stephen


Thomas de Groot <tho### [at] degrootorg> wrote:
> On 11-10-2017 7:46, And wrote:
> > I downloaded a sketchup 3d model on the 3d warehouse. Last week I processed it
> > to a section view, and output to povray, then rendered this picture.
> >
>
> Nice!! Didn't know the site, but I am sure to visit in future
>
> --
> Thomas



By the way, many models of 3d warehouse were made for google earth in the past.
So its models lack details. But there are still many authors upload detailed
models.

Post a reply to this message