Page 1 of 2

GZDoom 2.1.0 and 1.9.0 released

Posted: Sat Feb 06, 2016 9:01
by Graf Zahl
Here's the new versions that coincide with ZDoom 2.8.0. Actually, these have one bug less that was fixed shortly after the ZDoom release.

Re: GZDoom 2.1.0 and 1.9.0 (not yet) released

Posted: Sat Feb 06, 2016 9:18
by Rachael
No worries about the delayed release, thank you for doing this, as always. :)

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Sat Feb 06, 2016 9:33
by Tiger
Thank you for continued work on this engine! :D

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Sat Feb 06, 2016 9:37
by _mental_
Graf Zahl wrote:Actually, these have one bug less that was fixed shortly after the ZDoom release.
I guess it's about Heretic's time bomb issue. Will you update tags in git?

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Sat Feb 06, 2016 10:15
by Graf Zahl
Sure. I always forget to check the 'push tags' option.

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Mon Feb 08, 2016 8:35
by Amph
hi, i've tried the 2.1 build, but i dunno if it is the high resolution(1440p) all i'm getting is a black screen, when i set up the high resolution in-game

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Thu Feb 11, 2016 15:17
by l_johan_k
Hi!

I am using GZDoom 2.1.0-1 on Ubuntu 15.10 (64-bit).
When I try to load Project_Brutality_2.03.pk3 I get the following error:
JPEG failure: Wrong JPEG library version: library is 80, caller expects 62
terminate called after throwing an instance of 'int'
I have no problems loading brutalv20b.pk3.

Anyone who can help me with this problem?

regards,
ljohank

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Thu Feb 11, 2016 23:00
by Graf Zahl
Compile with the jpeg library that comes with the source. This should be settable through CMake.
This error is somewhat strange. Does this mean the library has become incompatible?

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Thu Feb 11, 2016 23:34
by l_johan_k
Hi,
thank you for the response.

I have just used the drd-team-ppa for the installation (deb http://debian.drdteam.org/).

One option would be that I just went back to version 1.8.7.

However, when I try to install, e.g., gzdoom1_1.8.7-1_amd64.deb 16-Oct-2015 from http://debian.drdteam.org/pool/multiverse/g/gzdoom1/ my system give me the following warning:
Lintian check results for /home/*****/gzdoom1_1.8.7-1_amd64.deb:
E: gzdoom1: maintainer-name-missing DRD Team [admin@maniacsvault.net]
E: gzdoom1: maintainer-address-malformed DRD Team [admin@maniacsvault.net]
Use of uninitialized value $name in pattern match (m//) at /usr/share/perl5/Lintian/Check.pm line 215.
E: gzdoom1: wrong-file-owner-uid-or-gid opt/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/brightmaps.pk3 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/gzdoom 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/gzdoom.pk3 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/libGLEW.so.1.9 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/libfmodex64-4.26.36.so 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/liboutput_sdl.so 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid opt/gzdoom/lights.pk3 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/bin/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/bin/gzdoom 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/share/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/share/applications/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/share/applications/gzdoom.desktop 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/share/pixmaps/ 1000/1000
E: gzdoom1: wrong-file-owner-uid-or-gid usr/share/pixmaps/gzdoom.png 1000/1000
Is it safe to continue with this installation?

regards,
ljohank

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Thu Feb 11, 2016 23:43
by Graf Zahl
I can't help ypu here, these packages were build by Blzut3.

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Fri Feb 12, 2016 0:05
by l_johan_k
Hi.

I will try to mail him.

regards,
ljohank

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Fri Feb 12, 2016 5:18
by Blzut3
Graf Zahl wrote:Does this mean the library has become incompatible?
Despite being a pretty common library, libjpeg is not an ABI stable library. Lots of distros started pushing libjpeg-turbo which besides being faster actually is ABI compatible.

Some of the distros stopped shipping libjpeg 6.2 so when I saw that libjpeg-turbo8 linked fine I assumed it was working. I'm looking into the issue since from what I recall reading libjpeg-turbo8 should provide compatibility with both ABIs, but I might be wrong.

Edit: Found the error. I was using the wrong header files on the 64-bit builds only. I'll upload new builds tomorrow.

Also my memory was a bit wrong on libjpeg-turbo vs libjpeg, but the point kind of remains: http://www.libjpeg-turbo.org/About/Jpeg-9
l_johan_k wrote:Is it safe to continue with this installation?
Yes. I'll be fixing this as well, but these errors are basically harmless considering what (G)ZDoom does. It's a result of me building the packages as non-root and no one complaining before in the years I've been doing it like that.

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Fri Feb 12, 2016 15:08
by l_johan_k
Great!
Thank you!

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Fri Feb 12, 2016 17:04
by l_johan_k
So the new version will be on the http://debian.drdteam.org/ ppa?

Re: GZDoom 2.1.0 and 1.9.0 released

Posted: Sat Feb 13, 2016 4:38
by Blzut3
l_johan_k wrote:So the new version will be on the http://debian.drdteam.org/ ppa?
Yes. It should be up now.