News | Forum | People | FAQ | Links | Search | Register | Log in
Quakespasm Engine
This engine needs its own thread.

Feedback: I like the OS X version, but I have to start it from the terminal for it to work and can't just double-click it like a traditional OS X app. I'm sure you guys already know this, either way great engine.

http://quakespasm.sourceforge.net/
First | Previous | Next | Last
Gl_affinemodels 
(Theoretically) enables or disables perspective-correct texturing for MDLs. Set to 1 to disable perspective-correction, 0 to enable it.

See http://en.wikipedia.org/wiki/Texture_mapping#Perspective_correctness for an example of what effect perspective-correct terturing can have.

So, enabling it (gl_affinemodels 0) can be better quality but at a performance loss; disabling it (gl_affinemodels 1) better performance but at a quality loss.

Important note coming up.

This is a HINT. That means you're telling the driver "this is the setting I'd prefer if you can do it but I'm not going to lose sleep over it if you can't"; as in - drivers are not obliged to obey hints; some may ignore them completely and give you performance or quality depending on their own internal settings (and possibly driver control panel settings).

See http://www.opengl.org/sdk/docs/man/xhtml/glHint.xml for more.

So for a preference for quality set it to 0, but don't depend on that having any effect and don't get annoyed or waste time figuring why it's not working if it doesn't work. 
V0.85.8 
Thanks! This release works for me on OS X 10.8 (the switch to libmad I guess?) 
@ericw RE: V0.85.8 
If you were unable to run the previous versions, then yes, possibly the switch from mpg123 to libmad helped you. I took care not to having any foreign dependency and packaged all needed libraries in the binary distribution. 
OS X Version 
szo,

why aren't there any antialiasing (FSAA) options ?

And what about the ability to put the app in background, as in Quake3, using command-H ? 
 
Once you ask ten times a glowing fairy appears, says ello guys, waves his fabulous magic-stick and those features will exist. 
I'm On Windows 
I don't get AA options on ANY engines, except for DP. Radeon FTF. 
Re: FSAA 
Command-H backgrounding and FSAA support added to TODO list for the next release. 
Vsync Setting Is Behaving Strange 
hello,

i've noticed that i can disable vertical sync only via ingame menu, and it automatically resets to enabled every time i start the engine. quakespasm seems to ignore "vid_vsync 0" variable stored in autoexec.cfg as well as command "+vid_vsync 0" in bat file. still, i can turn off vsync during the game session via menu, it works until i close the program. i've checked config.cfg, cvar is set to 0 there, anyway autoexec and launch parameter should override it afaik

i'm currently using latest quakespasm release 0.85.8 for windows.

my sys specs:
windows 7 x64
amd phenom II quad-core processor
nvidia geforce gtx660 ti with the latest 306.23 drivers

i've checked setting in nvidia control panel as well, quakespasm is shurely allowed to control swap interval

thx to developers for great engine anyways =) 
NVIDIA Control Panel 
From their help text on vsync:

...turn Vertical sync on and off in the NVIDIA Control panel for OpenGL games... 
RE: NVIDIA Control Panel 
thx for answer.

so this behavior is purely a driver feature from NVIDIA, did i get it right? looks strange, because darkplaces, e.g., is opengl engine as well, but it seems to apply vsync cvar correctly on the startup. 
Re: Vsync Setting Is Behaving Strange 
That's a bug you found there. I just pushed a change to svn (r778) that should fix it. Can you test it and report the results? (My card doesn't support vsync toggling so I can't test it myself.) 
@ Svdijk 
would be glad to help, but unfortunately i'm not familiar with code compiling at all =( 
 
Raspberian (I guess from Debian actually) repo has some patches you guys might consider bug reports (linking and some minor hurd things): http://archive.raspbian.org/raspbian/pool/main/q/quakespasm/ 
@pat0gen 
@pat0gen 
@ Svdijk: Vsync Bug 
nope, didn't work for me. everything is like before, had to use nv control panel to disable vsync permanently.
new console message appears on startup, however: "Cvar_Set: variable vid_vsync not found" 
Re: Vsync Bug 
That message appeared in r778 because of a sloppy mistake of mine, but it shouldn't be occurring in the updated r779 that I posted; did you try that second link? 
Re: Vsync Bug 
oops, missed the update somehow, my bad. but no, r779 hasn't solve the problem either. 
Re: Vsync Bug 
OK, one more: http://quakespasm.sourceforge.net/tmp/qs_r780_win32.zip

If this doesn't fix it, is there anywhere off-forum where I can contact you so we can stop spamming this thread? 
Re: Vsync Bug 
all the same with this rev(
here, my postbox:
seraph[dot]divine[dot]sd[at sign]gmail[dot]com 
 
Trying to save in its (http://www.celephais.net/board/view_thread.php?id=60875) gives me a segfault: https://pastee.org/s6a23

Built from SVN a while ago:
QuakeSpasm 0.85.9 (c) Ozkan Sezer, Stevenaaus
Exe: 12:41:37 Nov 14 2012
FITZQUAKE 0.85 SERVER (38429 CRC) 
 
Yeah 
same here. Relevant portion of stack trace:


0 libsystem_kernel.dylib 0x00007fff895ad212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff91413af4 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff91457e9e __abort + 159
3 libsystem_c.dylib 0x00007fff9141971d __chk_fail + 35
4 libsystem_c.dylib 0x00007fff914198f8 __sprintf_chk + 201
5 net.sf.quakespasm.QuakeSpasm 0x000000010004e9da PR_UglyValueString + 170
6 net.sf.quakespasm.QuakeSpasm 0x000000010004f3e2 ED_WriteGlobals + 194
7 net.sf.quakespasm.QuakeSpasm 0x000000010004a0b9 Host_Savegame_f + 761
8 net.sf.quakespasm.QuakeSpasm 0x00000001000402b4 Cbuf_Execute + 196
9 net.sf.quakespasm.QuakeSpasm 0x0000000100044682 _Host_Frame + 82
10 net.sf.quakespasm.QuakeSpasm 0x000000010005dd85 SDL_main + 549 
@Spirit, @SleepwalkR 
Save crash should now be fixed in the svn as of rev. 791. 
 
What is your command line ?
Can't you save game at all ? I can't reproduce this. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.