|
|
| You can help! |
|---|
|
Every $ we get will be used to maintain our webservices and keep them running for your pleasure. |
|
|
| 0.49 FAQs |
We have compiled a list of Frequently Asked Questions (FAQs) from various sources, including, IRC, forums and server chat.
Contents of this FAQs
What are new features of 0.49(b)?The main features are the following:
A complete changelog can be found here in both Text or PDF. What are the minimum system requirements for 0.49*?Though TC:E is based on the ET engine, it has higher minimum system requirements:
Recommended system requirements:
What do I need to play 0.49*? Is it a patch or a full install? Is it be backwards compatible?TC:E 0.49* is a ~450MB FULL install(it is not an upgrade from 0.48), the files needed to play it can be found here. If you are a TC:E 0.48 (or earlier) player it is recommended you rename or delete your 0.48 TCETEST folder as it will be overwritten by 0.49*, if this isn't done you may have issues with online and offline play.Where can I download TC:Elite 0.49*?First you need to extract the contents of the .zip into your Wolf - ET folder, this should create a folder called tcetest inside that.Then you can create/copy a shortcut and add +set fs_game "tcetest" to the command line, for example on Windows: "C:\Program Files\Wolfenstein - Enemy Territory\et.exe" +set fs_game "tcetest"
Linux users can also just use it from the console:
et +set fs_game tcetest
When I try to connect on some servers in the list it tries to download a bunch of files then disconnects.You are trying to connect to an 0.48 server, unfortunetly there is no easy way to filter them from the 0.49* servers in the server browser. The best way is to sort by the map names, maps that have the obj_ prefix are from 0.49* while the dem_ ones are from 0.48, for example: obj_northport in 0.49* is a rehauled version of dem_northport in 0.48.I'm not seeing any servers in the in-game browser!This seems to be a little gremlin that appears and disappears. Something you could try is renaming ths servercache.dat within the tcetest folder and trying again. Failing that you could try... Windows users can use The All Seeing Eye, here are instructions on setting up a TC:E 0.49* filter, the filter that comes with ASE shows ALL TC:E servers of different versions, so using this custom filter is recommended. Info Linux and Mac server browsers will appear soon.Why are there no new weapons in this update?Coroner wrote: Unfortunately, some stuff that was already prepared or close to be finished didn't make it in the 0.49* release in the interest of time. New weapons will be released along with new maps in the future. We hope to be able to constantly improve TCE 0.49+ with shorter upgrade cycles.Any changes for servers?There is now a new "sv_official" setting, where official servers can only load offcially released TC:E maps and are meant to only reference the official TC:E pak files. TC:E 0.49* will also be limited to 20 clients in Objective mode and 32 clients in the other modesIs TC:E Open Source? How about moving to the Q3 GPL engine or its forks? Can I contribute?TCE is closed source. The engine subject has been discussed already, and the developement team has stated several times that they intend to continue in the W:ET engine as a closed source project. If you think you can contribute models/maps/textures of the same quality of the TC:E standards, feel free to contact the team through the Contact Form.I can't load some maps like Snow and Railhouse!!I get a Hunk_AllocateTempMemor error when trying to load them! What can I do?You need to set your com_hunkmegs higher, to do so, edit the autoexec.cfg text file located in your tcetest folder (if there isn't any, create one) and add/edit the line: Code: seta com_hunkMegs "192" Set the value (default is 192) to 1/2 of the amount of RAM you have, 256 for 512mb of RAM, etc. If you only have 256mb of RAM and are having this issue, you should really consider an upgrade. You may need to restart TCE twice after I'm getting a huge of amount of lag every time someone fires a gun! Is there any fix for this?The most common solution for this problem is to set the "Wall Mark Lifetime" off, you can do this in the View section of the Options menu. This can also be done by console or editing the cfg's by setting "cg_marktime" to "0". |
















