This could serve as a demonstration what a long way way web sockets/rtc/channels still have to go, since the experience is much worse even considering the ping compared to 20 year old netcode.
On a similar note, I think people were _way_ too early to celebrate the death of Flash (security issues aside of course). Developers were making content in 2000 which their contemporaries 20 years later don't come anywhere close to in terms of performance, design, or responsiveness.
Play Counter-Strike 1.6 in your browser
131–140 of 337 posts
Re: Play Counter-Strike 1.6 in your browser
#132I love how people like to make browser versions of everything. From chat apps to email clients to games. But they all end up consuming 10x the memory but are still 10x slower than their native counterparts !
Re: Play Counter-Strike 1.6 in your browser
#133I love how people like to make browser versions of everything. From chat apps to email clients to games. But they all end up consuming 10x the memory but are still 10x slower than their native counterparts !
This is a flippant useless negative comment on someone's cool effort. Looking at your other comments, and at your blog - everything is negative. "This sucks, this is crap, I would never use this". What's with all the negativity? Just give creating comments and posts about stuff you like a try. The internet is not short of critics to make useless negative comments.
Re: Play Counter-Strike 1.6 in your browser
#134Re: Play Counter-Strike 1.6 in your browser
#135Earlier quoted context omitted.
> IIRC it got replaced at some point. The current iteration of Source's netcode doesn't have anything to do with that, though. Do you have a source (heh) to back that? Lots of the networking configuration cvars from 1.6 are still there in CS:GO and do the same thing. Maybe it was cleaned up but I wouldn't be surprised if it's still mostly the same code.
https://github.com/SteamDatabase/Protobufs
Re: Play Counter-Strike 1.6 in your browser
#136Earlier quoted context omitted.
Seems a bit unfair to only acknowledge one side of the trade-offs. Obviously native apps win the perf side. How about being able to play with your friends after just handing them a link? Native 1.6 doesn't even run on my computer at all. I think browser ports are the only hope that old games have at coming back. The other month I played Nox's quest mode with my friend on a browser emscripten port (plus a lot of custo…
Mouse tracking is clearly broken on Firefox here. The input lag is insance. I wouldn't link this to any of my friends with the intention of getting them to play Counter Strike with me.
Re: Play Counter-Strike 1.6 in your browser
#137Earlier quoted context omitted.
> Valve games use Protocol buffers and UDP connections to the lobby server, in their netcode (someone correct me if I'm wrong). The netcode originally used in GoldSrc/1.6 came from QuakeWorld and predates Google. IIRC it got replaced at some point. The current iteration of Source's netcode doesn't have anything to do with that, though.
> IIRC it got replaced at some point. The current iteration of Source's netcode doesn't have anything to do with that, though. Do you have a source (heh) to back that? Lots of the networking configuration cvars from 1.6 are still there in CS:GO and do the same thing. Maybe it was cleaned up but I wouldn't be surprised if it's still mostly the same code.
Re: Play Counter-Strike 1.6 in your browser
#138I love how people like to make browser versions of everything. From chat apps to email clients to games. But they all end up consuming 10x the memory but are still 10x slower than their native counterparts !
This is a flippant useless negative comment on someone's cool effort. Looking at your other comments, and at your blog - everything is negative. "This sucks, this is crap, I would never use this". What's with all the negativity? Just give creating comments and posts about stuff you like a try. The internet is not short of critics to make useless negative comments.
I am an avid gamer who players a couple of hours of Apex Legends and Call of Duty Modern Warfare everyday. And I've been info FPS gaming for 2 decades now.
To play a game released a couple of decades ago and see it take up almost the same amount of resources as the games I mentioned earlier gave me a chuckle.
I commend the developer for his effort though. To make a game like that run on browsers is a mighty impressive effort and it is Uber cool. I don't dispute that even for a second.
Re: Play Counter-Strike 1.6 in your browser
#139Earlier quoted context omitted.
On the other hand, they don't require admin rights, disk space or installation time, and are platform independent (including for example chromebooks)
The first two are trivially solved by portable applications (AppDirs, Application Bundles, AppImage, etc.). Platform independence is only kinda true, as many of these things don't actually function correctly on anything but Chrome, so they effectively target just one platform.
Re: Play Counter-Strike 1.6 in your browser
#140This could serve as a demonstration what a long way way web sockets/rtc/channels still have to go, since the experience is much worse even considering the ping compared to 20 year old netcode.
You're going to hang the state of networked browser gaming on this random person's netcode implementation? Go to r/GameDev and you can find some redditor Unity projects built on UDP that are even worse, but you aren't going to say "wow, UDP sux". Check out something like https://krunker.io/ which gives me a surprisingly good FPS experience despite my distance from the server. Browser gaming does take some thought tho…