Message Boards

Preface
This guide assumes a player is using the common WASD configuration for their movement keys, configured with the following:
bind W +forward
bind S +back
bind A +moveleft
bind D +moveright
Players should choose the method that they feel comfortable with, modify the key binding to match their movement layout, and then paste into the bottom of odamex.cfg.

Old School
Usage: The player will SR-40 to the right with W & D and then SR-50 by holding down the second mouse button and moving the mouse continuously to the right.

bind mouse2 +strafe
set m_side 15
Three Key
Usage: The player will SR-40 to the right with W & D but will also hold down a third key, Q, to SR-50 to the right. Similarly, the player will hold down W & A & E to SR-50 to the left.

alias +sr50l_3key "+left\;+strafe"
alias -sr50l_3key "-left\;-strafe"
alias +sr50r_3key "+right\;+strafe"
alias -sr50r_3key "-right\;-strafe"
bind Q +sr50r_3key
bind E +sr50l_3key
Two Key
Usage: The player holds down W to move forward and then holds down a second key, E, to SR-50 to the right, or Q to SR-50 to the left.

alias +sr50l_2key "+left\;+moveleft\;+strafe"
alias -sr50l_2key "-left\;-moveleft\;-strafe"
alias +sr50r_2key "+right\;+moveright\;+strafe"
alias -sr50r_2key "-right\;-moveright\;-strafe"
bind Q +sr50l_2key
bind E +sr50r_2key
One Key
Usage: The player holds down E to SR-50 to the right and Q to SR-50 to the left. While moving backwards, the player holds Z to SR-50 to the back and left, and holds C to SR-50 to the back and right.

alias +sr50fl_1key "+forward\;+moveleft\;+left\;+strafe"
alias -sr50fl_1key "-forward\;-moveleft\;-left\;-strafe"
alias +sr50bl_1key "+back\;+moveleft\;+left\;+strafe"
alias -sr50bl_1key "-back\;-moveleft\;-left\;-strafe"
alias +sr50fr_1key "+forward\;+moveright\;+right\;+strafe"
alias -sr50fr_1key "-forward\;-moveright\;-right\;-strafe"
alias +sr50br_1key "+back\;+moveright\;+right\;+strafe"
alias -sr50br_1key "-back\;-moveright\;-right\;-strafe"
bind Q +sr50fl_1key
bind E +sr50fr_1key
bind Z +sr50bl_1key
bind C +sr50br_1key
Turnspeeds Toggle
Usage: The player will SR-40 to the right with W & D and then SR-50 by holding down the second mouse button. Note that this method will require the player to press the second mouse button when first spawning to initialize the controls. If the player forgets do do this, the A and the D keys will spin the player's view instead of moving them to the left or right. Note that +sr50l_ts will take the place of the key bound to +moveleft and +sr50r_ts will take the place of the key bound to +moveright.

alias +sr50l_ts "+left\;+moveleft"
alias -sr50l_ts "-left\;-moveleft"
alias +sr50r_ts "+right\;+moveright"
alias -sr50r_ts "-right\;-moveright"
alias +sr50_ts_toggle "turnspeeds 65536\;+strafe"
alias -sr50_ts_toggle "turnspeeds 0\;-strafe"
bind A +sr50l_ts
bind D +sr50r_ts
bind mouse2 +sr50_ts_toggle

I have crashes on cybercrime3.wad with this client every 3 minutes or so. I use winXP.

Under certain circumstances, I was able to produce a crash firing the railgun on another map and I traced it back to an overflow bug with rendering particles (used to draw the rail). I was able to fix that bug which I believe to be the same bug you were experiencing.

Slopes have a thin black line drawing around them that don't look quite right.

I believe that is related to this rendering error:



There is a thin band of red above the entryway which should not be there. It indicates either the texture is offset incorrectly or that the texture is wrapping prematurely.

I would be very much in favor of creating a very detailed stat tracking scheme and have created outlines for such before. However there are a few larger issues that need to be resolved for us first:

• Players need to be authoritatively identified. The server needs to know you're Fluff and its not someone aliasing with the same name. (Read: username & password)
• Which method should be used to output the stats at the end of each round? Should it be put into a plain-text file or a SQL database? Where should this data be saved to?
• Should the stats be on a per-server basis or be universal across all Odamex servers?

These questions primarily revolve around Odamex's philosophy of not having a central authority for servers and instead letting server administrators function independently and decide what's best for themselves. Given that outlook, Odamex servers have no ties to something like a central server that maintains user accounts or a stats database. Deciding how to implement a stats tracker server within this context may prove difficult but an interesting discussion nonetheless.

This bug was due to an integer overflow when calculating the length of a sound-effect. It was fixed a month ago and will be fixed in our next release.

When I need a break from my bigger coding projects, I look at what is on the bug tracker to fix/implement. It serves as a handy to-do list for us, as well as a place to store relevant discussion for a feature/bug.

The take-home message is that if it's not on the tracker, we tend to forget about it. :D

With version 0.6.2, patches can be 32768 x 32768. Prior to that version, patches could only be up to 254 pixels high. Keep in mind that if you go beyond that, your textures will have tutti-frutti issues in some other non-ZDoom based ports like Chocolate Doom, if that's a concern to you.