POV-Ray : Newsgroups : povray.binaries.images : WIP: We check the union Blender - Povray : Re: WIP: We check the union Blender - Povray Server Time
17 May 2024 20:26:44 EDT (-0400)
  Re: WIP: We check the union Blender - Povray  
From: LanuHum
Date: 30 Jun 2015 14:00:00
Message: <web.5592d8a9b92297fd7a3e03fe0@news.povray.org>
Thomas de Groot <tho### [at] degrootorg> wrote:
> On 29-6-2015 21:44, LanuHum wrote:
>
> > Thomas, please check this vase in Poser.
> > This mesh2 was created by the official exporter.
> > It is important to me to know: there is a error or not?
> >
>
> Now, this is an interesting conundrum.
>
> The mesh2 geometry obviously seems corrupt when loaded in *Poseray*
> (image povwip27.jpg).
>
> However, it seems to render correctly, although extremely slow when
> rendered in *UberPOV* (image povwip27_uber.png) ;
>
> and a bit faster in *official POV-Ray* version  (image povwip27_37.png).
>
> To speed things a bit up, I switched photons off.
>
> My guess is that the export is not really correct because the vase which
> was made from an obj version rendered fast, also with photons. So, the
> official exporter needs to be looked into.
>
> --
> Thomas

Thanks!

I am inclined to consider that the error in the official exporter is.
If in a scene of lathe and mesh2, the created Povray (meshmaker), caustics from
objects have identical intensity and uniformity at spacing 0.01.
But, if mesh2 creates blendpov, caustics from lathe and from mesh2 have
different intensity and dances with a tambourine demand.
On the weekend I will try to take it a error.
If the obj file gives a correct idea, to the obj exporter can give the answer.
obj doesn't take a normal from vertices.
obj calculate normal split.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.