News for hackers. Stuff that matters.

sponge

Re:Quake Live goes native and drops OS X, Linux on Friday November 08, 2013 @01:30PM (#6698099)
Sorry, I meant to say greater than 60hz. QuakeJS certainly hits 60, but 60 is often considered the minimum, especially as 120hz LCDs become more popular. (Most QUAKE LIVE LAN tournaments are played on 120hz LCDs, and there is still a small but loud segment of players that will play on CRTs to get 144hz)

Disabling vsync in about:flags definitely works, although it's an ugly thing for end-users to have to do. I've benchmarked 100> FPS by quake3's timedemo command through this method, although I don't recall trying to play the game and determining if the frames are actually being painted at that rate.

Re:Quake Live goes native and drops OS X, Linux on Friday November 08, 2013 @12:07PM (#6697428)
Many Quake players play at such a high-level of play, that the limitations of the web would instantly make the game unplayable to them. There's an awesome project at http://www.quakejs.com that have basically done this with emscripten (I'm friends with inolen, you've probably already talked to him).

Problem is, websockets are currently TCP only (TCP is unacceptable for a fast-paced real-time game). I guess there's WebRT but the support for that is not very widespread. Chrome and Firefox render webgl using vsync, which adds an unacceptable amount of mouse latency to mouse input. Chrome apparently won't render at 60hz+ even if your refresh rate is above it. I'm sure there's some additional latency between mouse events and updating the game too. It's a very compelling tech demo, but not something at the level that could be sold as a complete product yet.