Live data from Hacker News

Doom crash after 2.5 years of real-world runtime confirmed on real hardware

lenowo.org

111–120 of 221 posts

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#111

Earlier quoted context omitted.

Consumer protection laws prevents businesses following this to it’s extreme. For many businesses the ideal would be to just sell stuff that immediately breaks down as soon as it’s sold. It has the fulfilled its purpose from their point of view

I run sous vide cookers 24*7, and they uniformly break within 90 days or less. But they don't like to admit their smaller duty cycle, so they don't, and keep sending me warranty replacements instead. I keep buying different brands looking for one with a longer life. I'll bet most people do that when their gadgets die, and purposely making products that die as soon as sold isn't often a successful business model.

Are there not industrial ones meant to last longer? Maybe you can buy a used but good condition one of those.

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#112

Earlier quoted context omitted.

I run sous vide cookers 24*7, and they uniformly break within 90 days or less. But they don't like to admit their smaller duty cycle, so they don't, and keep sending me warranty replacements instead. I keep buying different brands looking for one with a longer life. I'll bet most people do that when their gadgets die, and purposely making products that die as soon as sold isn't often a successful business model.

That’s not a small cycle count for a normal household. 90 × 24 = 2,160 total hours. I sous vide now and then, about twice a week for 6 hours each, so around 12 hours a week. That works out to roughly 15 years of usable machine time for the average person. Not bad at all.

You think a measly 360 uses at your 6 hours typical operation is even remotely acceptable for a glorified heating element?

And yes, 15 years is bad. I don't want to replace my entire household every 15 years FFS.

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#113

Earlier quoted context omitted.

I run sous vide cookers 24*7, and they uniformly break within 90 days or less. But they don't like to admit their smaller duty cycle, so they don't, and keep sending me warranty replacements instead. I keep buying different brands looking for one with a longer life. I'll bet most people do that when their gadgets die, and purposely making products that die as soon as sold isn't often a successful business model.

That’s not a small cycle count for a normal household. 90 × 24 = 2,160 total hours. I sous vide now and then, about twice a week for 6 hours each, so around 12 hours a week. That works out to roughly 15 years of usable machine time for the average person. Not bad at all.

Photography is the same way. Most SLR / DSLR / mirrorless cameras have a mechanical shutter which is expected to last around 200k-1m activations. I've had a camera for a bit over a year. I've used it quite heavily, and my shutter count is at about 13k photos. At this rate, the shutter will probably last for 20+ years - which seems fine. If I'm still using the camera by then, spending a few hundred dollars to replace the shutter mechanism sounds totally reasonable.

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#114
In games I worked on I use time to pan textures for animated FX.

After a few hours precision errors accumulate and the texture become stretched and noisy, but since explosions are generally short-lived its never a problem.

Yet this keep bothering me..

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#115

Earlier quoted context omitted.

Install an ad blocker.

I opened this on an iPhone which has fewer adblock options. Desktop is better locked down. Regardless I can still complain about how intrusive the ads are.

I just opened this my iPhone with 1Blocker installed. I saw no ads. It’s been around since iOS 8

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#116

Earlier quoted context omitted.

I run sous vide cookers 24*7, and they uniformly break within 90 days or less. But they don't like to admit their smaller duty cycle, so they don't, and keep sending me warranty replacements instead. I keep buying different brands looking for one with a longer life. I'll bet most people do that when their gadgets die, and purposely making products that die as soon as sold isn't often a successful business model.

Are there not industrial ones meant to last longer? Maybe you can buy a used but good condition one of those.

There are, and if you really have the workload that you need to cook stuff 24/7 (what in gods name is OP cooking btw?) then you should definitely get one of those. Maybe not even secondhand but just a new one. The cheap consumer grade ones are meant for people who use them once or twice a year.

This is a fine example of what I meant about people complaining when they use products beyond their design parameters.

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#117

About a year ago I was looking at Crash Bandicoot timer systems and I found that Crash 3 has a constantly incrementing int32. It only resets if you die. Left for 2.26 years, it will overflow. When it does finally overflow, we get "minus" time and the game breaks in funny ways. I did a video about it: https://youtu.be/f7ZzoyVLu58

Is it common to default to a signed integer for tracking a timer? I realize being unsigned it would still overflow but at least you'd get twice the time, no?

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#118

Earlier quoted context omitted.

I run sous vide cookers 24*7, and they uniformly break within 90 days or less. But they don't like to admit their smaller duty cycle, so they don't, and keep sending me warranty replacements instead. I keep buying different brands looking for one with a longer life. I'll bet most people do that when their gadgets die, and purposely making products that die as soon as sold isn't often a successful business model.

That’s not a small cycle count for a normal household. 90 × 24 = 2,160 total hours. I sous vide now and then, about twice a week for 6 hours each, so around 12 hours a week. That works out to roughly 15 years of usable machine time for the average person. Not bad at all.

2160/12 is 180 weeks, or roughly 3.5 years, not 15 years

Re: Doom crash after 2.5 years of real-world runtime confirmed on real hardware

#119
post #48

Literally unplayable, someone should fix that. Doom is actually such a good game, I always go back to it every few years. The 2016 reboot is also pretty fun, but the later two in the series didn’t do it for me.

Same. Something about the metroidvania design with the home hub of the later ones didn’t give the same feeling. It should be run, kill, find secrets, end, next level.

I just finished Robocop: Rogue City and it was exactly this a linear level by level shooter that felt like a pure Robocop power fantasy movie. I played new game plus it was so much fun and I never do that.

It's like the game industry got a fake memo saying no one wanted linear story-based games anymore. I ended up buying two more Teyon games because I was so happy with their formula and they are playable in a dozen or so hours. Tight, compact, linear, fun story and game play... No MTX or always online BS and they don't waste my time with busy work.

Post reply on HN