 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres <jai### [at] ignorancia org> wrote:
> On Sat, 1 Mar 2003 15:49:27 +0000
> kav### [at] delete_thisfocalimagecom (Kaveh) wrote:
>
> > I just downloaded all those and saw that. It is *exactly* what I need.
>
> Nice! And don't forget to show us the results!
>
> > And congratulations for doing so much work on color. It's not an easy
> > field!
>
> Yeah... but here all the merit goes to Ive, who done the hard work
> researching and implementing color transformations. I'm still learning
> and trying to understand it all, but I know already enough to see that
> there are plenty of potential applications for CIE.inc.
>
> > I am probably doing something silly here, but when I run your test
> > file:
>
> Oh! No! You used the non-tested example on the readme! :)
>
> > I get an error:
[...]
I had a file directory problem, now solved.
The Wavelength() macro works and I am very happy. Now when I send a ray
through a system (in conventional optical 'forward' ray tracing), not
only are the angles calculated in povray, but the ray has the correct
color. :-)
--
Kaveh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 3 Mar 2003 00:38:39 +0000
kav### [at] delete_thisfocalimagecom (Kaveh) wrote:
>
> I had a file directory problem, now solved.
Which was exactly the problem? I'm about to install POV on a eMac with
Mac OS X, and it will be nice to be aware of it...
> The Wavelength() macro works and I am very happy. Now when I send a
> ray through a system (in conventional optical 'forward' ray tracing),
> not only are the angles calculated in povray, but the ray has the
> correct color. :-)
I'm glad it served to you. It's also nice to discover one more use for
the CIE macros (again don't forget to post the final pic!).
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jaime Vives Piqueres's furious key-hammering produced this:
>> I had a file directory problem, now solved.
>
> Which was exactly the problem?
I'm guessing that he simply forgot to set the path to the lightsys3 directory
in his POV-Ray settings.
> I'm about to install POV on a eMac with
> Mac OS X, and it will be nice to be aware of it...
One thing to keep in mind with MacPOV and MacMegaPOV (hint: use MacMegaPOV...the
official 3.5 doesn't use all the CPU power in OS X) is that you have to set the
include file paths. Unlike the Windows version, the Mac OS release does not
set the path for you. Minor inconvenience, I assure you. :)
One thing to note, unlike with many "common" applications, there is not much of
a benefit to using a PowerPC processor with POV-Ray (my G4-733, for instance, is
only a touch faster than my P3-750 at rendering). So a 2.0GHz Pentium 4 will
probably beat a G4-1.25 hands down.
--
/*^*/light_source{100*<-5,2,-5>2}#macro I(i,n)#while(strlen(i)>=n)#local A=asc(
substr(i,n,1));#local a=asc(substr(i,n+1,1));cylinder{<div(A,8)-12,mod(A,8)-4,4
><div(a,8)-12,mod(a,8)-4,4>,0.1pigment{rgb z}}#local n=n+2;#end#end I("ScUe[]"1
/*<*/)I("mkmtlttk"1)//@_$#!,:<"Thhis polysig brought to you by Ian Burgmyer :)"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e64207d$1@news.povray.org> , "Ian J. Burgmyer"
<the### [at] maccom> wrote:
> (hint: use MacMegaPOV...the
> official 3.5 doesn't use all the CPU power in OS X)
This isn't true. This is only a rumor created by Chris Huff.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e646317$1@news.povray.org>,
"Thorsten Froehlich" <tho### [at] trfde> wrote:
> > (hint: use MacMegaPOV...the
> > official 3.5 doesn't use all the CPU power in OS X)
>
> This isn't true. This is only a rumor created by Chris Huff.
It is true, and testable. The preview version you released may fix it, I
have not tested that, but the official release left a large chunk of the
CPU idle, from 20-30%, while MacMegaPOV pinned the CPU at 100%.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <cja### [at] netplexaussieorg> ,
Christopher James Huff <cja### [at] earthlinknet> wrote:
> It is true, and testable. The preview version you released may fix it, I
> have not tested that, but the official release left a large chunk of the
> CPU idle, from 20-30%, while MacMegaPOV pinned the CPU at 100%.
What is more relevant what comes out in the end, not what some fuzzy CPU
usage indicator suggests is going on. As you know, there is no way to tell
a "while(1) { }" from an actual computation...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <cja### [at] netplexaussieorg> ,
Christopher James Huff <cja### [at] earthlinknet> wrote:
> The preview version you released may fix it,
BTW, I should point out that 3.51 (of which a public Mac beta is available)
cannot be directly compared with 3.5 because of some antialising bug fixes
that among other scenes also affect benchmark.pov.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ian J. Burgmyer <the### [at] maccom> wrote:
> Jaime Vives Piqueres's furious key-hammering produced this:
> >> I had a file directory problem, now solved.
> >
> > Which was exactly the problem?
>
> I'm guessing that he simply forgot to set the path to the lightsys3 directory
> in his POV-Ray settings.
Well, I put aliases to these files in the include directory, so as to
keep the files organized and separate. There was no error when reading
the 'include' command, so it saw the file, but did not *really* read it,
i.e. the declarations were not made. When I put in the files directly
into 'include', it worked.
--
Kaveh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 4 Mar 2003 17:55:53 +0000
kav### [at] delete_thisfocalimagecom (Kaveh) wrote:
> Well, I put aliases to these files in the include directory, so as to
> keep the files organized and separate. There was no error when reading
> the 'include' command, so it saw the file, but did not *really* read
> it, i.e. the declarations were not made. When I put in the files
> directly into 'include', it worked.
Ah! I see.. That explains it all. POV reads the link file, and not
follows the link to the real files... hmmm... I've never used links
with POV: let me try.. It works fine here with the Linux version.
Perhaps a problem with your custom compile?
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3e64aa31$1@news.povray.org>,
"Thorsten Froehlich" <tho### [at] trfde> wrote:
> What is more relevant what comes out in the end, not what some fuzzy CPU
> usage indicator suggests is going on. As you know, there is no way to tell
> a "while(1) { }" from an actual computation...
Well, it is doing something, and I don't think it is looping. Renders
also finish faster. I haven't checked how much having the preview up
affects this, though. It certainly is possible that MegaPOV is really
wasting that extra CPU power and rendering faster for some other reason.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
