RE: NAT Issue On 0.85.7 Under Debian Squeeze
#386 posted by egre on 2012/07/23 12:15:15
Here's the client log output
http://pastebin.com/uSy5r5cb
Port 26000 UDP is assigned by me.
Port 60982 UDP is randomly assigned each time the program executes.
I see nothing in the documentation regarding a second UDP port being configured or configurable. If someone could clue me in, I'd be very grateful.
Thanks in advance.
RE: NAT Issue On 0.85.7 Under Debian Squeeze
#387 posted by egre on 2012/07/23 13:05:02
Here's some more on the UDP port assigns:
http://pastebin.com/sr3LH8Qu
I get where the 26000 is assigned, but why the other port number? Why is it random each time?
OpenBSD
#388 posted by LeopolD on 2012/07/23 18:58:12
Just compiled it on OpenBSD, runs fine, awesome.
However the Makefile failed at detecting the os, had to set it to OpenBSD by hand, after that everything was good:)
#389 posted by AAS on 2012/08/04 07:38:00
Any thoughts about crashing on OS X 10.8?
Crash log: http://pastebin.com/wz1M1Mcb
#390 posted by anonymous user on 2012/08/04 12:04:22
Hmmm - it can't find libltdl.7.dylib
It'd be better if we'd linked to libltdl.dylib. Try something like
sudo bash
cd /usr/lib
ln -s libltdl.dylib libltdl.7.dylib
#391 posted by anonymous user on 2012/08/04 12:23:53
Actually, it seems libltdl is indirectly linked ... So maybe it's a mountain lion issue
Use "otool -L libmpg123.dylib" to follow the library dependancies
#392 posted by AAS on 2012/08/04 13:21:39
Thanks for the reply. Making symlink didn't solve the problem (there are not any libltdl* files in /usr/lib/).
Here is an otool output:
libmpg123.dylib:
@executable_path/../Resources/libmpg123.dylib (compatibility version 26.0.0, current version 26.0.0)
/usr/lib/libltdl.7.dylib (compatibility version 9.0.0, current version 9.2.0)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version 315.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.1)
#393 posted by anonymous user on 2012/08/05 02:22:40
Yes - it appears libltdl has changed or something... but can't sort it out for myself. Apple are getting pretty aggressive with their OS upgrades at the moment. Lion was the shortest lived OSX ever. ... I might stick with snow leopard till there's a reason to upgrade.
Perhaps try this ?
On 10.8 I solved this issue with:
brew install libtool
brew link libtool
https://github.com/mxcl/homebrew
#394 posted by AAS on 2012/08/05 08:42:44
Thank you, now it is works.
Already had homebrew installed but didn't realize that I could install missing lib myself :)
V0.85.8
#395 posted by szo on 2012/10/08 10:33:56
Version 0.85.8 of QuakeSpasm is released:
* Made Quake shareware 1.00 and 1.01 versions to be recognized properly.
* Fixed control-character handling in unicode mode. Keyboard input tweaks.
* Made the keypad keys to send separate key events in game mode.
* Text pasting support from OS clipboard to console. (Windows and Mac OS X.)
* Support for the Apple (Command) key on Mac OS X.
* Fixed increased (more than 32) dynamic lights.
* Music playback: Made sure that the file's channels count is supported.
* Support for Solaris.
* Switched to using libmad instead of libmpg123 for MP3 playback on Mac OS X.
* Better support for building the Mac OS X version using a makefile, support for cross-compiling on Linux.
* Fixed a minor intermissions glitch.
* Increased string buffer size from 256 to 384 for PF_VarString to work around broken mods such as UQC.
* Restored original behavior for Quake registered version detection.
* Minor demo recording/playback tweaks.
* Minor tweaks to the scale menu option.
* unbindall before loading stored bindings (configurable by new cvar cfg_unbindall, enabled by default.)
* New icon.
* Miscellaneous source code cleanups.
FSAA ?
#396 posted by Barnak on 2012/10/16 23:14:39
And what about support for FSAA (antialiasing) on OS X ?
And what about the command-H option to switch the app into background, as in Quake3 ?
Gl_affinemodels
#397 posted by TempesT on 2012/10/17 00:26:26
I have searched google trying to figure out what this command does, but have found contradicting answers. I'm making a high quality config that will render quake to look the best that it possibly can. I know that it has to deal with perspective correction on player models, but I don't know which value will effect this change. I want the models to have maximum quality so what should gl_affinemodels be set as? 1 or 0?
I Looked At The Code.
#398 posted by czg on 2012/10/17 00:42:43
0
W00t
#399 posted by TempesT on 2012/10/17 01:31:18
Thank you very much czg.
Gl_affinemodels
#400 posted by mh on 2012/10/18 02:46:46
(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
#401 posted by ericw on 2012/10/18 16:21:33
Thanks! This release works for me on OS X 10.8 (the switch to libmad I guess?)
@ericw RE: V0.85.8
#402 posted by szo on 2012/10/18 17:05:17
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
#403 posted by Barnak on 2012/10/18 20:30:23
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 ?
#404 posted by Spirit on 2012/10/18 21:06:12
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
#405 posted by RickyT33 on 2012/10/19 01:05:03
I don't get AA options on ANY engines, except for DP. Radeon FTF.
Re: FSAA
#406 posted by szo on 2012/10/19 10:21:35
Command-H backgrounding and FSAA support added to TODO list for the next release.
Vsync Setting Is Behaving Strange
#407 posted by pat0gen on 2012/10/31 19:27:15
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
#408 posted by mh on 2012/11/01 02:04:40
From their help text on vsync:
...turn Vertical sync on and off in the NVIDIA Control panel for OpenGL games...
RE: NVIDIA Control Panel
#409 posted by pat0gen on 2012/11/01 11:52:30
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
#410 posted by svdijk on 2012/11/01 18:36:44
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.)
|