Yeah, there's no doubt in my mind that this is a bad thing for the game and VR in general. We need less platform lock in, not more.

Don't trust the hardware survey. If the headset isn't plugged in it doesn't exist. Not many people leave the headset plugged in 24/7, so I don't think the HW survey is a reliable source.

I don't think it's actually trending downward, the hardware survey only shows devices connected at the time. I have two vr headsets and I only plug them in when I'm actually using them, so according to the survey I don't have one. I'm sure a lot of people do the same. Also, totally ancedotal evidence, but four of my friends bought into VR in the last few months since the price finally came down low enough for them to do it and they wanted to play Beat Saber. If that can sell headsets Half Life certainly can.

Beat Saber really seems to be the closest thing to a Killer App for VR right now. I'm introducing it to people who have never really been interested in video games and they fall in love immediately. It's also the only VR game I've played that has felt like a complete, novel, and interesting experience that I keep coming back to.

Can confirm. I'm currently pretty addicted to Beat Saber. Let my (non-gamer) mom try it some time ago and now everytime they visit she asks if she can play a bit.

It seems like ECC support is pretty widespread, I know for a fact that my Asus Prime X570-PRO has an option for ECC memory in the bios and it's a midrange board. Might depend on the board manufacturer to enable it. Asus seems to have it in most if not all of their boards.

FYI Steam doesn't even have content restrictions on the marketplace now. There's a ton of adult games on there now. So not the best point.

It was patched for almost all systems almost immediately like he said. I suspect the reason he still had the bug was due to the Asrock Rack X470D4U motherboard being an older generation board, and also a micro atx server board of all things. They might have only sold a couple hundred of them total in a niche like that so it's not too surprising it would be a low priority on the bios update list.

I also find it kind of funny that he calls Asrock Asus every single time he mentions them in the article. If he was trying to install an Asus bios on his Asrock mobo then he's got bigger problems than this bug.

Hmm, I guess that makes sense save for why wasn't the OS supplied microcode working or why was it out of date.

So if I was to build a Ryzen System today, would that bug not exist?

You would definitely be fine as long as you're using an updated motherboard with at least AGESA 1003ABB, which would be any x570 board and likely the vast majority of x470s by now.

Last time I checked, this was not fixed for my B450-TOMAHAWK-MAX

Hmm, I see 1.0.0.3abba was released for that board on 9-18-2019. That should include the fix, although I'm not an expert, maybe it isn't there for some reason?

Last time I checked it was only BETA - I will check again to see if anything has changed.

EDIT: looks like it's out of beta now - awesome! Thanks.

I see you've met my CTO.

Can being the keyword. None of that is even close to required. You have the option to tinker, you aren't required to.

Not sure what cpus you're looking at but everything in the desktop space is over 4ghz nowadays. My last cpu was at 4.6ghz its entire life and my 3900x stays at over 4ghz on all 12 cores when doing a render.

Your CPU has 3.8GHz base clock (guaranteed), it can't sustain 4.6GHz turbo clock on all cores.

Yes, I know, but it never actually goes below 4.0 for me on all cores when doing a render. The 4.6 was referring to my 4770k which was at 4.6 on all cores all the time.

The website it's linked on is called widgetsandshit.com. I think that's a bigger problem if you're that worried.

Nothing offensive about shit.