Package Details: gzdoom 4.14.0-1

Git Clone URL: https://aur.archlinux.org/gzdoom.git (read-only, click to copy)
Package Base: gzdoom
Description: Feature centric port for all Doom engine games
Upstream URL: http://www.zdoom.org/
Licenses: GPL3, BSD, LGPL3
Replaces: gzdoom-legacy, gzdoom1
Submitter: None
Maintainer: xente
Last Packager: xente
Votes: 167
Popularity: 2.60
First Submitted: 2009-02-22 22:28 (UTC)
Last Updated: 2024-12-18 19:14 (UTC)

Dependencies (27)

Sources (4)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 Next › Last »

oyunnhagland commented on 2013-08-10 22:17 (UTC)

The fmod source url has changed, please update to: http://www.fmod.org/download/fmodex/api/Linux/fmodapi${_fmodver}${_fmodarch}.tar.gz

miffe commented on 2013-07-17 17:06 (UTC)

/usr/bin/makepkg: line 583: git: command not found Please add git to makedepends

z33ky commented on 2013-03-31 16:57 (UTC)

I have not had gzdoom installed before. I tried rebuilding, but that didn't fix it. I will try the zdoom forums, as I get the same problem there it seems likely that gzdoom inherits whatever is wrong from it. http://forum.zdoom.org/viewtopic.php?f=2&t=35866

grubber commented on 2013-03-31 09:02 (UTC)

I was not able to reproduce that. But it seems like if you were using gzdoom.pk3 from a different version of gzdoom.

z33ky commented on 2013-03-30 15:37 (UTC)

That fixes the paths, but the Script errors remain. Tested with The Ultimate Doom, Doom 2 and the Doom demo (doom1-wad in AUR).

grubber commented on 2013-03-30 14:31 (UTC)

It was a bug in the package(s), which caused initial config file to point at a wrong path to look for gzdoom.pk3. Remove the bad config file in ~/.config/gzdoom and gzdoom will generate a new one for you.

z33ky commented on 2013-03-28 00:19 (UTC)

$ gzdoom GZDoom v1.7.1 - SVN revision 0 - SDL version Compiled on Mar 28 2013 Using video driver x11 M_LoadDefaults: Load system defaults. Cannot find gzdoom.pk3 $ cd /usr/share/games/gzdoom $ gzdoom GZDoom v1.7.1 - SVN revision 0 - SDL version Compiled on Mar 28 2013 Using video driver x11 M_LoadDefaults: Load system defaults. Gameinfo scan took 0 ms Cannot find a game IWAD (doom.wad, doom2.wad, heretic.wad, etc.). Did you install ZDoom properly? You can do either of the following: 1. Place one or more of these wads in the same directory as ZDoom. 2. Edit your zdoom-username.ini and add the directories of your iwads to the list beneath [IWADSearch.Directories] $ DOOMWADDIR=~/.gzdoom gzdoom GZDoom v1.7.1 - SVN revision 0 - SDL version Compiled on Mar 28 2013 Using video driver x11 M_LoadDefaults: Load system defaults. Gameinfo scan took 0 ms W_Init: Init WADfiles. adding ./gzdoom.pk3, 583 lumps adding /home/z33ky/.gzdoom/doom.wad, 2306 lumps I_Init: Setting up machine state. CPU Vendor ID: GenuineIntel Name: Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz Family 6, Model 37, Stepping 2 Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 I_InitSound: Initializing FMOD FMOD Sound System, copyright � Firelight Technologies Pty, Ltd., 1994-2009. Loaded FMOD version 4.26.36 HOSS could not be initialized. Trying ALSA. V_Init: allocate screen. S_Init: Setting up sound. ST_Init: Init startup screen. Checking cmd-line parameters... S_InitData: Load sound definitions. G_ParseMapInfo: Load map definitions. GScript error, "gzdoom.pk3:mapinfo/doom1.txt" line 54: GUnknown property 'sucktime' found in map definition ... and lots more of those Script errors, Unknown property. In the end it won't start. The selection window does show and I selected the doom.wad, then these errors spew and that's it. Same with gzdoom-svn and zdoom. Should I take this upstream? If so, to GZDoom or ZDoom?

grubber commented on 2012-12-30 10:07 (UTC)

Fixed. I wish there was a better way of handling per-arch source files.

miffe commented on 2012-12-30 03:42 (UTC)

Fails to build since the PKGBUILD has the same md5sum for both the i686 and x86_64 version of fmod.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 Next › Last »