POV-Ray : Newsgroups : povray.binaries.images : Texture maps different in 3.5 even when using #version Server Time
13 Aug 2024 17:23:02 EDT (-0400)
  Texture maps different in 3.5 even when using #version (Message 1 to 4 of 4)  
From: Not My Real Email Address
Subject: Texture maps different in 3.5 even when using #version
Date: 1 Feb 2003 07:20:22
Message: <3e3bbb86@news.povray.org>
/*
Please reply to the group povray.general (and povray.bugreports if you
can confirm this is a genuine certified 100% bug).

I find the following texture renders markedly differently in 3.5 compared
with both 3.0.20-10 debian and megapovplus 0.5.0.2.5a-1 (3.1 equivalent),
which both render the images similarly to each other.

It looks to me like the grade between 0 and 1.0 in the texture map of the
older versions is quite different to the grade in 3.5 .. for example as
if one used a linear gradient and the other an exponential one. I hope
someone understand what I mean.

I don't see this mentioned in the documentation or in the bugs so far 
listed in povray.general or povray.bugreports, or by googling old usenet 
postings.

I haven't played much with 3.5, but have checked that if I use a plain
pigment it is the same color.

Can someone tell me this is a bug, or is expected behaviour and why? If
so, how do i figure out how to translate an old-style texture into a new
one?

Images attached to this message -- see beneath the scene data below:

Simeon
*/

#include "colors.inc"
#version 3.0

//test.pov                  
//bah there is some bug in the 3.5 textures i think         
//Simeon Scott 2003-02-01 ////////////////////////
//Something like a blue agate.
/////////////////////////////


background
  { color White }

global_settings
{
  ambient_light 0.05
  assumed_gamma 1
}

camera
{
  location <0, 0, -3>
  look_at <0, 0, 0>
  scale 0.2
}

light_source
  {  <2, 4, -3> color White scale 0.4 }

#declare Sim_Blue_Agate = texture
{
  waves
  texture_map	
  {
    [  0.15 pigment { color White }        ]
    [  1.0  pigment { color <0, 0, 0.3> }  ]
  }
  turbulence <10, 10, 0.3>
  scale 0.1
}

sphere
  {  <0, 0, 0>, 0.3	texture {  Sim_Blue_Agate } }



// end of scene data .. image data follows (3 images)

/*


Post a reply to this message


Attachments:
Download 'test_3.0.jpg' (11 KB) Download 'test_3.5.jpg' (8 KB) Download 'test_mega0.5.jpg' (11 KB)

Preview of image 'test_3.0.jpg'
test_3.0.jpg

Preview of image 'test_3.5.jpg'
test_3.5.jpg

Preview of image 'test_mega0.5.jpg'
test_mega0.5.jpg


 

From: Not My Real Email Address
Subject: Re: Texture maps different in 3.5 even when using #version
Date: 1 Feb 2003 07:36:04
Message: <3e3bbf34@news.povray.org>
Bah this newsreader!

If you don't get the images automatically, try this URL .. I will leave
them there for a while. (Otherwise please cut and paste the text and 
uudecode it if you know how).

http://bur.st/~shevek/test_3.0.jpg
http://bur.st/~shevek/test_mega0.5.jpg
http://bur.st/~shevek/test_3.5.jpg

Thanks in advance for your kind help :)

Simeon


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Texture maps different in 3.5 even when using #version
Date: 1 Feb 2003 09:11:07
Message: <3e3bd57b$1@news.povray.org>
In article <3e3bbf34@news.povray.org> , Not My Real Email Address 
<ano### [at] anoncom>  wrote:

> Bah this newsreader!

Note that it creates attachments in an invalid format.  You may want to use
a less buggy newsreader.  And you may want to configure it to at least show
your name...

    Thorsten


Post a reply to this message

From: Mark Wagner
Subject: Re: Texture maps different in 3.5 even when using #version
Date: 2 Feb 2003 06:24:38
Message: <pan.2003.02.02.11.23.17.620335.263@gte.net>
On Sat, 01 Feb 2003 09:11:07 -0500, Thorsten Froehlich quoth:

> In article <3e3bbf34@news.povray.org> , Not My Real Email Address
> <ano### [at] anoncom>  wrote:
> 
>> Bah this newsreader!
> 
> Note that it creates attachments in an invalid format.  You may want to
> use a less buggy newsreader.  And you may want to configure it to at
> least show your name...

It created a perfectly valid format: text/plain.  The only problem is that
PAN 0.11.2 doesn't support binary attachments, so Simeon tried to fake it
by base64-encoding the images manually and pasting the result into the
body of the message.

-- 
Mark


Post a reply to this message

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