Threaded Mode | Linear Mode

Ruthless · 18 Jan 12, 02:37PM

Maybe separate the chat window from the kill feed ? Problem with this is covering up too much window space :\

flowtron · (This post was last modified: 20 Jan 12 08:41PM by flowtron.)

Yes, I did this for another game I was working on before I took over AssaultCube. It can work quite well - simply put the frag-messages on the top right, the chat on the left - reduce space to half screen (minus space for clock if shown). Of course, that requires a bit more math in the rendering of the chat stuff - but frag-messages have a definite limit in size (MAXNAMELEN*width_of_W)*2 + spacing + width_of_frag_icons. That formula was wrong at first and it assumes one would want a "X f Y"-format of frag messages like: "Player-1 X Player-2" and again: where X (or whatever) would be the iconic display of the weapon in use .. which again requires a bit of code voodoo to make it work.

Lantry · (This post was last modified: 14 May 12 01:06AM by Lantry.)

Found a bug in the svn, not sure where to put it, here looks good.
Anyway:

To replicate:
press and hold 'w' (to walk forwards)
press and release 's' (while still holding 'w')

when you press 's', you will start to walk backwards, as you should. However, when you release 's' you will stop moving, even though you are still holding down the 'w' key.

I am using Windows 7, and the movement is working fine for the 1104 installed on the same computer. The person I was playing with (Aekom) is also on Windows 7 but could not replicate this bug.

jamz · 14 May 12, 07:46AM

My guess is that this is an unintended consequence of this neat addition. I couldn't explain why it didn't work for Aekom, unless he has a overriding manual bind for S that puts it back to just "backward".

#M|A#Wolf · 14 May 12, 09:43AM

Wait, was the backward ladder climbing feature removed...?!

jamz · 14 May 12, 11:58AM

No. Adding it caused Lantry's bug.

Lantry · 16 May 12, 01:58AM

Yep, I changed it to just

cubescript code :

 

bind "S" [ backward ]

and I don't have that bug anymore. Perhaps Aekom didn't have this bug because his saved.cfg still had the old bind with just 'backward' in it.

Aekom · 16 May 12, 04:50AM

(16 May 12 01:58AM)Lantry Wrote: Perhaps Aekom didn't have this bug because his saved.cfg still had the old bind with just 'backward' in it.

Yeah you're right. I reset my binds and end up with the same bug.