I have done the following experiment to demonstrate my problem:
I am running in runlevel without X.
I have started Xwrapper; xterm and quake-sdl only
(No gnome or winmanager, only agetty’s, bash, XF86_S3, xterm and
sdl-quake)
The sounds in quake-sdl are fragmented or come late
after events.
Does anybody else suffer from these kind of problems ?
Thanks
Update for my previouse message:
I have pgcc-2.95.3 compiler and almost all the programs I am
compiling with “-mk6 -O2” cflags.____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
I have done the following experiment to demonstrate my problem:
I am running in runlevel without X.
I have started Xwrapper; xterm and quake-sdl only
(No gnome or winmanager, only agetty’s, bash, XF86_S3, xterm and
sdl-quake)
The sounds in quake-sdl are fragmented or come late
after events.
What resolution are you running quake at?
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
What resolution are you running quake at?
-Sam Lantinga (slouken at devolution.com)
I am running it at 640x480 and have tried lower (320x200, …) - it does
not change a thing.
Changing X resolution also doesn’t help.
I still want to emphasize that the problem appears when I am starting
quake-sdl from
within X, even if it is THE ONLY PROGRAM RUNNING (bash; XF86_S3;
quake-sdl - read
my previous message).
Here is again output from top:
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME
COMMAND
232 Mic 18 0 11524 11M 2212 R 0 69.5 18.2 0:07
quake-sdl
124 root 9 0 11960 10M 2344 R 0 34.4 16.6 1:14 X
231 Mic 13 0 1032 1032 852 R 0 0.9 1.6 0:00 top
1 root 0 0 472 472 412 S 0 0.0 0.7 0:04 init
2 root 0 0 0 0 0 SW 0 0.0 0.0 0:00
kflushd
3 root 0 0 0 0 0 SW 0 0.0 0.0 0:00
kupdate
4 root 0 0 0 0 0 SW 0 0.0 0.0 0:00 kpiod
5 root 0 0 0 0 0 SW 0 0.0 0.0 0:00
kswapd
28 root 0 0 688 688 552 S 0 0.0 1.0 0:00
syslogd
31 root 0 0 676 672 324 S 0 0.0 1.0 0:00 klogd
42 root 0 0 584 584 492 S 0 0.0 0.9 0:00 crond
45 uucp 0 0 268 264 204 S 0 0.0 0.4 0:00
portmap
48 root 0 0 392 384 324 S 0 0.0 0.6 0:00 gpm
50 root 0 0 616 616 576 S 0 0.0 0.9 0:00 xfstt
53 root 0 0 412 412 352 S 0 0.0 0.6 0:00
agetty
54 root 0 0 412 412 352 S 0 0.0 0.6 0:00
agetty
55 root 0 0 412 412 352 S 0 0.0 0.6 0:00
agetty
56 root 0 0 412 412 352 S 0 0.0 0.6 0:00
agetty
The problem is only with sounds. Video is very fine.
It sounds like when there are many sounds - some sounds are started and
then interrupted
by others and then continued and so on …
But there is no problems when I am running it from console and no
problem with sdlquake.
So maybe it is a problem with quakeforge, but I have get slight sound
interrupts in
Amphetamine 0.8.8 .
Thanks
But there is no problems when I am running it from console and no
problem with sdlquake.
So maybe it is a problem with quakeforge, but I have get slight sound
interrupts in Amphetamine 0.8.8 .
It sounds like a problem in quakeforge, so I’ll take a quick look when I can.
In the meantime, can you try Maelstrom and see if you have the same problem?
http://www.devolution.com/~slouken/Maelstrom/
See ya,
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
The problem is only with sounds. Video is very fine.
It sounds like when there are many sounds - some sounds are started and
then interrupted
by others and then continued and so on …
But there is no problems when I am running it from console and no
problem with sdlquake.
I had the same problem in windows but the graphics didn’t look as sharp as
they did in linux. I have an Nvidia card which isn’t supported yet. The
windows version had messed up graphics on my machine too. I am about
ready to toss the video card out.!!!
Dave
Hello Sam !
I have tried Maelstrom - Very impressive !!!
There were no problems with sounds or video (Even with esound !!!).
So I think that the problem is in quakeforge or when there is more then
4 sounds
simultaneously.
One question about Maelstrom: why can not I stop it with ^C from xterm I
have started it ?
Is it normal behavior ?
(Even in sdlquake STARTED FROM X there were very very little
disturbances, when
the number of enemies on was more then 4).
Thanks.
One question about Maelstrom: why can not I stop it with ^C from xterm I
have started it ?
Is it normal behavior ?
Ctrl-C by default sends an SDL_QUIT message to the program, which may or
may not be interpreted as a quit request. If you want to hard-abort an SDL
program, use Ctrl-, which sends a SIGQUIT signal on UNIX.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
program, use Ctrl-, which sends a SIGQUIT signal on UNIX.
just out of curiosity, why CTRL-? Is there something special about this
combination?–
Daniel Vogel My opinions may have changed,
666 @ http://grafzahl.de but not the fact that I am right
Sam Lantinga wrote:
program, use Ctrl-, which sends a SIGQUIT signal on UNIX.
just out of curiosity, why CTRL-? Is there something special about this
combination?
No, ^\ is just the traditional key that causes the tty driver to send
a SIGQUIT. I think it is from Unix V6, but I’m not sure.
In other words, it has nothing to do with SDL or even X11. It will work on
a serial vt52, if you have one
Mattias Engdeg?rd wrote:
No, ^\ is just the traditional key that causes the tty driver to send
a SIGQUIT. I think it is from Unix V6, but I’m not sure.
Nice to know, thanks :)–
Daniel Vogel My opinions may have changed,
666 @ http://grafzahl.de but not the fact that I am right
Sam Lantinga wrote:
program, use Ctrl-, which sends a SIGQUIT signal on UNIX.
just out of curiosity, why CTRL-? Is there something special about this
combination?
I never knew about this keystroke! Cool!
As for why CTRL-? Sam didn’t pick it - it’s a Unix thing. (As he said,
it sends a SIGQUIT signal to the process.)
-bill!