 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
'StretchDIBits()Failed!(Windows error)'
Whatever it is, is there a way to avoid it?
~Steve~
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 'StretchDIBits()Failed!(Windows error)'
>
> Whatever it is, is there a way to avoid it?
The only time I've encounted this was when I rendered a huge image and had
the display window maximized. I think I was low on memory too.
So it basically means the image can't be displayed in the display window for
some reason, but it should still go to the output file which you can view
later.
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Slime" <fak### [at] email address> wrote in message
news:41377687$1@news.povray.org...
> > 'StretchDIBits()Failed!(Windows error)'
> >
> > Whatever it is, is there a way to avoid it?
>
> The only time I've encounted this was when I rendered a huge image
and had
> the display window maximized. I think I was low on memory too.
>
> So it basically means the image can't be displayed in the display
window for
> some reason, but it should still go to the output file which you can
view
> later.
Thanks Slime, that's exactly what's happening. I have a large
render that sometimes displays in the render window, but if it
doesn't, then I can still view the output as per normal. The message
being sporadic confused me - but that's the memory side of it I
guess...
Thanks again.
~Steve~
>
> - Slime
> [ http://www.slimeland.com/ ]
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I hate when that happens :)
I'm really used to the display window.
--
- Nicolas Alvarez
nicolas [dot] alvarez [at] gmail [dot] com
news:41377237$1@news.povray.org...
> 'StretchDIBits()Failed!(Windows error)'
>
> Whatever it is, is there a way to avoid it?
>
>
> ~Steve~
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
St. wrote:
> 'StretchDIBits()Failed!(Windows error)'
>
> Whatever it is, is there a way to avoid it?
>
>
> ~Steve~
I got that in 3.5 on W98 after running for about two hours without
rebooting, with a large render getting parsed and rendered every three or
four minutes.
How about regularly closing Povray and restarting it (using XP) or rebooting
(using 98)?
--
Stefan Viljoen
Software Support Technician
Polar Design Solutions
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
