Hmm... the numpad seems to work for me under linux and winXP, so i'm not sure what the problem might be.

We have been fixing networking code (cheers SleepwalkR). You can check-out subversion, or try this recent win32 binary
http://quakespasm.sourceforge.net/tmp/quakespasm-20100821.exe 

w7/multicore timing bug = Sys_FloatTime

Sys_DoubleTime should replace it in FitzQuake 0.85. The SDL version including FitzQuake SDL 0.80 doesn't have this issue just due to the alterations and the SDL.net library or at least FitzQuake SDL's implementation of it.

Clock fixed NQ engines = DarkPlaces, JoeQuake, Qrack, ProQuake. All QW engines have the fix.

A symptom of the problem: demos play all jerky. 

Dear Quakespasm team,

your website is confusing and awkward to use. I have to hover the links to find out what hides behind the pretentious names. When there is text and links mixed, the text stands out more, suggesting it is a link. 

Ha ha.. i made the cd player to work in dedicated mode. quakespasm -dedicated -cd inits the sound and cd subsystems. Also added "cd next" and "cd prev" commands... It's only about 20 lines of bloat, but SDL is so common and works mostly that this is quite handy for me. I should reinstall QNX and see if i can get it going there. Baker.. what do you think ?? The code's in svn, and i've updated the above windows bin too.

I figured out the windows device format too for when it doesn't get auto-detected. It's something like quakespasm -cddev F:\ 

I should reinstall QNX and see if i can get it going there. Baker.. what do you think ??

No clue what QNX is, well except Googling it.

I'm not very Linuxy, although I am very adaptable. 

Nah..i'm just wondering about the uselessness of a quake/sdl command-line cd player. It advances tracks now, though it's possible i've broken something somewhere. 

I'm wondering about that, too. What's the point? 

A few lines of code saves me installing bloatware like microsoft mplayer just to play CDs. 

but I don't care either way. Just don't turn QS into an emacs clone. 

0.85.3 is up downloads, changes.
Nothing major, mainly just the networking stuff previously mentioned. 

For people with newish systems (Xorg >= 7.5) and broken brightness slider, these patched libSDL binaries should hopefully fix the thing.

libSDL 32 bit
libSDL 64 bit

I guess there could be side effects, as it's not officially included with libSDL. 

Hello everyone. Only recently decided to venture into Quake once more. It's been since.....well it's been too long. DOS! I'm amazed at all the work that has been done, especially the engines and I've tried more than a few and Quakespasm comes out on top as far as I'm concerned but there is one thing that's bugging me and I can't seem to find the answer or their isn't one.
I'm running the Linux and Quakespasm performs outstanding for the most part but I have no statusbar....Any ideas how to enable it? I've Googled for several days and read countless documents....no joy. Any help would be appreciated. 

try viewsize 100 at the console

then you can use scr_sbarscale to adjust the size.. (1 being normal, 2 being twice as big.. 1.5 also works) and you can also use scr_sbaralpha 0.99 (instead of 1) to get it to sit 'in' the view rather than below it, which imo feels nicer

quakespasm is basically a modified fitzquake, so having a copy of the FQ readme is helpful for commands n stuff: http://www.celephais.net/fitzquake/ 

Great that works. I knew there must have been a command somewhere. I was assuming it would be under scr_something. Now how to get it to persist. What would I put in my .cfg file?
Yea I did look over what documents were available but I would never have seen the relationship between the two. Good man. I had already figured out the size and alpha blending but the non-appearance of the bar was a mystery. 

i just have an autoexec.cfg file in id1 which sets it each time. you may be familiar with them but if not, it's basically just a list of commands fired each time you start quake, regardless of mod 

*familiar with that. i know what i meant 

I had edited that but edited as view "100" rather than viewsize "100", which I had correctly entered in my config.cfg file. I have corrected my autoexec.cfg file and all is well. Thanks a million. This has led me to search for other commands to finesse my configs...which I find are numerous and make Quake a very personal experience. 

Another question.....the speed I have set as..
_cl_forwardspeed "999"
but that has no noticeable effect. It's still not fast enough for my taste. Syntax correct? 

you must also change sv_maxspeed 

I don't have a sv_maxspeed listed in my configs.
Is the syntax as you have written correct and in what increments is it set? 

Where can I find a farly definitive autoexec.cfg guidline/turotial? 

Ahem! tutorial 

Nevermind...found it. Took some digging as most posted configs re for the newer versions. Thanks to those who helped. 

Generally you do not need a autoexec.cfg. If your engine does not work well without one (ie forgetting its settings) tell the authors about it. Usually one only needs it to work around engine's overwriting each others settings or not even saving them in the first place.

You can set the "proper" movement speed by setting "Always Run" to "yes" in the menu. That would set the right sv_*speed. If the viewsize is so big it does not show the HUD by default it should be considered as a bug. Maybe you had an existing config.cfg that was the culprit for this? 

Points well taken...thanks. That has been my a question of mine...why have both config files.