Message Boards

Odamex 0.5.0 is the first major version release in over two years and introduces dozens of bug fixes, new features, and useful optimizations for server administrators and players alike.

Improved netplay will be the most noticable optimizations for most users in Odamex 0.5. Default rate caps have been raised for both client and server which allows for bandwidth intensive coop games (Scythe 2 Map25 for instance) and large ffa games. In theory, a non-coop server with appropriate bandwidth would be able to host almost a hundred players without issue. While that may sound excessive, it just shows what Odamex is now capable of. Other changes made are related to various map and item/weapon desyncs.

A very important change for server administrators comes with reorganized cvars. Most server variables now begin with the sv_* prefix (not all however). An extensive listing of these variables and their usage can be found on the server variable page on the Odawiki. The logfile console command has been reimplemented for server and client. Servers can now also set a "Message of the Day" for connecting clients. More information on basic server settings can be found on the Odawiki.

Odamex 0.5.0 includes an improved server protocol as well as an updated launcher interface. The Odamex Launcher now includes graphical ping indicators and a server information window which displays version, revision, any dehacked patches running on the server, and all server variables.

There are way too many changes to Odamex 0.5 to describe them all here! Check out a more extensive list on the release page or the complete listing using our svn changelog.


There are still a few bad bugs affecting clients on Windows platforms, particularly Windows Vista and Windows 7. Despite many efforts to resolve these issues, we have not been able to come to any solutions. In light of this, here are some recommended work arounds:


Q: My mouse feels weird and seems to decelerate in Odamex. It makes it difficult for me to play sometimes, is there a way to fix this?

A: The Odamex team has been attacking this bug for quite a while and believe we are closing to fixing it, but have to provide workarounds for now. Odamex uses two types of video drivers on Windows, the default windib (gdi) and directx. Without going into too much detail, DirectX interprets mouse input independent of video resolution and, as a result, has proven to be much more reliable an option for some users. To set the Odamex video driver from gdi to directx from the Odamex Launcher, goto File > Settings, and locate the "Extra command line arguments" box. Inside the box type "-directx" without quotations.


Q: When I try to turn down the music, the sound turns off as well! How can I turn down the music without affecting sound volume?

A: Unfortunately, Microsoft changed the way midi and sound volumes are controlled in Windows Vista/7. Due to these changes, SDL cannot independently lower midi volume without affecting all wave sound formats. For now, the best recommended solution is to run Odamex without music at all. To do this from the Odamex Launcher, go to File > Settings, and locate the "Extra command line arguments" box. Inside the box type "-nomusic" without quotations.


The Odamex team would like to remind our users that the Odamex project thrives off of user input, particularly when it comes to resolving bugs in the engine. If you would like to be involved in helping Odamex's development move forward, please take a moment to sign up for the Odamex Bug Tracker. The team refers to the bug tracker to determine how development should move forward. If you come across something odd or broken that is not already listed or resolved in the tracker, please submit as much information as you can! Odamex can only succeed with the help of dedicated users!

If you are interested in tracking official Odamex news more easily, you can subscribe to updates in a variety of ways:

1) You can subscribe to the Odamex releases rss feed.

2) Subscribe to the new Odamex Mailing List, which will give you immediate updates on Odamex bugs and their status as changes occur. You can do this by signing up here or email odamex-bug-reporter-request@freelists.org with "subscribe" in the subject field.

3) You can receive email alerts on official Odamex releases (requires a sourceforge account or an openid).

I will say that the angle of the pistol looks sort of weird. Like it's cocked too far to the left in relation to the hand and placement on the screen.

Though this is not a complete list of everything that Odamex can do (exhaustive documentation still has to be done), the following articles on the wiki may prove useful to you:

How To Run A Server

Server Variables

Server Commands

Updated as of 1/19/09.

Closed bug 326 as invalid since there hasn't been any response from the bug author since 2007 and nobody else I've asked can reproduce this bug.

Bug 243 has been closed as bug 499 has been declared a better solution.

EDIT: Scrapped enhancement bug for keys/ctf support (bug 458)

It's that time again to look through the Bug Tracker, only this time we're gonna try and squash as much as we can. The Bug Tracker Cleanup Initiative which promotes community and personal involvement and investment in Odamex. This will hopefully lead to a healthier, more manageable project for our programmers and encourage project growth.

The way to get involved is easy! All you have to do is use this compiled list of currently outstanding bugs and attempt to reproduce any of the bugs in the list that haven't been tested yet.




Your job is to identify or try to reproduce the bug in your current client. PLEASE SPECIFY YOUR OPERATING SYSTEM AND THE REVISION YOU ARE RUNNING ('version' command in either client or server will output this information).


If during your testing, you have any new information on how to reproduce a bug, you should report any new findings to both the bug tracker and this thread immediately.

If you cannot reproduce the bug but are not sure that it is corrected, please specify that you cannot reproduce. This may or may not be the most common response we'll receive. We'll have to see how this goes.

While it is important to find any new information on a bug, it is not the main goal of this program. The main goal is simply put to determine the legitimacy of any bugs still in the tracker (some of which have been open for over 3 years!). However if you do find new information pertaining to an outstanding bug, PLEASE REPORT IT!

Do not waste your time with any grayed out bugs in the list as they are usually enhancement bugs or something similar that detail implementation of a feature rather than an existing issue.

The projected goal is to report and complete the status of all current open bugs on this list by February 5th. Let's see if we can pull together and help get the ball rolling even faster towards an Odamex 0.5 release.

The cross-platform server browser, Doomseeker, has been updated to include even more support. With the release of the Doomseeker 0.5b beta (revision 364), the powerful browser now has Mac OSX support thanks to the efforts of our Hyper_Eye.

On top of support for Mac OSX, Doomseeker also has improved stability among a variety of other changes.

The changelog,download links, and discussion for this beta of Doomseeker 0.5b can be found in this development blog.

The new cross-platform server browser, Doomseeker, has just been released with support for the current version of Odamex.

Doomseeker boasts some of the fastest speeds seen on server browsers yet. Other useful features of the browser are a search filter for servers, buddy lists, and plugin support for other multiplayer engines. Doomseeker also utilizes Wadseeker, a quick, GetWAD alternative.

Doomseeker appears to be a nice alternative to those who do not prefer the native Odamex launcher or IDE. To download Doomseeker, visit their download page to select your platform.