"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "GioSeregni" <gms### [at] hotmailcom> wrote:
> > "jr" <cre### [at] gmailcom> wrote:
> > > ...hi,
> > > thank you !  if, while you're on the exporting things stuff, you could output
> > > the finish with a braced reflection[*], written eg:
> > >   finish{ambient .21 diffuse .78 reflection {.01}}
> > > then your code will be correct, and can be used with WFP's 'yuqk' branch/fork.
> > > [*] as documented
> > > <wiki.povray.org/content/Reference:Finish#Specular_Reflection>.
> >
> > I have to apologize because my English is poor and I don't understand the
> > problem.
>
> nessun problema.  (Google Translate tells me :-))
>
>
> > ...
> > My standard definition does not give me any errors or warnings by Povray, so it
> > is correct.
>
> no, alas.  no warnings/errors is the result of (what I consider) bugs in the
> POV-Ray parser.  see this example from the reference page:
>
>     finish { reflection {1.0} ambient 0 diffuse 0 }
>
> your code is missing the braces required by 'reflection'.
>
>
> > ...
> > " WFP's 'yuqk' branch/fork." sorry , what is the meaning? I cannot understand ..
> > because I don't know these abbreviations
>
> yes, sorry.  WFP = William F Pokorny, he's the author of 'yuqk', a branch/fork
> from the POV-Ray 3.8 line.  see, for example, the following thread:
>
<news.povray.org/povray.binaries.programming/thread/%3C68258118%241%40news.povray.org%3E/>
>
> (and his parser is stricter than POV-Ray's, enforcing the 'reflection {}'
> syntax)
>
>
>
> regards, jr.

Thanks, great, now I understand and I corrected the finish code.
It was simple and quick, but now I have to take a short break to fix an issue
that seems important to me.
The recognizability at first sight of each mesh object.
It will take a little time because I want to align on a new feature all my
plugins and also the executable that I use for the conversions (CAD - STL
-PovRay) of my models.
Let me explain better.
The various formats "understand" which mesh they are translating because the
finishes are defined in a common and recognizable format that begins with the
CAD drawing that assigns the layer name.
In the layer name there is the color information.
The name is in hexadecimal, because it is easy to read.
Example HEXFF0000T7F means rgb red, with alpha (Transparency) equal to 50%, 127
of 255
This system creates a database with its pointers to finishes that helps organize
the meshes and the smooth.

UDT  for my system details for a model:

TYPE Internal
 numfacets AS LONG ' 4 bytes
 Xmin AS DOUBLE
 Xmax AS DOUBLE
 Ymin AS DOUBLE
 Ymax AS DOUBLE
 Zmin AS DOUBLE
 Zmax AS DOUBLE    'END HEADER

' start bloCnt________________________ LOOP

 x0      As Double
 y0      AS Double
 z0      As Double
 x1      As Double
 y1      As Double 'vertex = 72 bytes
 z1      As Double
 x2      As Double
 y2      As Double
 z2      As Double '__________________
 LayerCo As Double    ' 8 bytes
 EntitCo As Double    ' 8 bytes
 Transp  As Double    ' 8 bytes
' end bloCnt  ________________________

'                   repeat bloCnts IN LOOP

END OF FILE

 TargetX AS DOUBLE
 TargetY AS DOUBLE
 TargetZ AS DOUBLE
 WPntX   AS DOUBLE 'view = 48 bytes
 WPntY   AS DOUBLE
 WPntZ   AS DOUBLE
 Orto    AS DOUBLE   '8 bytes


But it's a database that uses long integers (or long ) and I can't add strings
for various reasons.
So I thought of a dictionary that uses the color as an index, to remember what
kind of object it is. A parallel, textual file of specifications.
Example "shoes"
In the database HEX000000
[T00] optional, not needed here.
But in the dictionary "clean and shiny shoes".
THIS COMMENT will be in a comment label in the PovRay mesh.
It will be useful to easily customize the files.
Not only that, this reminder label, adjustable in "human" language could be used
by those who want ALSO as a prompt for the AI... which could automatically
suggest the best finish for the mesh.
It may all seem very strange, but in this way each model, with a simple label at
the end of each mesh, becomes very flexible and improvable.

Thanks aagain! see you later ...
G.

Post a reply to this message