Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Quake Engine Indicators

fabiensanglard.net

Post reply on HN
Print view View original

41–50 of 65 posts

Re: Quake Engine Indicators

#41

Post by anthk »

somat wrote: post #15
whou wrote: post #2

Cool curiosities! The chocolate quake source port is great as well. I've always wondered why there wasn't a chocolate doom equivalent for quake. It was nice to see its announcement earlier this year, so I've been quietly following its development ever since. The guy behind it did a great job, now we just need a crispy doom equivalent for quake! I also wonder where is that tortoise texture from. Seems such a small thi…

I am not familiar with chocolate doom what makes it better than any other doom source port? There are many good source ports of quake, I always liked darkplaces but it intentionally and willfully tries to push improvements so not really for purists. There is stuff like fitzquake/quakespasm that stays much closer to vanilla quake and if you like quakeworld ftequake.

Quakespasm needs a flag so your system doesn't nearly halt if it's running under an old 32 bit machine. And by old I mean an N270 CPU based netbook.

Re: Quake Engine Indicators

#42

Post by anthk »

doublerabbit wrote: post #31

Engines used to be cool. The original Theme Park engine was it's own application in it's emulator. You had SCRUMM which was another interactive cool thing of it's own. DOS games amazed me as a kid.

The ZMachine it's its own computer too (an emulator in the end).

Re: Quake Engine Indicators

#43

Post by fabiensanglard »

whou wrote: post #2

Cool curiosities! The chocolate quake source port is great as well. I've always wondered why there wasn't a chocolate doom equivalent for quake. It was nice to see its announcement earlier this year, so I've been quietly following its development ever since. The guy behind it did a great job, now we just need a crispy doom equivalent for quake! I also wonder where is that tortoise texture from. Seems such a small thi…

I think nobody tackled it because Quake is so fast. There is quake.exe but also glquake.exe and winquake.exe. Each have different capabilities.

And of course there is quakeworld which is a complete fork with different net protocol, prediction, and commands. Example of new features is that skins can be downloaded on the fly, you no longer needed skinpacks.

Re: Quake Engine Indicators

#44

Post by paulryanrogers »

mewse-hn wrote: post #27
somat wrote: post #15

Earlier quoted context omitted.

I am not familiar with chocolate doom what makes it better than any other doom source port? There are many good source ports of quake, I always liked darkplaces but it intentionally and willfully tries to push improvements so not really for purists. There is stuff like fitzquake/quakespasm that stays much closer to vanilla quake and if you like quakeworld ftequake.

> I am not familiar with chocolate doom what makes it better than any other doom source port? The earliest doom variants once the source code released started adding features that weren't faithful to the original dos version 1.9. Even Boom which was a pretty conservative codebase that focused on limit removal for level editing added weird things like weapon recoil pushing the player back when you shoot a weapon. So c…

Chocolate even has same bugs and visual glitches beyond original limits. This helps when making maps you want to work in DOS without having to boot DOSBox or ancient hardware.

Re: Quake Engine Indicators

#45

Post by epolanski »

doubletwoyou wrote: post #35
CodeCompost wrote: post #29

When I read the title I was expecting it to talk about indicators in the inheritance sense, say how you can tell if an engine has a Quake Engine pedigree. Like looking at the graphics or the online behavior of a game and tracing it back to Quake's renderer or netcode. Still a cool article though.

along those lines, I saw a video where a light strobing pattern from quake was still used in a section half-life alyx (with much better lighting lol) the fact the quake engine’s internals still live on in so many modern games is quite a feat

Half life was built on quake 1 code and the codebase was never abandoned but they kept improving and improving on it, essentially all valve games have something inherited from it from TF2 to Dota to Alyx.

Re: Quake Engine Indicators

#46

Post by zeroq »

toast0 wrote: post #4

> The NET indicator is displayed when a client has not received any packets from the server in the last 300ms. This was likely aimed at players to help them determine how bad their ping was. This is not an indicator of high ping. It's an indication of loss of connectivity. Even if your ping is 2 seconds, the server should be sending you updates regularly. If you haven't received anything in 300 ms, either you're losi…

Oh sweet summerchild.

When OG games were released we were playing on LAN with BNC terminators. That's why the Q1 netcode is so bad.

When we moved to online we didn't had the infra we have today.

Bonus point: CS at one point just halved the ping in the UI so players would think it was more responsive.

Re: Quake Engine Indicators

#47

Post by bigtechmustburn »

whou wrote: post #2

Cool curiosities! The chocolate quake source port is great as well. I've always wondered why there wasn't a chocolate doom equivalent for quake. It was nice to see its announcement earlier this year, so I've been quietly following its development ever since. The guy behind it did a great job, now we just need a crispy doom equivalent for quake! I also wonder where is that tortoise texture from. Seems such a small thi…

[dead]

Re: Quake Engine Indicators

#48

Post by thenthenthen »

girvo wrote: post #28
dmurray wrote: post #14

Earlier quoted context omitted.

In practice if you have a very high ping, you're losing packets or there's buffering somewhere. Not because you have a 30,000 km long ethernet cable.

We used to play these games on dial-up where ~300ms pings were pretty common. Moving to a cable connection in ~2001 was shocking in comparison!

Funny, my first cable connection was waaay worse than dailup. Abysmal pings and speeds maxing out around 3kb/sec. It took a few years to reach 32kb/sec which felt insane.

Re: Quake Engine Indicators

#49

Post by stoneforger »

cluckindan wrote: post #32
hnlmorg wrote: post #17

Earlier quoted context omitted.

Are you sure it’s not meant to be an RJ45 plug? The cylindrical thing to the bottom left corner of the wall socket looks like it might be a BNC plug. Which would make sense for the era of quake when Ethernet wasn’t yet ubiquitous.

RJ45 next to BNC implies a token ring network, not ethernet :)

Token ring was the protocol, BNC the connector. Have you even lived without StarCraft on X.25 ? Don't forget to cap the ends!

Re: Quake Engine Indicators

#50

Post by Sanctor »

I think it should say "present" instead of "prevent" in this sentence: "The NET indicator is prevent and active in Quake 2."

Thought I should report since I saw Mr. Sanglard in the comments :)

Post reply on HN