QB64 Phoenix Edition
Error 1285 - gluBuild2DMipmaps failed ? - Printable Version

+- QB64 Phoenix Edition (https://qb64phoenix.com/forum)
+-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1)
+--- Forum: Code and Stuff (https://qb64phoenix.com/forum/forumdisplay.php?fid=3)
+---- Forum: Help Me! (https://qb64phoenix.com/forum/forumdisplay.php?fid=10)
+---- Thread: Error 1285 - gluBuild2DMipmaps failed ? (/showthread.php?tid=2722)



Error 1285 - gluBuild2DMipmaps failed ? - madscijr - 05-21-2024

I left 2 instances of the QB64PE IDE (v3.10.0 - guess I'm due for an update!) 
open with the program A and program B code listed here
and when I opend my PC today, saw 2 alert boxes open saying "gluBuild2DMipmaps failed.png:  1285". 
Clicking OK on either of them just re-opens the popup, and I ended up having to kill QB64PE to make them go away. 

Does anyone recognize this error message as indicating something specific, that might help track down the cause? 

   


RE: Error 1285 - gluBuild2DMipmaps failed ? - DSMan195276 - 05-21-2024

The 1285 means OpenGL reported an 'out of memory' error, and that message itself gets thrown if OpenGL fails when creating a new Hardware image (probably for the screen redraw, so hence why it just keeps popping back up). I think it means vram, but it's not super clear, and that probably depends on the particular system and setup anyway.

When you killed QB64PE did you happen to take a look at memory usage? And did you have the A and B programs running?


RE: Error 1285 - gluBuild2DMipmaps failed ? - madscijr - 05-21-2024

(05-21-2024, 04:11 PM)DSMan195276 Wrote: The 1285 means OpenGL reported an 'out of memory' error, and that message itself gets thrown if OpenGL fails when creating a new Hardware image (probably for the screen redraw, so hence why it just keeps popping back up). I think it means vram, but it's not super clear, and that probably depends on the particular system and setup anyway.

When you killed QB64PE did you happen to take a look at memory usage? And did you have the A and B programs running?
Thanks for your reply - I did not look at the memory usage, but the a & b programs were not running as far as I could see. If the error pops up again, I'll be sure to check the memory usage. 
Thanks again!