 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Francois ,
I've tried to mail you but can,t seem to get through. So I'm hoping
you are reading this news group. (Sorry to everyone else)
Thanks for your help. That's quite the scene you sent me and I must
say I
was impressed with your other renderings on your home page as well.
Just for your information, I rendered the scene with the following
results.
command line: povray -ibiere.pov +A0.2 +V +W800 +H600
Time: 60 hours 21 min 48sec (The machine was doing nothing else)
Machine:
Dec 21164PC
533MHz
64 Meg
OS windows NT 4.0 service pack 3
(If your wondering, this machine retails for around $2000 US (But It's
not mine))
When I get a chance, I'll try it on the bigger machines and
eventualy on
multiple nodes using pvmpov and Linux.
Thanks again,
dave
--
dav### [at] altatech com
http://www.altatech.com/
Post a reply to this message
Attachments:
Download 'us-ascii' (2 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 22 Jan 1998 18:48:20 -0700, Dave Tucker <dav### [at] altatechcom>
wrote:
>
>--------------63C1B4AB13E26AB8A136BCF4
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Francois ,
> I've tried to mail you but can,t seem to get through. So I'm hoping
>you are reading this news group. (Sorry to everyone else)
>
> Thanks for your help. That's quite the scene you sent me and I must
>say I
>was impressed with your other renderings on your home page as well.
>
> Just for your information, I rendered the scene with the following
>results.
>
>command line: povray -ibiere.pov +A0.2 +V +W800 +H600
>
>Time: 60 hours 21 min 48sec (The machine was doing nothing else)
>
>Machine:
> Dec 21164PC
> 533MHz
> 64 Meg
> OS windows NT 4.0 service pack 3
>(If your wondering, this machine retails for around $2000 US (But It's
>not mine))
Ssshhhhhu! Made the ferrari...
>
> When I get a chance, I'll try it on the bigger machines and
>eventualy on
>multiple nodes using pvmpov and Linux.
>
>Thanks again,
> dave
>
>
>
>--
>dav### [at] altatechcom
>http://www.altatech.com/
>
>
>
>--------------63C1B4AB13E26AB8A136BCF4
>Content-Type: text/html; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
><HTML>
>Francois ,
><BR> I've tried to mail you but can,t seem to get through.
>So I'm hoping you are reading this news group. (Sorry to everyone
>else)
>
><P> Thanks for your help. That's quite the scene
>you sent me and I must say I
><BR>was impressed with your other renderings on your home page as well.
>
><P> Just for your information, I rendered the scene
>with the following
><BR>results.
>
><P>command line: povray -ibiere.pov +A0.2 +V +W800 +H600
>
><P>Time: 60 hours 21 min 48sec (The machine was doing
>nothing else)
>
><P>Machine:
><BR> Dec 21164PC
><BR> 533MHz
><BR> 64 Meg
><BR> OS windows NT 4.0 service pack 3
><BR>(If your wondering, this machine retails for around $2000 US
>(But It's not mine))
>
><P> When I get a chance, I'll try it on the bigger machines
>and eventualy on
><BR>multiple nodes using pvmpov and Linux.
>
><P>Thanks again,
><BR> dave
><BR>
><BR>
><PRE>--
>dav### [at] altatechcom
><A HREF="http://www.altatech.com/">http://www.altatech.com/</A></PRE>
> </HTML>
>
>--------------63C1B4AB13E26AB8A136BCF4--
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
There is a bug in POV-Ray version 3.02 (Win95 version).
When rendering scenes with radiosity the "brightness" setting will
default to 3.3 during a pixel-by-pixel trace. During 2x2 traces, 4x4
traces, and etc, the brightness value specified in the scene file
gives the appropriate results, as soon as a 1x1 is reached, the value
will default back to 3.3
THIS IS NOT A MINOR PROBLEM. Brightness is the most important
setting in POV-Ray's radiosity. To get around it, I've had to use
light sources with colour-components greater than 1.0 This trick
ruins the scene where there is direct lighting and can never match the
results of higher brightness values no matter how much larger the
light's components are made.
This bug happens even if I repeat the "brightness" statement
continually in the scene file. Even after a restart of POV-Ray. Even
after saving the scene. Even after rebooting. With or without
anti-alaising. With or without global ambience, with or without
assumed_gamma. Even after closing all other programs and
re-rendering.
To see this problem in action, set the brightness to some ridiculous
value (around 55.0 or so).. The first pass of the scene, usually an
8x8, the scene will be washed-out in glowing white, then during the
final pixel-by-pixel pass, the rendered lines should look noticably
darker. In fact, just as dark as they would be for a 3.3 brightness!!
This has happened at a myriad of brightness settings above 3.3
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, reading section 7.8.9.2.1 only confused me more. :) When I checked
on this a week ago, the brightness section made me think this is the way it
is supposed to be!
I know you're right, though, because I accidently ran a scene at
brightness 33.3 once. It came out the same as brightness 3.3 did. Most
important?
--
Paul Hinds
gri### [at] swbellnet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
oops, try putting "ambient_light color rgb <something other then 1,1,1>" in
your global_settings.
Should modify your definition of most important, just a tad. :)
--
Paul Hinds
gri### [at] swbellnet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
>Try modifying your global settings with something other then <1,1,1>
under
>"ambient_light color rgb <?,?,?>"
>
>Paul Hinds
>gri### [at] swbellnet
This DOES NOT fix the problem for values above or below 1.0 Above
1.0, radiosity affects _totally_ disappear. Below 1.0, I get the same
old problem.
Sorry. The fact is that the brightness value is ACTUALLY changing
back to 3.3 during rendering. I have been programming in ray tracing
since I was in high school and I know that POVray's radiosity works by
using a multiplier on already-existing ambient values of a surface.
(Note that having ambient values of zero on surfaces causes POV's
radiosity to dissappear.) A larger "brightness" increases the
multiplier on the ambient value before it is returned upwards to the
renderer. This is how I know the effect I am seeing is caused the
brightness value.
The bug remains!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Please stop posting this "correction." I would hate to repeat myself
on every group.
As I said before in other groups on this server, this WILL NOT FIX THE
PROBLEM. The bug remains. Thank you.
On Sat, 24 Jan 1998 23:34:17 -0600, "GrimDude"
<grimdude&nos### [at] swbellnet> wrote:
>oops, try putting "ambient_light color rgb <something other then
1,1,1>" in
>your global_settings.
>
>Should modify your definition of most important, just a tad. :)
>
>--
>Paul Hinds
>gri### [at] swbellnet
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I didn't fly off the handle and post to every group, dude. I think posting
to the appropriate group would have been enough.
I'd hate for you to repeat it, too.
--
Paul Hinds
gri### [at] swbellnet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I haven't seen any followups here, but I did test this on both PC versions
(Win95 & DOS). Both versions react identically.
--
Paul Hinds
gri### [at] swbellnet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think a povray.bugs group would be nice, somewhere for any apparent bugs
to be reported, and acknowledgements from the POV team so you know that it
may be fixed by the next version. With an FPB (Frequently Posted Bugs
heehee ;-) allowing bugs and workarounds to be archived and removed to
clear up clutter.
Perhaps this could actually be povray.suggestions.moderated - with posts
'signed' by 5 or more povray users somehow (this would ensure proper
discussion in povray.suggestions perhaps and details on how it might work
before cluttering the 'real' suggestions group), [volunteer] moderators
would look at the signaturies for at least one povray programmer (that they
can recognise from the povray.programming group) before they accept it for
cluttering up in case it's utterly far fetched for the PoV team to do it.
And of course, there would be no obligation to the PoV team to follow up on
the suggestions (but I think we would all demand a follow up on the bugs).
--
Tristan Wibberley
(Remove the '.NO_LUNCHEON_MEAT' from my
email address to reply.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
