Bro whatcookie had like the exact same experiences I had at that time! Never owned a PS3 until the lock down cause I wanted to play demon’s souls, cause I have a been a souls fan since dark souls prepare to die on PC! Also the PS3 I bought was the slim, just like yours. And until now, I didn’t think any of my systems could handle the emulation of it and your telling me my steam deck can‽ I mean, it’s kind of a moot point as I already have an actual PS3 that’s been letterbombed and multiman’d. But knowing I can take grand Turismo 6 on the go with me if pretty fucking dope!
MKIceandFire is probably one of the best no commentary Let’s Players on all of YouTube. It’s just gameplay and no bullshit. And they edit out any grinding and unnecessary side stuff; like their playthrough of Spider-Man 2, they would regularly edit around breaks and collecting things to just show you more of the story. And they have different ways to watch, from one long video of the entire story, to breaking it up into multiple 15 minute+ videos in their own playlists.
Can you highlight where you link this steam deck advice? There are no references to steam, steamdeck or linux in the article, and the only links are to the projects websites. Do they have a steamdeck guide?
EDIT: They have a steam deck installer on this page with the others:
Curious. Hadn’t heard of them at all and they seem to have made solid progress.
So I went to their “github” link which goes to their own self hosted (codeberg?) which is a big ol’ orange flag because it implies that either they don’t understand what git actually is or they assume their audience doesn’t… I can see that it is a yuzu fork. Not inherently bad but it does explain the progress for something nobody ever heard of until… today. And that has implications for the project getting a pretty strong C&D because of the shenanigans Yuzu was allegedly doing to get such strong compatibility on release day for so many games. Yellow flag, we’ll say.
Just skimming the last few MRs? Seeing a LOT of “waiting reviews” on the merged side of things which is another orange flag. Best case scenario it means they don’t understand how to map their SDLC to their tools, worst case scenario it means they aren’t actually doing thorough code reviews which is playing with fire when it comes to a console with as many leaks as the Switch.
Also no Releases. Which further suggests they have no idea how to use their tools. So did some digging on the readme and it looks like the project itself probably began 6 months ago with git.eden-emu.dev/…/d29d7b931c6ae8c035992d7a15d96a…
So yeah. Not sure how much they have contributed to the fork but everything I am seeing is just making me want to remind people that a LOT of people are going to make yuzu forks and you should think about what is going into the code you are going to blindly run. And… it kinda makes me think less of whatever blog site ran this interview.
To elaborate. There is nothing wrong with forking a project (assuming all licenses are upheld which, at a glance, this does). But the beautiful thing about git is that it is fundamentally decentralized so ANYONE can make a fork. And EVERYONE does. So the important things to check are if they actually have any idea how to run a project or are fly by night “hackers”. The former is how you make something stronger. The latter is how you get a whole shit ton of unacknowledged CVEs. And a great indicator is how they use their tools and implement an SDLC. And a huge indicator into that is how merge requests are handled.
One more edit. What allegedly sealed the fate of Yuzu (and Ryujinix) was very strong evidence that the devs had been looking at the various Switch leaks/hacks and were using pirated pre-release copies of games to improve 0-day compatibility.
Now, I am obviously not a lawyer so I can’t say whether they WERE doing things nefariously. But if you spend enough time dabbling in reverse engineering, you rapidly spot the telltale “intuitions” that come from somebody “cheating”. Because they aren’t testing code against behaviors or even using tools to speculate what C code created that assembly. They are looking at code and then writing an interface/re-implementation of it. And that is a MASSIVE no no because it gets you well past the bleem lawsuit and starts making you liable for a lot of penalties that we DO have precedent for.
As for the pre-release copies? It is, again, hard to not think they had copies of Tears and what not pre-release. And while it is possible that for every major release all the devs went to stores that broke embargoes… yeah.
And the implications of this for a fork that was very publicly taken down is… they know they are potentially working with poison fruit.
It’s been popular in the Steam Deck emulation scene because of its performance for most titles running better on the hardware compared to Ryujinx/Forks (Although because of those orange flags you mentioned, now it makes sense why EmuDeck refuses to provide support or streamlined installation in their menus).
Hopefully the ship is above board, but right now we’re able to reap the performance benefits as users - although I’ll probably stick to Ryujinx on my proper desktop PC.
I guess I wonder how much of that is just that… yuzu was REAL fucking good and this is Yuzu (if you check the source since their website doesn’t seem to acknowledge that?).
From a skimming of the code (if they aren’t going to do proper code review, why would I?), the main deltas seem to be related to CI/CD, branding, package updates, and MAYBE improved controls/interfaces more geared towards the android client.
And, to be clear, I think there is a lot of value in maintenance. But when you have to dig relatively deep to even see this is a fork and they already have donation links plastered everywhere?
Yeah… I would be a bit more concerned over making sure this is “above board” as it were.
Which… is honestly really shit to the actual yuzu devs who put the work in. And it isn’t like Nintendo is going to say “Wow, that really good emulator might not be the one we had taken down. Let’s actively not look and instead cry into our money”. If they want it down, they’ll look for a reason. And then REALLY quickly see it is the same codebase they had removed already.
I’m surprised you haven’t heard of Eden before this! It’s the choice for emulating on Android now! They’re very well established, and seem to be vouched for by all the ‘big’ names in the emulation and handhelds scene.
Obviously practicing your own caution is important, but Eden isn’t some unknown fly-by-nighter. They’re very, very much a known name now.
I don’t see anything that says they don’t understand Git or Github.
They know people will look for them on Github, and they do their official releases there. They host their code on the non-profit Codeberg site for reasons of their own. People can still fork from there. They just can’t click a button on Github to do it. They can, however, click a button on Codeberg to fork.
It sounds to me like they did understand all of this, and decided to let internet popularity work for them (host releases on Github for discoverability and fraud prevention) without giving up how they wanted to manage their code.
Why? It sounds like an old link description that they didnt update. Webdev likely isnt their top priority being emulation devs, and frankly, they may not care.
Github/codeberg are both git, so its pretty irrevelant which one you link to. They just host the git repos, which give no shits about what web platform they live on.
Well, the movie would be playable on any device. I have an Xbox, and my computers are Macs, so I have fewer options for running games, but anything can play video.
The other consideration is that most people aren’t going to pay to watch the video. They’ll watch it on YouTube with ads but they’re not gonna pay game money to watch it played.
bin.pol.social
Aktywne