.NET Runtime VS Ryujinx

Also, it seems that initial memory settings have a big effect on mobile, this is a fix that will make it for 7.0.4 (April): https://github.com/dotnet/runtime/pull/80849

looked it up and engine.cpp seems to only be 8.5k lines, which doesn't seem super unreasonable to work with. It ain't no gc.cpp that's for sure.

Threading.Channel has more or less replaced all the concurrent queue alternatives for me. channels have the benefit of nonblocking wait for when the channel can be written.

My teammate created an issue on GitHub: the developers fixed the order of arguments and added a test.

i have tried with an adapted .editorconfig but even using the "official" dotnet team editorconfig

Technically Mono supports RISC-V, so you can get .NET code running on it. Also it looks like if you're willing to go through messy and poorly documented build processes you can build CoreCLR on RISC-V: https://github.com/dotnet/runtime/issues/36748

So proper support is likely coming soonish, I'd guess by the time .NET 8 comes out.

There's an issue on simplifying WebSockets specifically https://github.com/dotnet/runtime/issues/77060 that may be of interest.

See CLR is also using left/right for its not-quite-binary-tree in SortedSet. Though this also uses the Enum-As-Discriminator trick instead of boolean/array. I know the JVM also has/uses left/right but I can't find the backing source file right now.

I've found an issue on github without clear answer: List should have Index & Range method overloads

The issue is that the current GTK UI causes black screen on Vulkan in fullscreen mode, it is a UI framework issue. The Discover version is still using GTK I believe. There also is no "nightly" version of Ryujinx, and the Avalonia builds already have updaters in them. Issue thread here: https://github.com/Ryujinx/Ryujinx/issues/3874

Feel free to use this PR while it gets fixed and reviewed https://github.com/Ryujinx/Ryujinx/pull/3616

The only update I'd need for Ryujinx on mac is fixing the V-Sync issue. Everything else is perfect for me! https://github.com/Ryujinx/Ryujinx/issues/3906

Wtf is wrong with you? You were already answered in this post. It is currently a work in progress available in a Pull Request on github. Download the build and test if you want it so badly. https://github.com/Ryujinx/Ryujinx/pull/3616

https://github.com/Ryujinx/Ryujinx/wiki/Ryujinx-Setup-&-Conf...

> Your Switch keys and either your dumped firmware or recent game cartridge untrimmed XCI

> Your dumped Nintendo Switch games or homebrew

You don't need a hacked switch if you can find the homebrew apps / games / firmware on the internet and if you can find a donor set of keys. But that enters questionable territory

I hadn't seen this before and I was curious what approach Ryujinx and Yuzu (mentioned here) take to emulate the GPU. Both appear to emulate the actual hardware rather than patch the guest to intercept graphics calls in some way. This includes recompiling Maxwell shader machine code into host-compatible shaders (GLSL or whatever). Impressive.

  1. https://github.com/Ryujinx/Ryujinx/blob/master/Ryujinx.Graphics.Shader/Decoders

Here is the wiki page with a step-by-step to extract the keys: https://github.com/Ryujinx/Ryujinx/wiki/Keys

The quad to tris conversion and also the methods used to mitigate the impact of updates to buffers in the middle of a render pass.

I've tried this build and the one in the drive. It did improve the FPS from about 15 to 20 when looking north, but still not getting above 20.

Both downloads (game and update) are virus free and legit, you'll need this build of Ryujinx: https://github.com/Ryujinx/Ryujinx/pull/3832 Make sure "expand DRAM Size to 6GB" is OFF, as that caused a crash on boot for me when on.