GL Errors in atlas (OOM 1285 and Invalid value 1282)

[Stan`]

Today I learnt that the map unit demo allows to display all the buildings in order to cache every texture. So I decided to try it. On the Vanilla Game I get à 1285 error and a 1282.

http://stackoverflow.com/questions/15722803/opengl-shader-error-1282

http://stackoverflow.com/questions/13376021/devil-ilload-error-1285

I also get some glitches on the mounted units.

Here is a screenshot (I have more models than you do cause I have mods enabled here)

[feneur]

Hmm, it's not 100% clear from your post whether or not you get the errors with just SVN as you first say with the vanilla game, and then at the screenshot mentions additional units from mods. I certainly don't get any such errors in the SVN version. (On Windows 7.)

Also, it would really be helpful if you would be more specific than "get some glitches". If it's difficult to describe in words, please take a screenshot of it, or possibly record a video if it's hard to tell in a screenshot.

[Stan`]

Don't you see the glitches on that screenshot ? The unit distorsion.

I'm using svn.

How many VRAM (GPU Memory do you have) I have 1GB.

[feneur]

I see some weird lines in the background if that's what you mean. I would suggest that you try deleting the cache to see if that fixes those though, or rather iirc that kind of thing (or at least what it looks like, it's not much one can see far in the distance there) usually is a sign that something is wrong with the cache.

I have 512MB VRAM (and 8GB RAM).

[Stan`]

Good to know that at least it's not because too many things get cached in the GPU. I'll see if I can get on IRC. Weirdly Enough the 1285 error is the one I get when doing the animation bug in atlas.

[historic_bruno]

You could use a tool like gDEbugger to run the game, and set it to break on detected GL errors. Then when you get the 1285 error, you can take a look at the GPU memory usage and see if anything sticks out (it will show everything in GPU memory: textures, shaders, FBOs, VBOs, etc).

[Stan`]

How can I set it up ?

[historic_bruno]

Assuming you're on Windows: Download and install it, create a new project with the wizard, point it to wherever your pyrogenesis.exe is, and accept all the defaults until it's finished. You can set a breakpoint with Breakpoints > Break on Detected Error. Then press F5 or clicking the green arrow will start the game as usual. Now at any time you can press F6 or use Debug > Break inside gDebugger to break into the debugger, or wait until there is an error and it will break automatically. I would recommend testing in windowed mode, not fullscreen.

Once you've broken into the debugger, View > Viewers > Graphic and Compute memory analysis viewer or Ctrl+Shift+M will open up a window that shows the GPU memory usage.

[Stan`]

It didn't break...

[Stan`]

It broke way after (in the background so the program popped up) Here is the ctrl-shift m data :

pyrogenesis-gDEBuggerGraphicMemoryData.7z

[historic_bruno]

Ah I see you got it working Thanks for providing the data! It's only textures? ~274 MB which is a lot but still much less than the 1GB you have, you might look at the other objects I mentioned (framebuffers, vertex buffers, shaders, etc) Maybe it doesn't break on out of memory errors :/

[Stan`]

Here is a detailed view. However that doesn't link the graphic card to be faulty...

[historic_bruno]

Can you see which texture #28 is? It may be obvious from looking at it, or you may have to look at a call stack for it. The "Graphic and Compute memory analysis viewer" should let you view the individual textures.