On 29-6-2015 11:03, Mr wrote:
> Hi, sorry but I fail to see any problem in LanuHum's images or in mine when I
> tried rendrering the scene in the official exporter. By just looking at
> the pictures, the only problem I saw was ray depth set too low. Do you mean that
> there is use of a syntax that is going to be deprecated ? I also checked the
> normals of the file, which are fine. I don't have any urge to import the mesh
> into PoseRay, though in the long run I can see it could be good to have a better
> compatibility with it. But I'm probably missing something?
>
>
The point in question was the mesh2 export result as exemplified by the 
attached image of the object as it was shown in Poseray or as rendered 
in POV-Ray.

-- 
Thomas

Post a reply to this message

Attachments:
Download 'data_vase_dec.jpg' (25 KB)

Preview of image 'data_vase_dec.jpg'

"Mr" <nomail@nomail> wrote:
> "LanuHum" <Lan### [at] yandexru> wrote:
> > clipka <ano### [at] anonymousorg> wrote:
> > >
> > > Hmm... maybe an off-by-1 error in the triangle vertex indices generated
> > > by the exporter?
> >
> > We will wait for Mr.
> > I don't see error. :(
>
> Hi, sorry but I fail to see any problem in LanuHum's images or in mine when I
> tried rendrering the scene in the official exporter. By just looking at
> the pictures, the only problem I saw was ray depth set too low. Do you mean that
> there is use of a syntax that is going to be deprecated ? I also checked the
> normals of the file, which are fine. I don't have any urge to import the mesh
> into PoseRay, though in the long run I can see it could be good to have a better
> compatibility with it. But I'm probably missing something?

Why you didn't show render result???

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?

Post a reply to this message

Attachments:
Download 'povwip27.7z.zip' (895 KB)

On 6/29/2015 8:44 PM, LanuHum wrote:
> "Mr" <nomail@nomail> wrote:
>> "LanuHum" <Lan### [at] yandexru> wrote:
>>> clipka <ano### [at] anonymousorg> wrote:
>>>>
>>>> Hmm... maybe an off-by-1 error in the triangle vertex indices generated
>>>> by the exporter?
>>>
>>> We will wait for Mr.
>>> I don't see error. :(
>>
>> Hi, sorry but I fail to see any problem in LanuHum's images or in mine when I
>> tried rendrering the scene in the official exporter. By just looking at
>> the pictures, the only problem I saw was ray depth set too low. Do you mean that
>> there is use of a syntax that is going to be deprecated ? I also checked the
>> normals of the file, which are fine. I don't have any urge to import the mesh
>> into PoseRay, though in the long run I can see it could be good to have a better
>> compatibility with it. But I'm probably missing something?
>
> Why you didn't show render result???
>
> Thomas, please check this vase in Poser.
The file renders and the vase looks fine in PovRay 3.7.
But when loading into PoseRay I get an Access Violation.
Poser will not import PovRay files

> This mesh2 was created by the official exporter.
> It is important to me to know: there is a error or not?
>


-- 

Regards
     Stephen

Post a reply to this message

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

Post a reply to this message

Attachments:
Download 'povwip27.jpg' (26 KB) Download 'povwip27_37.png' (64 KB) Download 'povwip27_uber.png' (85 KB)

Preview of image 'povwip27.jpg'

Preview of image 'povwip27_37.png'

Preview of image 'povwip27_uber.png'

Am 30.06.2015 um 09:28 schrieb Thomas de Groot:
> 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) ;

There's a simple solution to the riddle:

It's a bug (or undocumented limitation) in PoseRay.

The official syntax of the face_indices block is as follows:

   face_indices {
     number_of_faces,
     <index_a, index_b, index_c> [,texture_index [,
       texture_index, texture_index]],
     <index_d, index_e, index_f> [,texture_index [,
       texture_index, texture_index]],
     ...
   }

Apparently PoseRay stumbles over the optional texture indices.

Post a reply to this message

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

It is a victory or not?
spacing 0.005

  Trace Time:       0 hours  3 minutes 23 seconds (203.487 seconds)
              using 4 thread(s) with 797.850 CPU-seconds total
POV-Ray finished

'***POVRAY FINISHED***

Post a reply to this message

Attachments:
Download 'update_export_mesh.jpg' (74 KB)

Preview of image 'update_export_mesh.jpg'

On 30-6-2015 22:07, LanuHum wrote:
> It is a victory or not?

It certainly is! Well done!

-- 
Thomas

Post a reply to this message

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 for the report then. This looks like it would be a most profitable fix.
But I hope it is not intrinsically related to the face indices features used for
exporting multiple materials, because this was the only way to keep the Blender
centric approach of the exporter (preserving the material assigned locally to
different parts of a mesh).

Post a reply to this message

"Mr" <nomail@nomail> wrote:
>
> Thanks for the report then. This looks like it would be a most profitable fix.
> But I hope it is not intrinsically related to the face indices features used for
> exporting multiple materials, because this was the only way to keep the Blender
> centric approach of the exporter (preserving the material assigned locally to
> different parts of a mesh).

Mr! Hi!
Update my exporter.
Compare a render of this scene and that scene.
Or add to this scene a vase from there
Because of the Povray shape type enum updating can glitch.
Here a vase - mesh
Glasses - lathe
Mirror - prism
Vase there - mesh2
New object - loft.
Other - mesh2

Post a reply to this message

Attachments:
Download 'vase_mesh.7z.zip' (180 KB)