yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2025-06-16 15:21:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

byte suggestions

Browse source 
Co-authored-by: liamwhite <liamwhite@users.noreply.github.com>
This commit is contained in:
Matías Locatti 2022-06-12 15:10:46 -03:00 committed by GitHub
parent 76e4857f96
commit 7afeb9e209
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
site/content/entry/yuzu-progress-report-may-2022/index.md
View file

@ -91,19 +91,16 @@ Fermi GPU users rejoyce.
>}} >}}
One of the important parts of yuzu's graphical emulation is the need to translate small sets of GPU instructions, called `macros`. One of the important parts of yuzu's graphical emulation is the need to translate small sets of GPU instructions, called `macros`.
yuzu uses a Just-in-Time (JIT) compiler to emulate these macros in a performant way. yuzu uses a Just-in-Time (JIT) compiler to execute these macros in a performant way. It provides a performance boost of about 10% over interpretation in most cases.
MacroJIT is an optimization applied over this process, it manages to provide a performance boost of plus 10%, more or less.
byte[] found that macro could try to access a parameter that was too far outside the bounds of what it was supposed to be accessing. byte[] found that due to emulation inaccuracies, sometimes a macro could try to access a parameter that was too far outside the bounds of what it was supposed to be accessing. This could crash the emulator without a single trace as to why in some cases.
Usually the end result of this behaviour would be the emulator crashing.
{{< gh-hovercard "8319" "One less reason for annoying crashes." >}} {{< gh-hovercard "8319" "One less reason for annoying crashes." >}}
Now, while on the subject or macros, MME, or Macro Method Expander, are small programs sent to the GPU when booting a game, responsible for executing methods (anything that changes the current status of the GPU). Additionally, byte[] added the option to {{< gh-hovercard "8320" "dump all macros" >}} used by a game for debugging purposes.
byte[] added the option to {{< gh-hovercard "8320" "dump such MME macros" >}} for debugging purposes.
But why are MME macros important enough to merit their own dump mechanism? But why are macros important enough to merit their own dump mechanism?
Turns out, the `Nintendo 64` emulator (*totally not outside Nintendo's Terms of Service*), included with the `Nintendo Switch Online` subscription, reasigns the same macros multiple times, each with different code. Turns out, the `Nintendo 64` emulator (*totally not outside Nintendo's Terms of Service*), included with the `Nintendo Switch Online` subscription, reassigns the same macros multiple times, each time with different code. yuzu incorrectly appended the new code to the end of the macro in this case, instead of replacing the existing code.
{{< gh-hovercard "8328" "Properly clearing that code" >}} on upload address assignments allows the NSO Nintendo 64 emulator to be playable. {{< gh-hovercard "8328" "Properly clearing that code" >}} on upload address assignments allows the NSO Nintendo 64 emulator to be playable.
Time to re-enjoy those classics! Time to re-enjoy those classics!