Screenshot corruption in OpenGL mode

General help and assistance forum.
Post Reply
charcola
New User
Posts: 6
Joined: Wed Sep 12, 2012 8:13 pm

Screenshot corruption in OpenGL mode

#1

Post by charcola » Fri Sep 14, 2012 11:31 am

Basically the above. Playing on an hp 3105m netbook with opengl enabled at 1366x768, taking a screenshot results in this:

Image

Screenshots look fine in software mode. I haven't done much testing or fiddled with settings, and the game itself runs fine, it just seems to have this problem taking screenshots with Zandronum for whatever reason. skulltag seems to take screenshots just fine in openGL.

Qent
Retired Staff / Community Team Member
Posts: 1424
Joined: Tue May 29, 2012 7:56 pm
Contact:

RE: Screenshot corruption in OpenGL mode

#2

Post by Qent » Fri Sep 14, 2012 1:23 pm

I believe screenshots don't work at that resolution. I'm curious how it works on Skulltag though, since this problem was long before Zandronum. Are you running Skulltag at 1366x768, too?

DoktorNuts
New User
Posts: 3
Joined: Wed Sep 12, 2012 10:00 pm
Location: Chile

RE: Screenshot corruption in OpenGL mode

#3

Post by DoktorNuts » Fri Sep 14, 2012 2:05 pm

I have the same problem, and i'm running Zandronum at 1366x768, however, programs like FRAPS don't have this problem when taking screenshots in Zandronum.
Qent wrote: I believe screenshots don't work at that resolution. I'm curious how it works on Skulltag though, since this problem was long before Zandronum. Are you running Skulltag at 1366x768, too?
Yes, Skulltag had the same problem, but GZDoom doesn't, even running at the same resolution.

Bloax
Forum Regular
Posts: 411
Joined: Mon Jun 04, 2012 5:11 pm

RE: Screenshot corruption in OpenGL mode

#4

Post by Bloax » Fri Sep 14, 2012 3:17 pm

It was fixed some time ago, had something to do with resolutions not being mod4 and thus bugging out due to a performance optimization. (Or shall we say non-degradation.)

Llewellyn
Forum Regular
Posts: 578
Joined: Mon Jul 02, 2012 7:12 am

RE: Screenshot corruption in OpenGL mode

#5

Post by Llewellyn » Fri Sep 14, 2012 3:28 pm

What I would do is either:
Try to load your INI from Skulltag to see if it has the same problems
AND
Try a fresh ini and change settings on-and-off until you can find the specific setting that causes this problem, so we can attempt to reproduce it on our end (with an appropriate bug report when the problem is located.)

Bloax
Forum Regular
Posts: 411
Joined: Mon Jun 04, 2012 5:11 pm

RE: Screenshot corruption in OpenGL mode

#6

Post by Bloax » Fri Sep 14, 2012 3:30 pm

No, the problem is the resolution itself. 1366/4 = 341>.5<

And if my fuzzy memory serves, it lies in the way the screenshots are taken.
Last edited by Bloax on Fri Sep 14, 2012 3:31 pm, edited 1 time in total.

User avatar
Combinebobnt
Retired Staff / Community Team Member
Posts: 1905
Joined: Mon Jun 04, 2012 3:37 am
Location: Earth
Contact:

RE: Screenshot corruption in OpenGL mode

#7

Post by Combinebobnt » Fri Sep 14, 2012 8:57 pm

use 1360x768

charcola
New User
Posts: 6
Joined: Wed Sep 12, 2012 8:13 pm

RE: Screenshot corruption in OpenGL mode

#8

Post by charcola » Fri Sep 14, 2012 10:40 pm

Looks like changing to 1360x768 solved it. Strange though, I could have sworn that I didn't see that mode available as an option the last time I tried checking the resolution options.

I think Skulltag must have been using a different setting as well, it was using 1280 x 768, yeah.

User avatar
President People
Forum Regular
Posts: 394
Joined: Tue Jun 05, 2012 8:12 am

RE: Screenshot corruption in OpenGL mode

#9

Post by President People » Sat Sep 15, 2012 4:20 am

This is clearly the work of Slenderman. Don't turn around, charcola.
Image
***MARATHON SKINS PACK V1.0.7***

I have been Roland, Beowulf, Achilles, Gilgamesh.
I have been called a hundred names and will be called
a thousand more before the world goes dim and cold.

User avatar
Torr Samaho
Lead Developer
Posts: 1543
Joined: Fri May 25, 2012 6:03 pm
Location: Germany

RE: Screenshot corruption in OpenGL mode

#10

Post by Torr Samaho » Sat Sep 15, 2012 7:38 pm

It's a GZDoom bug that has been fixed in GZDoom but is still in Zandronum, see the tracker ticked: http://zandronum.com/tracker/view.php?id=920

Post Reply