 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"StephenS" <sshonfield(at)ottawa(dot)net> wrote in message
news:442707ac$1@news.povray.org...
> No pvengine-sse2.exe like the previous betas
I hadn't noticed, yeah, I moved the files into the bin folder a little
hastily. ;)
> Windows 98se reports
>
> The PVENGINE.EXE file is linked to missing export
> USER32.DLL:SetLayeredWindowAttributes
>
> under this popup window is another
>
> C:\Program Files\POV-Ray for windows v3.6\bin\pvengine.exe
> A device attached to the system is not functioning
XP complains about DLL C:\Windows\System32\faultrep.dll is not a valid
windows image, and shows a different message from POV under that, instead of
what you got there.
Something seems to be wrong. Bad compile or bad upload/download?
I reinstalled 3.6.1b and also this beta 12 again, no change.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
StephenS wrote:
> No pvengine-sse2.exe like the previous betas
oops, my bad, will fix now.
> Windows 98se reports
>
> The PVENGINE.EXE file is linked to missing export
> USER32.DLL:SetLayeredWindowAttributes
yes, this is the issue mentioned in the release notes.
I will fix this shortly.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob H wrote:
> I reinstalled 3.6.1b and also this beta 12 again, no change.
strange, I downloaded the zip and the file works well here. yet there's
obviously a problem. I will pull the beta until I work out what.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Checked the system registry (XP SP2) and did some DLL juggling and nothing
helps here. Was hoping I only fouled things up when I overwrote the version
3.6 pvengine.exe when I thought I had renamed it. So either your computer is
somehow more forgiving or mine is less tolerant.
Sorry to have ruined this early beta release! Was a pleasant surprise before
now.
Bob Hughes
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob H wrote:
> Checked the system registry (XP SP2) and did some DLL juggling and nothing
> helps here. Was hoping I only fouled things up when I overwrote the version
> 3.6 pvengine.exe when I thought I had renamed it. So either your computer is
> somehow more forgiving or mine is less tolerant.
Turns out the issue only appears on non-SMP machines. some of the startup
code was misbehaving but having the extra CPU masked it. I'm building a new
release now.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
A new archive is available which hopefully solves the timeout on startup issue.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
That solved it alright!
Almost asked about the increase in file size until I remembered that SSE one
was put back in.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Images rendered with 3.7beta12 seem noticeably brighter than the same
image rendered with 3.6 (even when no assumed_gamma of any kind is used
in the scene). Seems to be some gamma issue still.
For example, try textures/patterns/fractals1.pov for a remarkable
difference.
For some reason advanced/bwstripe.pov renders very differently in
3.7beta12 than in 3.6.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> For some reason advanced/bwstripe.pov renders very differently in
> 3.7beta12 than in 3.6.
this is due to the way we handle color ranges and AA in particular. bwstripe
uses a 'trick' to get the striping (very high brightness values), and that
trick was dependent on the way POV handled these (particularly at what point
the pixels were truncated to 1.0).
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoo povrayorg> wrote:
> this is due to the way we handle color ranges and AA in particular. bwstripe
> uses a 'trick' to get the striping (very high brightness values), and that
> trick was dependent on the way POV handled these (particularly at what point
> the pixels were truncated to 1.0).
I actually got this morning the wild idea that perhaps, just perhaps,
the effect seen with bwstripe.pov is the result of some experimental
antialiasing algorithm which handles the problems in the pov3.6 antialiasing.
However, when I made a simple test with an overbright object, the edge
was still pixelated. So I suppose I was wrong. :(
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
