Notably, it refers to answers, not the invalidity or duplication of a question.
I think it’s too much to close a question just because a different question happen to have the same answer. There might be a future answer that might apply to one, but not the other.
Emulating DK’s Jungle Parkway in MK64 goes brrrr
Not only that. Emulators must often ”cheat” to achieve high speeds. This means emulators doesn’t try to achieve a 1:1 replication of what’s happening inside the hardware, but something that’s gives close enough results and better tailored for modern hardware.
The reason why N64 is particularly difficult is because each game must be optimized individually (due to the heavy reliance on microcode). The emulator must replicate the hardware at a much lower level for an accurate emulation of all games. Emulator developers can apply optimizations on each individual game, but it’s incredibly time consuming to do so for every game in the N64 library.
Well, MVG is an experienced programmer, especially with emulation and homebrews, so he knows what he’s talking about.
The video says that emulation has always worked better on popular games. But if you try to emulate a less popular game, you will run into major issues. This is because the emulation must be tweaked for each game specifically due to how N64 hardware works.
The catch about Lemmy is that degenerates like me are here
I like DS for what it is: the first fully 3D Mario Kart on a handheld console. Played quite a lot of it back in the days. It was also the first one with online play.
I think the missions was a fun addition as well. It’s the only Mario Kart game that features boss battles (to my knowledge).
I’m not sure. I preferred MK64 back in the day.
I think the specials make the game quite unbalanced. It’s more about picking favorite special rather than favorite character. If you don’t like a particular special, well then you will never play those characters (I’m looking at you Peach and Daisy).
With the other MK games I just pick whatever character I feel like playing today.
I also didn’t like how triple shells became limited to the Koopas only. Those should be accessible by everyone.
Limiting to PC only games makes things tricky. Most games on PC are available on console as well. Especially soulslike and fighting games.
But my recommendation is Ultrakill. It’s a fast paced FPS with a Devil May Cry style system. It really showcases the benefit of having a mouse and keyboard for shooters.
Edit: another is Black Mesa.
If anything, I think RTS need to go back to its roots. I’m not a huge RTS fan, and I’m not particularly nostalgic about the genre, but I have played a few games. My favorite? AoE2! It’s just a damn good game.
I love the game. Even got all the endings.
I think all the parrying is more satisfying than all the dodge rolls in Dark Souls. It makes cool noises and look more spectacular. Dodge rolls just look weird and doesn’t make sense at all (but it’s still fun to do).
And if you think the game is too easy, there’s a way to make it harder (before NG+). You can ring the Demon Bell found in Senpou Temple, which will trigger some form of ”hard mode”.
I’m meaning more in the sense of a wearable head device developed by a big tech company. It’s heavily marketed as the next big thing. Many talk about it - both with anticipation and concern. And when it finally releases, it’s quickly forgotten about.
Hololens did the same.
It’s Google Glass all over again.
Has any significant 3rd party apps been made for it?
Basically it’s just an optimization of a double nested for loop. It’s a way to avoid running the inner for loop when it is known there will be no hit.
This is useful when we for example want to find all product orders of customers in a particular country. The way we can do this is to first filter all customers by their country, and then match orders by the remaining customers. The matching step is the double for loop.
Something like this:
for order in orders:
for customer in customers_in_country:
if order.customer_id == customer.id:
…
Many orders won’t match a customer in the above query, so we want to single out these orders before we run the expensive inner for loop. The way they do it is to create a cache using a Bloom filter. I’d recommend looking it up, but it’s a probabilistic cache that’s fast and space efficient, at the cost of letting through some false positives. With this particular use case it’s ok to have some false positives. The worst thing that can happen is that the inner for loop is run more times than necessary.
The final code is something like this:
bloom_filter = create_bloom(customers_in_country)
for order in orders:
if bloom_filter.contains(order.customer_id):
for customer in customers_in_country:
if order.customer_id == customer.id:
…
Edit: this comment probably contain many inaccuracies, as I’ve never done this kind of stuff in practice, so don’t rely too much on it.
That’s how DRY is described in Pragmatic Programmer, where DRY was first coined. They’re clear that just because code look similar, doesn’t necessarily mean it’s the same.
That shouldn’t be needed either. A PSN or Steam account should be enough.