 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm running POV-Ray for Windows 3.6.1 on Win2000 and just ran into an
interesting effect. I continued a trace which was actually an animation. The
preview Window would show the finished images one by one after parsing, but
with some colors switched: white was black, some reds seemed blue, but some
grays remained gray, as well as some brownish ones... Very interesting.
Didn't have any negative effects on the actual written Output, nontheless,
is this a known issue?
It's late right now and I need to go to bed, but tomorrow I'll try to cook
up a minimal scene which duplicates the effect.
Regards,
Tim
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
le message de news:415767ea$1@news.povray.org...
> It's late right now and I need to go to bed, but tomorrow I'll try to cook
> up a minimal scene which duplicates the effect.
Yes, it's a bug (no harm done, it just messes with the display when the file
output is a bmp). See my bug report dated Sept 1. The bizarre thing is that
though it's a very visible bug (render bmp, abort trace, resume trace,
blam!) it took such a long time to be noticed!
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Yes, it's a bug (no harm done, it just messes with the display when the
file
> output is a bmp). See my bug report dated Sept 1. The bizarre thing is
that
> though it's a very visible bug (render bmp, abort trace, resume trace,
> blam!) it took such a long time to be noticed!
Well, I guess many just use subset-framing to start at certain points in an
animation, rather than using continued trace. Makes sense as well, as
POV-Ray needs to parse the finished frames before it recognizes that the
Output-File is present (which might be useful to handle with an option to
check first and only parse if image isn't finished or not present, but is
needed for situations in which each frame creates data for the next, like
via particle systems or such).
In any case, I've often, instead of resuming an animation, started off at a
later frame, hence I missed the bug before. Still it's just a minor nuisance
in display, nothing of extreme importance, so I guess an update will be
released once more serious problems have been fixed. I won't complain. :-)
Regards,
Tim
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
le message de news:415885c5$1@news.povray.org...
> In any case, I've often, instead of resuming an animation, started off at
a
> later frame, hence I missed the bug before.
Note that it's not an animation bug, but that it shows up any time one
aborts and resumes the tracing of a BMP file with the display on. I guess
that few people use BMPs and even less people resume tracing BMPs!
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Note that it's not an animation bug, but that it shows up any time one
> aborts and resumes the tracing of a BMP file with the display on. I guess
> that few people use BMPs and even less people resume tracing BMPs!
Oh, didn't notice that. I always use BMP, but I really seldomly use
continued trace, mainly because when I change the image, I change so much...
--
"Tim Nikias v2.0"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
