POV-Ray : Newsgroups : povray.beta-test.binaries : optics.pov 3.7.0 vs 3.7.1 : Re: optics.pov 3.7.0 vs 3.7.1 Server Time
28 Apr 2024 17:01:59 EDT (-0400)
  Re: optics.pov 3.7.0 vs 3.7.1  
From: clipka
Date: 24 Feb 2016 10:51:23
Message: <56cdd17b$1@news.povray.org>
Am 24.02.2016 um 16:02 schrieb ThH:
> Am 24.02.2016 um 15:55 schrieb Jaime Vives Piqueres:
> 
>>    Happens here too on 3.7.1-alpha.8454683, AMD FM-6300, Ubuntu 14.04.3
>> LTS.
>>
>> -- 
>> jaime
> 
> Thanks for checking and confirming Jaime :)
> 
> So it's not just me ;)

Okay, here's the deal: I can't reproduce it, so my only chance to
identify the root cause is to have a close look at the code, but for
that to make any sense I need a clear picture of exactly where to look.
To this end, I need you (that's "you" as in "y'all") to:

- figure out the simplest possible scene that exhibits the problem;

- identify exactly which commit (in the master branch) broke the scene; and

- do plenty of systematic toying around with the scene to figure out the
exact circumstances under which the error shows. (For instance, why
isn't the green beam affected? Is it because it is not reflected? Then
why aren't the red and blue beams affected right after the first
reflection? Does max_trace_level have anything to do with it? Why does
only the bottom of the red sub-beams seem affected? Why the top and
center of the blue sub-beams? etc. -- Be inquisitive and creative!)


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.