Two small improvements that I would still like to see in QL:
1) [x] Sound in Background toggle, so I know when the match starts while I'm tabbed out. Because these fuckers take ages to F3 sometimes. This should really be standard these days, every game has it.
2) Spectator queue for team modes. Surely it would be a step up from everybody just spamming or holding down team red/blue binds. Duel already has it, just imagine teamsize >1, and it is exactly the same thing.

Now, I know, Steam QL isn't supposed to get any more updates. But these two things would be incredibly easy to implement, IMO.
Whatever...
Where is Sync & Sponge nowadays? They still oversee QL on Steam and have access to it, don't they?

Ya I'm sure I could think of many more improvements, but what would be the point... these two stand out as they'd require so little effort to code, yet hugely improve quality of life.
What's on your 'wishlist' ?

hi

so I've had this bug in QL for a long time
sometimes when the map loads, the image is weirdly stretched, as if the horizontal fov or aspect ratio was screwed up. so I have to vid_restart then it's back to normal. not a big deal just a slight annoyance.
just wondering if anyone else getting this

here is how it looks like when bugged: http://i.imgur.com/mJCK0HZ.jpg
and here is normal one after reload: http://i.imgur.com/jpdpfz2.jpg

Hey, so apparently a lot of people are having issues with the com_maxfps limit being downscaled in the new standalone client(114 instead of 125, 200 instead of 250, etc). So I figured this would be worth a thread of its own.
After experimenting a bit last night, it seems that this problem is somehow related to timers such as HPET(http://en.wikipedia.org/wiki/High_Precision_Event_Timer). Turning on HPET in BIOS fixes the fps problem for me.
Now, HPET is quite a controversial thing, and may allegedly cause issues on _some_ systems such as microstuttering or mouse lag - for me it doesn't, though. You have try it for yourself.
Some sources:
http://www.ghacks.net/2013/04/18/try-changing...rformance/
http://www.neowin.net/forum/topic/1075781-twe...e-and-fps/
Also note that despite turning it on in BIOS and therefore fixing the fps issue, Windows will still use mixed timers. So you might want to turn it on in Windows as well and see if that works better for you or not. To do this, open a command prompt and type:
"bcdedit /set useplatformclock true" - to enable
"bcdedit /deletevalue useplatformclock" - to disable
You have to reboot afterwards for it to take effect.
Again this is separate from the BIOS setting.

If you don't want to use HPET for whatever reason, then it seems that com_maxfps 126 should give you a stable fps, if you want the old ~125 fps, that is. Obviously if you have the downscaling issue, the highest you can reach with com_maxfps 250 is around 200 at this point.

Regarding 250 fps, I played a bunch of games last night and I have mixed feelings about it to be honest. First of all, mouse feels 'faster', which have cons and pros for me.
Movement feels slightly better, as if I have better control, it's hard to explain but definitely noticeable.
In many cases, my aim feels sharper and flick shots seem to be a magnitude crazier than before. But at the same time I now seem to have a REALLY hard time against even the simplest dodges, seems to be way worse than before. Really annoying. So it's kind of up in the air for me atm.
I'm using a Samsung 2233 so it's 'only' 120hz, I wonder how things would be at 144 or even with a super high refresh rate CRT.
Also there's something wrong with the sounds I think, but I can't really put my finger on what it is. Probably the footsteps sound bug that others have mentioned.

Anyway, feel free to share your thoughts on playing at 250 fps, and whether or not the fix helps you.