On 09/04/2011 12:20 AM, Alain wrote:
> Then, don't use a modeler for your text but use the text primitive to
> create your individual letters. Unless a letter appears 100's times,
> you'll use much less memory, you'll save parsing and loading time, and
> the difference in render time won't be that important. Also, no faceting
> nor mesh artefacts.
>
> Anyway, the letters from those modelers are mesh objects, one mesh
> object per letter, even for a word, with duplicated letters in the word
> as several meshes.

As StephenS pointed out.
Bishop3D exports SDL code.

> Missusing union causes many "Sould have more than one
> objects in CSG".

Yes my constant companion. :-(
But a necessary evil.

> It also makes your code ugly.
>

I can't say that I agree with either you or StephenS. Machine written 
code is never elegant, from the little I've seen. So what difference 
does an extra line or two make?
Anyway it is years since we have had the coders ranting on about how 
using a SDL modeller is an affront to the very idea of Pov-Ray.



-- 
Regards
     Stephen

Post a reply to this message

Stephen wrote:

>> Missusing union causes many "Sould have more than one
>> objects in CSG".
> 
> Yes my constant companion. :-(
> But a necessary evil.

You could suggest to the Bishop3D team that unions
with one element get exported as object instead.

Post a reply to this message

On 09/04/2011 10:23 AM, Christian Froeschlin wrote:
> Stephen wrote:
>
>>> Missusing union causes many "Sould have more than one
>>> objects in CSG".
>>
>> Yes my constant companion. :-(
>> But a necessary evil.
>
> You could suggest to the Bishop3D team that unions
> with one element get exported as object instead.

I obviously did not make myself clear. Putting a single object in a 
union is a workaround because Bishop3D does not have a local axis and if 
you want to rotate the object around a point, that is the only way to do it.
If Bishop3D did as you suggest then it would break its import feature 
and import the object as fixed at the point of import.

I did, of course, suggest to the development team that a local axis 
would be useful. That was some years ago.


-- 
Regards
     Stephen

Post a reply to this message

Stephen <mcavoys_at@aoldotcom> wrote:
....
> > It also makes your code ugly.
> >
>
> I can't say that I agree with either you or StephenS. Machine written
> code is never elegant, from the little I've seen...
To be some what more complete:
I also find any SDL code with 5 to 8 indent spacing hard to read and change to 1
or 2 spacing before I continue.

Stephen S

Post a reply to this message

> On 09/04/2011 10:23 AM, Christian Froeschlin wrote:
>> Stephen wrote:
>>
>>>> Missusing union causes many "Sould have more than one
>>>> objects in CSG".
>>>
>>> Yes my constant companion. :-(
>>> But a necessary evil.
>>
>> You could suggest to the Bishop3D team that unions
>> with one element get exported as object instead.
>
> I obviously did not make myself clear. Putting a single object in a
> union is a workaround because Bishop3D does not have a local axis and if
> you want to rotate the object around a point, that is the only way to do
> it.
Not at all.
> If Bishop3D did as you suggest then it would break its import feature
> and import the object as fixed at the point of import.
>
> I did, of course, suggest to the development team that a local axis
> would be useful. That was some years ago.
>
>

POV-Ray also don't have "local" axis, only 1 set of global axis.

If the object is named, then there is NO need to use union.
Whenever you find yourself placing a single object in an union, use 
"object" instead.

If you want to place several objects around an axis at a given radius, 
then the way to do it is:

union{
  object{Object1 translate Radius rotate<x,y,z>}//Correct
  object{Object2 translate Radius rotate<x,y,z>}
...
rotate Global_Union_Rotation
translate Global_Object_Location
}

You wrongly suggers this:
union{
  union{Object1 translate Radius rotate<x,y,z>}//NOT correct
  union{Object2 translate Radius rotate<x,y,z>}
...
rotate Global_Union_Rotation
translate Global_Object_Location
}

Anyway, it's usualy beter to model all objects around the origin, scale 
and rotate them as needed, then to translate them to the desired location.
A lamp should reside with it's base at y=0.
A door with it's hinge at x=0, z=0.
A cabinet with it's back at x=0 or z=0.



Alain

Post a reply to this message

On 09/04/2011 7:57 PM, Alain wrote:

>> I obviously did not make myself clear. Putting a single object in a
>> union is a workaround because Bishop3D does not have a local axis and if
>> you want to rotate the object around a point, that is the only way to do
>> it.
> Not at all.

Not at all, what? That I not make myself clear or that it is the only 
way to do it in Bishop3D?


>
> POV-Ray also don't have "local" axis, only 1 set of global axis.
>

I'm probably using the terminology used by Moray that is confusing you.

> If the object is named, then there is NO need to use union.
> Whenever you find yourself placing a single object in an union, use
> "object" instead.
>

I take it that you've not used either Moray or Bishop3D much. In case we 
are talking at cross purposes. My last post was in reply to a suggestion 
that Christian made about Bishop3D


> You wrongly suggers this:
> union{
> union{Object1 translate Radius rotate<x,y,z>}//NOT correct
> union{Object2 translate Radius rotate<x,y,z>}
> ...
> rotate Global_Union_Rotation
> translate Global_Object_Location
> }
>

No, what I meant was this:

union {
  sphere {  // Sphere0
   0.0, 1.000000
   translate <0.0,0.0,14.0> // Radius of revolution
  }  // end Sphere0

  rotate    <0.0,27.0,0.0> /* Required rotation about the centre of 
revolution*/
  translate <-10.0,0.0,10.00> // Centre of revolution
}

> Anyway, it's usualy beter to model all objects around the origin, scale
> and rotate them as needed, then to translate them to the desired location.

Yesss, but when using a modeller you do that then leave them where they 
are and use the method I described. Moray is different as it gives you 
an extra degree of freedom and you don't need to use an extra union.


-- 
Regards
     Stephen

Post a reply to this message

> No, what I meant was this:
>
> union {
> sphere { // Sphere0
> 0.0, 1.000000
> translate <0.0,0.0,14.0> // Radius of revolution
> } // end Sphere0
>
> rotate <0.0,27.0,0.0> /* Required rotation about the centre of revolution*/
> translate <-10.0,0.0,10.00> // Centre of revolution
> }
>

This should be:
object{
  sphere {  // Sphere0
   0.0, 1.000000
   translate <0.0,0.0,14.0> // Radius of revolution
  }  // end Sphere0

  rotate    <0.0,27.0,0.0> /* Required rotation about the centre of 
revolution*/
  translate <-10.0,0.0,10.00> // Centre of revolution
}

Post a reply to this message

On 11/04/2011 5:17 PM, Alain wrote:

>
> This should be:
> object{
> sphere { // Sphere0
> 0.0, 1.000000
> translate <0.0,0.0,14.0> // Radius of revolution
> } // end Sphere0
>
> rotate <0.0,27.0,0.0> /* Required rotation about the centre of revolution*/
> translate <-10.0,0.0,10.00> // Centre of revolution
> }

Maybe it should be but it isn't.

-- 
Regards
     Stephen

Post a reply to this message

Stephen <mcavoys_at@aoldotcom> wrote:
> On 11/04/2011 5:17 PM, Alain wrote:
>
> >
> > This should be:
> > object{
> > sphere { // Sphere0
> > 0.0, 1.000000
> > translate <0.0,0.0,14.0> // Radius of revolution
> > } // end Sphere0
> >
> > rotate <0.0,27.0,0.0> /* Required rotation about the centre of revolution*/
> > translate <-10.0,0.0,10.00> // Centre of revolution
> > }
>
> Maybe it should be but it isn't.
>
> --
> Regards
>      Stephen

Thanks for all of the input. I.m going to treat each letter as an object. I'll
post the movie in the animation group along with my text scene file.

DigitalDad

Post a reply to this message

Am 09.04.2011 10:48, schrieb Stephen:

> I can't say that I agree with either you or StephenS. Machine written
> code is never elegant, from the little I've seen. So what difference
> does an extra line or two make?

Speed and memory consumption.

Using a union for a single object will add unnecessary overhead, roughly 
duplicating the memory required per letter; it also /will/ impact render 
time, if ever so slightly.

Post a reply to this message