|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
What is "StretchDiBits() failed! Windows error!" ?
Anyone know what does it mean? It appears with a big resolution render.
Best regards,
Oleguer
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Oleguer Vilella" <ole### [at] infonegociocom> wrote in message
news:416adae3$1@news.povray.org...
> What is "StretchDiBits() failed! Windows error!" ?
I *think* this error only occurs when you render an image larger than the
current screen resolution, and then only under certain circs.
Try rendering with the render-window turned off.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <416adae3$1@news.povray.org> , "Oleguer Vilella"
<ole### [at] infonegociocom> wrote:
> What is "StretchDiBits() failed! Windows error!" ?
> Anyone know what does it mean? It appears with a big resolution render.
The preview image is too big for Windows to show you a preview. Turn off the
preview (using the -d option).
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yes if I turn off the preview all is OK.
Is it a Windows problem or a screen resolution problem?
news:416adf80$1@news.povray.org...
> In article <416adae3$1@news.povray.org> , "Oleguer Vilella"
> <ole### [at] infonegociocom> wrote:
>
> > What is "StretchDiBits() failed! Windows error!" ?
> > Anyone know what does it mean? It appears with a big resolution render.
>
> The preview image is too big for Windows to show you a preview. Turn off
the
> preview (using the -d option).
>
> Thorsten
>
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trfde
>
> Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <416af1b2$1@news.povray.org> , "Oleguer Vilella"
<ole### [at] infonegociocom> wrote:
> Is it a Windows problem or a screen resolution problem?
A Windows limitation.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ah, Ok, maybe with Linux I don't have this problem. Have you ever trayed
with Linux?
news:416af307$1@news.povray.org...
> In article <416af1b2$1@news.povray.org> , "Oleguer Vilella"
> <ole### [at] infonegociocom> wrote:
>
> > Is it a Windows problem or a screen resolution problem?
>
> A Windows limitation.
>
> Thorsten
>
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trfde
>
> Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <416af462@news.povray.org> , "Oleguer Vilella"
<ole### [at] infonegociocom> wrote:
> Ah, Ok, maybe with Linux I don't have this problem. Have you ever trayed
> with Linux?
It does not make sense to get a preview for a 6400*4800 render. All it will
do is consume a real lot of memory and slow down rendering.
As I already pointed out, there is no problem, it is simply a limitation of
the *preview* window of the Windows version. The preview does in absolutely
no way affect the output of the image. In order to view the output image,
you can open it in just about any image viewing program.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oleguer Vilella nous apporta ses lumieres ainsi en ce 2004-10-11 15:10... :
>What is "StretchDiBits() failed! Windows error!" ?
>Anyone know what does it mean? It appears with a big resolution render.
>
>Best regards,
>Oleguer
>
>
>
>
An error thrown by windows when it fails to successfully resize
something. It may cause a memory/resources leak. Are you using an old
version of WindowBlinds (V2.x or 3.x)? If so, set it to only skin the
titlebar of POV Ray.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I'm using Windows Millenium, it's old.
If I close the preview window all is correct, I realized this on summer.
Thanks,
Oleguer
news:416b492c$1@news.povray.org...
> Oleguer Vilella nous apporta ses lumieres ainsi en ce 2004-10-11 15:10...
:
>
> >What is "StretchDiBits() failed! Windows error!" ?
> >Anyone know what does it mean? It appears with a big resolution render.
> >
> >Best regards,
> >Oleguer
> >
> >
> >
> >
> An error thrown by windows when it fails to successfully resize
> something. It may cause a memory/resources leak. Are you using an old
> version of WindowBlinds (V2.x or 3.x)? If so, set it to only skin the
> titlebar of POV Ray.
>
> Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <416af912@news.povray.org>, tho### [at] trfde says...
> In article <416af462@news.povray.org> , "Oleguer Vilella"
> <ole### [at] infonegociocom> wrote:
>
> > Ah, Ok, maybe with Linux I don't have this problem. Have you ever trayed
> > with Linux?
>
> It does not make sense to get a preview for a 6400*4800 render. All it will
> do is consume a real lot of memory and slow down rendering.
>
> As I already pointed out, there is no problem, it is simply a limitation of
> the *preview* window of the Windows version. The preview does in absolutely
> no way affect the output of the image. In order to view the output image,
> you can open it in just about any image viewing program.
>
Sounds like a "What are scroll bars?" problem. lol Seriously though, I
use the preview window to see what I am doing, so I don't have to load
the image into a separate program to check it, which takes even more
memory and wastes the time needed to load the image besides (which on
that big of a file..). Lets just say I would be glad I have a relatively
fast computer. lol Having it bomb on a big image would be very annoying.
Thankfully I have never generated one that big, but it is an annoying
limitation never the less.
--
void main () {
call functional_code()
else
call crash_windows();
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |