 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> Beta 32 for Windows (32 and 64-bit) is now available at:
Must...restrain...finger...download button....until....home.
May I just say "Sahweeeeet!"
Thanks Chris and the POV Team :)
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Beta 32 for Windows (32 and 64-bit) is now available at:
>
> http://www.povray.org/beta/
>
> Source code will be updated in due course. Linux users will need to wait a
> few days, sorry :)
I still have the bug where if you try to open any file that is exactly 4096
bytes (such as the one attached) it crashes. This is on the 64bit Windows
beta 32. Can anyone else reproduce this?
Post a reply to this message
Attachments:
Download 'us-ascii' (4 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 4/7/2009 5:55 AM, scott wrote:
>> Beta 32 for Windows (32 and 64-bit) is now available at:
>>
>> http://www.povray.org/beta/
>>
>> Source code will be updated in due course. Linux users will need to
>> wait a
>> few days, sorry :)
>
> I still have the bug where if you try to open any file that is exactly
> 4096 bytes (such as the one attached) it crashes. This is on the 64bit
> Windows beta 32. Can anyone else reproduce this?
>
I can confirm that.
--
...Chambers
www.pacificwebguy.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"scott" <sco### [at] scott com> wrote:
> > Beta 32 for Windows (32 and 64-bit) is now available at:
> >
> > http://www.povray.org/beta/
> >
> > Source code will be updated in due course. Linux users will need to wait a
> > few days, sorry :)
>
> I still have the bug where if you try to open any file that is exactly 4096
> bytes (such as the one attached) it crashes. This is on the 64bit Windows
> beta 32. Can anyone else reproduce this?
On 32 bit Windows, no problem.
....and someone can verify this? :
http://news.povray.org/web.49da6275710555cf33f5eb8b0%40news.povray.org
--
Carlo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> Beta 32 for Windows (32 and 64-bit) is now available at:
>
> http://www.povray.org/beta/
>
> Source code will be updated in due course. Linux users will need to wait a
> few days, sorry :)
>
> -------------------------------------------
> Changes between 3.7.beta.31 and 3.7.beta.32
> -------------------------------------------
>
> Added ARRAYS_WriteDF3 macro to arrays.inc for writing an array to a df3 file.
>
> Fixed bug creating artifacts in output file when mosaic preview is used
> with +EP2 and -A.
>
> Several Unix build fixes.
>
> Added radiosity octree performance stats and fixed stats for max trace
> level & parse time.
>
> Made some improvements to performance in crackle cache, and optimised the
> management of the crackle cache size by setting limits in megabytes
> (currently per-thread and not user-settable: this will change).
>
> -------------
> Binary #write
> -------------
>
> It is now possible to write 8, 16 and 32-bit words to an external file.
> These words may be arranged in either little or big-endian fashion.
>
> Placing one of the following keywords in the argument list of a #write
> statement causes the values up to the next comma to be written in binary
> format, using 2's complement integer representation, rounded to the nearest
> integer in the representable range:
>
> uint8 - unsigned byte (0..255)
> sint8 - signed byte (-128..127)
> uint16be, uint16le - unsigned 16-bit word (0..65535)
> sint16be, sint16le - signed 16-bit word (-32768..32767)
> sint32be, sint32le - signed 32-bit word (-2^31..2^31-1)
>
> As of now, unsigned 32-bit words are not supported.
>
> Keywords ending in "be" will cause the values to be written most
> significant byte first ("big endian", aka network byte order) while those
> ending in "le" will instead write the least significant byte first ("little
> endian", Intel format).
>
> The values to be written in binary must be numbers or vectors; the latter
> will be written component by component as specified, in the standard x-y-z
> order, without any separating or enclosing characters.
>
> There is a sample macro called 'ARRAYS_WriteDF3' in arrays.inc which shows
> how this feature may be used.
>
> ---------------------------------
> Subsurface Light Transport (SSLT)
> ---------------------------------
>
> Beta 32 adds experimental support for subsurface light transport (aka
> subsurface scattering).
>
> Currently, SSLT is activated for a particular object by adding the
> following statement to its finish (note that this is very likely to change):
>
> subsurface { COLOR, COLOR }
>
> specifying the (reduced) scattering coefficients (sigma'[s]) and absorption
> coefficients (sigma[a]), respectively, in units of 1/mm, for each of the
> three basic colors. The object's IOR will also affect the results.
>
> The algorithm is designed to give realistic results at a scale of 10 mm per
> POV-Ray unit by default; for other scales, place the following statement in
> the global_settings section:
>
> mm_per_unit NUMBER
>
> To tune the algorithm for quality or performance, the number of samples for
> the diffuse scattering and single-scattering approximation, respectively,
> can be specified by placing the following statement in the global_settings
> section:
>
> subsurface { samples NUMBER, NUMBER }
>
> There is a sample SSLT scene in scenes/subsurface/subsurface.pov.
>
> SSLT is still in alpha stage.
>
OK... so, playing around with SSLT, it looks like radiosity does not
currently interact with the the scattering? Is that correct? Neat
feature, nonetheless, it's going to cost me a significant amount of time.
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason nous illumina en ce 2009-04-05 08:49 -->
> Beta 32 for Windows (32 and 64-bit) is now available at:
>
> http://www.povray.org/beta/
>
> Source code will be updated in due course. Linux users will need to wait a
> few days, sorry :)
>
> -------------------------------------------
> Changes between 3.7.beta.31 and 3.7.beta.32
> -------------------------------------------
>
> Added ARRAYS_WriteDF3 macro to arrays.inc for writing an array to a df3 file.
>
> Fixed bug creating artifacts in output file when mosaic preview is used
> with +EP2 and -A.
>
> Several Unix build fixes.
>
> Added radiosity octree performance stats and fixed stats for max trace
> level & parse time.
>
> Made some improvements to performance in crackle cache, and optimised the
> management of the crackle cache size by setting limits in megabytes
> (currently per-thread and not user-settable: this will change).
>
> -------------
> Binary #write
> -------------
>
> It is now possible to write 8, 16 and 32-bit words to an external file.
> These words may be arranged in either little or big-endian fashion.
>
> Placing one of the following keywords in the argument list of a #write
> statement causes the values up to the next comma to be written in binary
> format, using 2's complement integer representation, rounded to the nearest
> integer in the representable range:
>
> uint8 - unsigned byte (0..255)
> sint8 - signed byte (-128..127)
> uint16be, uint16le - unsigned 16-bit word (0..65535)
> sint16be, sint16le - signed 16-bit word (-32768..32767)
> sint32be, sint32le - signed 32-bit word (-2^31..2^31-1)
>
> As of now, unsigned 32-bit words are not supported.
>
> Keywords ending in "be" will cause the values to be written most
> significant byte first ("big endian", aka network byte order) while those
> ending in "le" will instead write the least significant byte first ("little
> endian", Intel format).
>
> The values to be written in binary must be numbers or vectors; the latter
> will be written component by component as specified, in the standard x-y-z
> order, without any separating or enclosing characters.
>
> There is a sample macro called 'ARRAYS_WriteDF3' in arrays.inc which shows
> how this feature may be used.
>
> ---------------------------------
> Subsurface Light Transport (SSLT)
> ---------------------------------
>
> Beta 32 adds experimental support for subsurface light transport (aka
> subsurface scattering).
>
> Currently, SSLT is activated for a particular object by adding the
> following statement to its finish (note that this is very likely to change):
>
> subsurface { COLOR, COLOR }
>
> specifying the (reduced) scattering coefficients (sigma'[s]) and absorption
> coefficients (sigma[a]), respectively, in units of 1/mm, for each of the
> three basic colors. The object's IOR will also affect the results.
>
> The algorithm is designed to give realistic results at a scale of 10 mm per
> POV-Ray unit by default; for other scales, place the following statement in
> the global_settings section:
>
> mm_per_unit NUMBER
>
> To tune the algorithm for quality or performance, the number of samples for
> the diffuse scattering and single-scattering approximation, respectively,
> can be specified by placing the following statement in the global_settings
> section:
>
> subsurface { samples NUMBER, NUMBER }
>
> There is a sample SSLT scene in scenes/subsurface/subsurface.pov.
>
> SSLT is still in alpha stage.
>
Tried to render subsurface.pov.
subsurface is not recognised as a valid keyword here.
Win XP, NOT SSE processor.
Same thing for mm_per_unit.
Both result in an undefined variable found error message.
--
Alain
-------------------------------------------------
You can go anywhere you want if you look serious and carry a clipboard.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 07 Apr 2009 14:00:00 -0400, Alain <ele### [at] netscapenet> wrote:
>Tried to render subsurface.pov.
>
>subsurface is not recognised as a valid keyword here.
>Win XP, NOT SSE processor.
>Same thing for mm_per_unit.
>Both result in an undefined variable found error message.
>
Using Vista and pvengine.exe, it ran OK for me.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Stephen nous illumina en ce 2009-04-07 14:22 -->
> On Tue, 07 Apr 2009 14:00:00 -0400, Alain <ele### [at] netscapenet> wrote:
>
>> Tried to render subsurface.pov.
>>
>> subsurface is not recognised as a valid keyword here.
>> Win XP, NOT SSE processor.
>> Same thing for mm_per_unit.
>> Both result in an undefined variable found error message.
>>
>
> Using Vista and pvengine.exe, it ran OK for me.
Will try again. Maybe it did'nt start properly.
--
Alain
-------------------------------------------------
Documentation; The worst part of programming.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> OK... so, playing around with SSLT, it looks like radiosity does not
> currently interact with the the scattering? Is that correct?
Yes. Was mentioned somewhere in this newsgroup already.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> I still have the bug where if you try to open any file that is exactly
>> 4096 bytes (such as the one attached) it crashes. This is on the 64bit
>> Windows beta 32. Can anyone else reproduce this?
>>
>
> I can confirm that.
Yeah, I can confirm it too with beta 32 (x64).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
