Jim Holsenback wrote:
> Stephen & Sabrina: I'm done with all my edits and have rendered all the 
> files in the textures directory.
> 

I've gotten the objects folder rendered, but the portfolio is taking 
longer as I'm not too talented at scripting, so I am running each pass 
by the GUI and Sel-Run.

The biggest issue I've seen so far is the wood include and 
objects/pawns.pov. The wood textures look completely different without 
the assumed gamma statements, and pawns seems to have some graphical 
issue. I'm thinking it might be coincident surfaces, but I've not looked 
at it too close yet.

Post a reply to this message

"Sabrina Kilian" <"ykgp at vtSPAM.edu"> wrote in message 
news:48a3573c$1@news.povray.org...
> The biggest issue I've seen so far is the wood include and 
> objects/pawns.pov. The wood textures look completely different without the 
> assumed gamma statements, and pawns seems to have some graphical issue. 
> I'm thinking it might be coincident surfaces, but I've not looked at it 
> too close yet.

hmmmm .... the only thing that slowed me down was that some of the images in 
advanced had different aspect ratio's (other than 4:3). The stuff in 
textures went by super fast once I got past my "Doh" moment using the file 
queue feature. The file queue feature was appealling to me because I wanted 
to have the renders go unattended. I inspected the headers and camera 
statements and found nothing unusual so I thought they looked like an ideal 
candidate for batch processing.

I'm wondering if you had a particular file in mind that you were seeing the 
wood.inc problem, or should I just have a look at anything that sources 
wood.inc ..... mind you it's not that I don't believe you, I'm just curious 
and want to have a look. I'm going to slow things down abit until I hear 
back from Chris on disc space.

Jim

Post a reply to this message

"Sabrina Kilian" <"ykgp at vtSPAM.edu"> wrote in message 
news:48a3573c$1@news.povray.org...
> The wood textures look completely different without the assumed gamma 
> statements, and pawns seems to have some graphical issue. I'm thinking it 
> might be coincident surfaces, but I've not looked at it too close yet.

pawns problem is indeed coincident surfaces ..... checkout where the author 
finally builds the chessboard. The calls to the object "Eights" could use a 
bit of +y ..... i used 0.000001 and it looks fine now. BTW: the wood 
textures in this file look ok to me.

Jim

Post a reply to this message

Jim Holsenback wrote:
> "Sabrina Kilian" <"ykgp at vtSPAM.edu"> wrote in message 
> news:48a3573c$1@news.povray.org...
>> The biggest issue I've seen so far is the wood include and 
>> objects/pawns.pov. The wood textures look completely different without the 
>> assumed gamma statements, and pawns seems to have some graphical issue. 
>> I'm thinking it might be coincident surfaces, but I've not looked at it 
>> too close yet.
> 
> hmmmm .... the only thing that slowed me down was that some of the images in 
> advanced had different aspect ratio's (other than 4:3). The stuff in 
> textures went by super fast once I got past my "Doh" moment using the file 
> queue feature. The file queue feature was appealling to me because I wanted 
> to have the renders go unattended. I inspected the headers and camera 
> statements and found nothing unusual so I thought they looked like an ideal 
> candidate for batch processing.
> 
> I'm wondering if you had a particular file in mind that you were seeing the 
> wood.inc problem, or should I just have a look at anything that sources 
> wood.inc ..... mind you it's not that I don't believe you, I'm just curious 
> and want to have a look. I'm going to slow things down abit until I hear 
> back from Chris on disc space.
> 
> Jim 
> 
> 

Yeah, the file queue worked great for objects, I set it to run in both 
3.6 and 3.7, turned on an MMO, and by the time the evening was over they 
were both done. The portfolio requires rendering with an .ini unique to 
each .pov file, and so eats up a bit more time as I'm not comfortable 
with scripting windows to do it for me.

On to wood.inc: In the display window while it's running and rendering, 
the images looked a lot different for the same file. Brighter or darker, 
the colors seemed more saturated. Checking the image after it's been 
saved to disk, I don't see the huge difference any longer.

I looked at t_woods6.png, it looks like it has some minor color 
differences in the dark area, but that could just be me. I'll check it 
in Gimp and difference the two images to see if it's just where I have 
the pictures on the screen.

