On Sun, May 22, 2011 at 12:42:50AM +0300, Antti Harri wrote:
> On Saturday 21 May 2011 21:05:25 Jacob Meuser wrote:
> > On Sat, May 21, 2011 at 02:56:36AM -0700, Ryan Freeman wrote:
> > > - sound is slightly modified snd_sndio.c from the games/quake port
> > > (works actually better than existing quake port which has dreadful
> > > audio sounding like its being overdriven by 100dB) i blame something
> > > in the old ver of quakeforge over Jacob's snd_sndio.c ;)
> >
> > wtf?  sound is indeed majorly mangled.  this used to work perfectly.
> >
> > hmm, cc -O2 -pipe -pthread -Wall -Did386=0 -O2 -pipe -pthread -Wall -Wall
> > -DQUAKEWORLD -Wall -O6 -ffast-math -funroll-loops -fomit-frame-pointer
> > -fexpensive-optimizations ...
> >
> > maybe gcc4 does something different with those switches than gcc3 did?
> 
> My hardware has changed but yeah last time I checked too it was working fine.
> 
> The attached diff makes quake honour CFLAGS again. The --enable-release
> didn't seem to be linked to anything else than enabling some GCC optimization
> flags. The extra flags don't seem to be the fault here though.
> 
> Adjusted also the license marker. There are lots of other stuff I could
> do with the port, but I'm waiting to see what happens with tyr-quake first. 
>

I should note that while we are using a rather old dist of quakeforge,
according to quakeforge.net there is activity trying to happen. The appeal
of tyr-quake to me was that it has a 'mission statement' so to speak of
similar proportions to chocolate-doom; that is to be conservative, only
fixing serious bugs but trying to maintain true to the original quake src.

One thing additional to tyr-quake i did notice and forgot to mention with
the post; there is no video menu. there is code in various places for it
(menu.c) but its not actually displayed, and opening console and typing
menu_video promptly crashes the game. having used tyr-quake for over 2
years on OpenBSD now with no sound until last night, i had gotten real
used to always using -width and -height. 

-ryan 

Reply via email to