Jim Holsenback wrote:
> "Sabrina Kilian" <"ykgp at vtSPAM.edu"> wrote in message 
> news:488a6e58@news.povray.org...
>> StephenS wrote:
>>> "Jim Holsenback" <jho### [at] hotmailcom> wrote:
>>>> I'm starting a new thread for the v3.7 example scenes project ...
>>> Ok, I've reinstalled POV-Ray 3.7.0.beta27.
>>> I'll go step by step in case my method needs fixing.
>>> As my first victim, scenes\qtvr\qtvrpanorama.pov from 3.7
>>> File states:
>>> #version 3.5;
>>> global_settings{ assumed_gamma 1.0}
>>> //-w384 -h1284 (command line recomended)
>>>
>>> 1)I run the scene with POV-Ray 3.5
>>> 2)I run the scene with POV-Ray 3.7(new output file name)
>>> 3)I run the scene with POV-Ray 3.7, removing version and gamma(new output 
>>> file
>>> name)
>>>
>>> I compare 1 and 2, PaintShopPro/Arithmetic/difference. The resulting 
>>> image is
>>> not blank.
>>> I compare 1 and 3, PaintShopPro/Arithmetic/difference. The resulting 
>>> image is
>>> not blank.
>>>
>>> qtvrpanorama.pov does not render the same.
>>> Yikes, now what?
>>>
>>> Include the updated scene anyways? If it needs fixing, this will be 
>>> beyond me.
>>>
>>>
>> Next is talking about what changes are visible, and figuring out what to 
>> change to "fix" it. Some differences will be easy, others might not. As a 
>> group, though, we should be able to get a good many of them.
> 
> i think before we get to far ahead of ourselves we should divide up the 
> examples so we can work without stepping on each others toes. 

I didn't mean it was the next immediate step, just the next thing to do 
for that single image.

>if there are 
> no objections i'll use the manifest list to evenly divide up those scenes 
> into managable chunks. i think a good first pass would be to try to render 
> the scenes and see what goes without any changes. fails/warnings/problems 
> lets just make notes and move on to the next scene.

That sounds like a good idea to me. I can think of one possible issue. 
Certain files in the demo scenes tend to take a lot longer to render. If 
memory serves me right, the radiosity ones take more time, in general, 
and should be split over multiple chunks.

> i think this will pare 
> down the list and help use identify the problem scenes. as for debugging i 
> agree with Sabrina that we should be able work through most problems amoung 
> ourselves. if not, i'm sure that others in the users community will be able 
> to bail us out. i'll wait a bit for any comments before proceeding in case 
> either of you have a better idea how to go forward.
> 
> Jim 
> 
> 

The last thing we need to agree on might be an ideal image format to 
test with. I'm not familiar with the technical differences between Targa 
and PNG, could anyone else chime in if we might notice certain 
differences that appear in one or the other, or at certain bit depths?

Post a reply to this message