Of course. I’m literally shaking with pure rage.

Most gamers don’t specifically follow gaming news or keep up with all the latest scandals (of which there are too many to keep up with in any case), but they will notice if the nostalgia project they’ve been looking forward to is suddenly gone.

You have no idea how the people complaining about video game prices spend their money. You just disagree with them and make shit up apparently.

1992 was a very different time with very different market conditions and consumer behaviour for video games. Games used to have a much greater perceived entertainment value, despite their relatively small development budgets compared with today. They were also entirely physical media and renting was still a very common way to play them. From what I remember, it wasn’t the most financially accessible hobby either. Most of my friends growing up didn’t have permanent access to their own gaming console and not everyone that did had all the latest games. Nowadays, the gaming market is completely saturated with high quality titles, most of which are fairly cheap as well if you don’t buy them on release.

In any case: Super Mario Bros 3 came out in 1988 and released 1990 and 1991 for the US and Europe respectively. It also didn’t cost $59 and your inflation calculation seems off…

It is true and has been my experience for the last decade or so. Unfortunately, OP is trying to use a GPU from 2015 that’s still based on GCN 1.0 with the newer amdgpu driver stack, which is not officially supported. Effectively, OP is getting a taste of what it was like before AMD started pouring ressources into their open source GPU drivers.

The Phoronix comment section has always been kinda shit. Maybe one in every thousand posts will contain anything of value (in most cases a comment by a developer telling the peanut gallery why they’re wrong).

There isn’t much overlap between the gaming community and the gaming journalist community.

And the ability to breathe.

It would certainly help if the GitHub code search wasn’t utter garbage.

Maybe a fixed line-height?

That’s just the limited resolution if you push it to the limit of how fast it can refresh the picture…

The whole premise of this discussion was about technological progress and growth going by your initial comment. That means refining existing models and training new ones, which is going to cost a lot of energy. The way this industry is going, even privacy conscious usage of open source models will contribute to the insane energy usage by creating demand and popularizing the technology.

Do we really need to grow our energy consumption as a society by such a disproportionate amount?

Is there a source for these haughty, cackling archeologists making fun of hairdressers or is that just to manufacture some kind of underdog victory scenario?

I remember reading somewhere that it would be the farthest manmade object from earth, far outpacing the Voyager spacecrafts, assuming it didn’t vaporize.

With bluray rips, I don’t really see any way to avoid that unfortunately, unless someone else has already added the hashes for your release. Most people use it to scan their encoded releases, which will (in most cases) have already been added to AniDB by the release group. I’m a bit surprised though, that none of your rips are recognized. Have you checked the AniDB pages for your series to see if anyone uploaded hashes for bluray rips?

Grouping seasons into a series folder doesn’t work well in some cases, because that’s not the way they are released in Japan. A new season is (most of the time) effectively an entire new show entry. Show seasons are mostly a north american thing. No matter which software you use, there’s always going to be some minor issues if you group seasons into one entry.

Shoko compares a files ED2K hash against the AniDB database. The filename doesn’t matter for automatic detection. Have a look at the log to see if there are any issues. It’s entirely possible that AniDB just doesn’t have the hashes for the raw BluRay rip. In that case you can either manually link them in Shoko, connecting the AniDB episode id to the file hash, or create new file entries on AniDB with your specific hashes.

Shoko also has rate limits. The problem is that AniDB does rate limiting in an extremely stupid way for a UDP API and doesn’t even have the decency to define clear time limits.