Post a reply to this message

"Sabrina Kilian" <"ykgp at vtSPAM.edu"> wrote in message 
news:48a4db21$1@news.povray.org...
> On to wood.inc: In the display window while it's running and rendering, 
> the images looked a lot different for the same file. Brighter or darker, 
> the colors seemed more saturated. Checking the image after it's been saved 
> to disk, I don't see the huge difference any longer.

i saw this too and thought that tweeking the Display_Gamma entries in 
quickres.ini would help ...... it did.

Jim

Post a reply to this message

"Jim Holsenback" <jho### [at] hotmailcom> wrote:
> Stephen & Sabrina: I'm done with all my edits and have rendered all the
> files in the textures directory.
>
> Chris: do you have some disc space that we can start putting the scene
> source files and images?
>
> Jim

I've gone thought my first edits with v3.7, some things i've seen:

Two files have warnings, this is just the way the file is constructed, I see no
problem with leaving them as is.
String.pov, warning no objects
Screen.pov, warning more than one camera

Web link, and still working, will it always?
Sundial.pov

Some files are set up to use animations, I_internal.pov, but some need to be
manualy edited to get the full benefit, Transform.pov. I'll leave this for
posible future edits. I prefer the animation setup.

I like the idea of using the comments to add the assumed_gamma settings
// -w768 -h576 +a0.3 display_gamma=1.8
or what ever is needed for the file.

comments welcome.

Stephen S

Post a reply to this message

Jim Holsenback wrote:
> Stephen & Sabrina: I'm done with all my edits and have rendered all the 
> files in the textures directory.
> 
> Chris: do you have some disc space that we can start putting the scene 
> source files and images?

Sorry, only just now catching up with group: yes, I'll set something up.

-- Chris

Post a reply to this message

"Jim Holsenback" <jho### [at] hotmailcom> wrote in message 
news:48a2b9c9@news.povray.org...
> Stephen & Sabrina: I'm done with all my edits and have rendered all the 
> files in the textures directory.

I'm all done with these sections (edits & renders) ....

advanced/animations (71)
interior/language/lights/objectmods/qtvr/radiosity (69)
textures (73)

1. there were less than half dozen files that required differnt aspect ratio 
other than 4:3

2. a couple of files were order dependant (error because it was looking for 
a image file that hadn't been rendered yet)

3. advanced/fish13/fish.inc and stem1.inc had #version 1.0 set. I left 
fih.inc at #version 1.0 (comma's between vector coords?) upgraded stem1.inc 
to #version 3.5 and replaced alpha with filter. left world12.inc alone as it 
had no #version.

4. modified glass.inc and glass_old.inc (textures-> materials)

5. assumed_gamma handling was by far the dominate issue.

Jim

Post a reply to this message

Stephen,

I've set up a FTP account for the scenes but don't have your email
address handy ATM. Please drop me an email and I'll pass on the login
details.

-- Chris

Post a reply to this message

"Jim Holsenback" <jho### [at] hotmailcom> wrote:
....
Sorry for taking so long, I have been struggling a bit, but seem to be going
fine now. This post by Jim has helped.
> [768x576, AA 0.3]
>
> Width=768
>
> Height=576
>
> Antialias=On
>
> Antialias_Threshold=0.3
>
> Display_Gamma=2.3
....
I'm using this in quickres.ini to help:

[768x576, AA 0.3, png]
Width=768
Height=576
Antialias=On
Antialias_Threshold=0.3
Output_File_Type = n

> // Updated: 04Aug2008(jh) for v3.7 distribution
>
>
>
> #if (version < 3.6)
>
>   #version 3.5
>
> #end
>
>
>
> #include "glass.inc"
>
> #include "lemon.inc"
>
>
>
> global_settings {
>
>    // conditionally comply with gamma correction handling
>
>    #if (version < 3.6)
>
>         assumed_gamma 1.0
>
>    #end
>
....
I'm using a version of this in the scene file:

// Updated: Aug2008(sjs) for version and gamma
// -w768 -h576 +a0.3 Output_File_Type=n Display_Gamma=1
#if (version < 3.7)
  #version 3.6;
  global_settings { assumed_gamma 2.2 }
#end

Stephen S

Post a reply to this message