Enemy Territory: Quake Wars v1.2 Update
The version 1.2 client for QuakeWars: Enemy Territory has been updated by
- voice chat support (OSS and Alsa backends)
- OSS sound: fixed the dsp device from s_dsp -> s_device
- s_noMic to skip the mic init / voice input
- by default, don’t require Ctrl+Alt+~ for console toggle
- r_useThreadedRenderer hardcoded to 0 - is not supported in the Linux build atm
- cleanup and simplify the frame timing code, hopefully fixing the fps banding problems
- fix showFPSBandings crash, com_showFPS needs to be enabled
- make SIGHUP shutdown more explicit, as it’s not a crashbut rather a requested shutdown (controlling terminal exited)
- set r_useFBODestinationBuffer to 0 when detecting an NVidia card(required for 5700 series otherwise performance degrades too much)
- misc updates to fix potential gamecode crashes
- add zpaks to the setups
There was also a server update recently to fix a threading issue. ETQW is a multiplayer-oriented first-person shooter developed by Splash Damage set prior to Quake 2 during the Strogg invasion of Earth.
Here are a few recent documentation updates and articles of note:
- Beyond3D, withassistance from Splash Damage, examined ETQW’sMegaTexture technology.
- A guest blog entry at the official
- The author of the previous article also maintains the
Download: [ enemyterritory.com (mirror list) ]
November 20th, 2007 at 7:33 pm
I don’t see any options in the sound configuration settings,, at any rate thanks for the patch timmo!
November 20th, 2007 at 7:56 pm
You’ll have to go into the Options -> Controls -> Miscellaneous tab and bind keys to global, team, and/or fireteam voice chat. Then in-game you just hold down the key and speak into your microphone.
November 20th, 2007 at 11:27 pm
hola quiero juegos para linux
November 23rd, 2007 at 5:11 pm
The first release ran like a dream. But these last two versions exit (seg fault) immediately. What gives? How can I figure out whats wrong?
November 24th, 2007 at 3:50 pm
Did you check google/search engines to see if it’s other peoples problem too or?
It might be a driver issue or if you are running a source distro (i.e. Gentoo) there could be large # of problems (not knocking those, just saying).
I would suggest that you update your kernel per your distributor + video driver from your manufacturer + audio driver via it’s vendor vendor.
If it’s [b]reproducible[/b] on other peoples boxes then you should file a bug report, but only if you cannot find a solution or are certain it is not a distrobution-specific problem.
Please note that it seems as if bug reporting is a lost or dead art form these days - so may I suggest including the following information:
Linux/BSD Distribution and Release version
Kernel version
Video card Make and Model
Video drivers Version and Where obtained
Audio drivers Version and How obtained
dmesg output
lsmod output
X11 logfile
WindowManager being used
Describe how you are launching the program
State the expected result (what should happen)
State what actually occurs (what is happening that should not or deviates from the expected)
Personally I would also include these:
Your motherboard Make and Model
#of RAM installed and have you Tested your RAM for errors
There is a when and how on reporting bugs at the official site. [i]It includes how to gain more information from the executable while launching.[/i] Look under the:
“Questions / Bug Reports”
http://zerowing.idsoftware.com/linux/etqw/
November 28th, 2007 at 4:48 am
Thanks. I checked your website and saw the note about kernel versions. I’m on 2.6.13 which is probably my problem.