In particular, 1.5x is the only resolution at which the included LCD3x and HQ3x filters display correctly:
<img width="481" alt="sc

I was not able to find any instructions on where to put the keys.prod file.
Someone in discord told me it goes into ~/.local/share/yuzu/keys/
That folder was not even created by yuzu.

I feel like the folder should be created by yuzu at runtime and that there should be instructions on where to put the keys.prod file in the first place.

I was using build 20200324-2e484ccc7 for this.

Is there a way to let the citra gdbstub automatically break on unmapped memory access? Right now, citra handles unmapped access gracefully and only spits out an error in the log. The real 3DS hardware will crash on unmapped memory access but the current Rosalina gdbstub will at least break with SIGSEGV and let you examine the process remains.
Would be nice if it was possible with citra as well ..

https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

Before we have a good fix for #63 we should manually verify the qemu args somehow. We may have to copy-paste code from qemu or something. In the very least we should be aware of incompatible config options exposed in the UI (maybe we can't check additional args).

People seem to use Vulkan despite the d3d12 backend being superior, so add a message so people stop asking which backend is better.

PCSX2 version:
1.5-930f07d

Description of the issue:
Currently the source code for parsing 7-patch codes expects the patch code to be in the format:
7aaaaaaa 00t0vvvv
where "aaaaaaa" is the address to modify, "vvvv" is the value to compare to, and "t" signals whether to do an and, or, or xor and whether it is 8-bit or 16-bit. You can see the list of patch codes [here](https://

IManagerForApplication EnsureIdTokenCacheAsync is not implemented.

Service description:

Switchbrew | Reswitched

EnsureIdTokenCacheAsync() -> object<nn::account::detail::IAsyncContext>

Returns an #IAsyncContext.

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

Below, all pull request that are currently closed, with an indication on their status.

This overview should be kept up to date, to prevent uncertainty. Also, having this up to date overview avoids spending repeated efforts to ascertain the state of closed pull requests.

Possible states per pull request:

• Invalid (explain why it wasn't good)
• Obsolete (should reference replacement pull request

RPCS3 has this page: http://rpcs3.net/quickstart
And a relevant dialog the first time you boot it.

The most important/relevant thing for us would be a quickstart guide for downloading and decrypting/installing the firmware.

When using the N64 plugins, some of the options can be very hard to understand what they actually do. By having some form of description (showing a popup when hovering over the option, having the description under each option, link to a website with detailed documentation in the application, readme txt file with the explanations, or any other way that you may implement a description) it will help

I know it wouldn't be a trivial amount of work but could you @jpd002 consider writing a PS2 hardware documentation like the ones available for the PS1, GBA and DS? Perhaps in collaboration with the PCSX2 devs? Presently not many people understand PS2 hardware thus both Play and PCSX2 lack contributors.
I am talking about something like this
https://github.com/simias/psx-guide/blob/master/guide.t

From my perspective the new documentation system at https://github.com/libretro/docs has been a very big success.

Here is how it looks on the public site: https://buildbot.libretro.com/.docs/

There are several regular libretro docs contributors, and the github/PR system means that there is a good way to track, approve, and when necessary undo changes to the docs.

Would the Lakka devs cons

Can anyone help me out with this error? I don't know what to change my bundle identifier to for this to work? @gabrieloc

The current documentation references fceux, which is not compatible with recent versions of desmume. The options here are:

• Create our own documentation which fully documents the API
• Support all of FCEUX's API

I'd personally recommend the latter since FCEUX offers a lot of useful features like gui.savescreenshotas which would be a lot more efficient than `gd.createFromGdStr(gui.gdscree

README refers to http://visi.kenshoto.com/ for additional information, but that site can't be contacted. More specifically, "visi.kenshoto.com" or "kenshoto.com" domain names can't be resolved, including when using Google's DNS 8.8.8.8. This happens at least for 2nd day.

Note that without that site, the README barely gives any information about the project, for example Vdb's descriptions starts

Parsing error on this sample: https://app.any.run/tasks/2be2b38f-4de2-4b48-8ae5-67bda9eecbaf

-------------------------------------------------------------------------------
PARSING VBA CODE:
INFO     parsed Sub z55e6df583 ([ByVal s2b7d47c629 as String]): 14 statement(s)
INFO     parsed Sub Document_Open (): 5 statement(s)
INFO     parsed Function tfaca84885f ([ByVal zd77f34558c as Varian