mirror of
https://github.com/yuzu-emu/yuzu-emu.github.io.git
synced 2025-08-03 15:41:12 +00:00
Vort vort
This commit is contained in:
Matías Locatti
GitHub
parent
6d410c7063
commit
bac73ae5f5
327
site/content/entry/yuzu-progress-report-nov-2021/index.md
Normal file
327
site/content/entry/yuzu-progress-report-nov-2021/index.md
Normal file
|
|
@ -0,0 +1,327 @@
|
|||
+++
|
||||
date = "2021-12-04T12:00:00-03:00"
|
||||
title = "Progress Report November 2021"
|
||||
author = "GoldenX86"
|
||||
coauthor = "CaptV0rt3x"
|
||||
forum = 0
|
||||
+++
|
||||
|
||||
Hello yuz-ers! Welcome to November’s summary of changes. This month we offer you a full input rewrite, UI navigation with controllers, massive kernel changes resulting in
|
||||
improved performance and stability, and more.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Project Kraken
|
||||
|
||||
Boy what a treat [german77](https://github.com/german77) has for us.
|
||||
As we mentioned in the previous progress report, `Project Kraken`, our latest input rewrite, is now available to all users.
|
||||
|
||||
But what does it mean?
|
||||
Well, there are multiple goals, first of all is accuracy.
|
||||
Being closer to how the Nintendo Switch operates is always prefered.
|
||||
Plus simplifying and removing old redundant code makes maintenance and scalability a lot easier.
|
||||
Maybe most important of all is making all input event based instead of polling based.
|
||||
This means that instead of asking the controller what it did at regular intervals, the controller itself will inform its actions the moment the user inputs an action, this
|
||||
applies for buttons, triggers, sticks, motion, the whole deal.
|
||||
The end result is reduced input lag.
|
||||
|
||||
But that’s not all of it, Kraken also includes many bug fixes and new additions.
|
||||
Users can now invert or turn any button into a toggle (press again to release) in any emulated controller.
|
||||
Previously this was only possible on a limited variety of controllers.
|
||||
|
||||
{{< imgs
|
||||
"./toggle.png| Did someone say they wanted to beat Dark Souls with a driving wheel?"
|
||||
>}}
|
||||
|
||||
Buttons are named instead of numbered on non SDL input controllers, easing identification.
|
||||
|
||||
{{< imgs
|
||||
"./button.png| SDL input like native Nintendo controllers or XBox controllers will be numbered"
|
||||
>}}
|
||||
|
||||
While we recommend to use controllers without third party drivers, full [UDP cemuhook support](https://cemuhook.sshnuke.net/) is added to
|
||||
`Emulation > Configure… > Controls > Advanced > Enabled UDP controllers`.
|
||||
|
||||
Previously cemuhook was only used for UDP motion, but now this means even Android apps allow connection to yuzu now.
|
||||
Cemuhook provides a guide on how to set up UDP devices [here](https://cemuhook.sshnuke.net/padudpserver.html).
|
||||
|
||||
{{< imgs
|
||||
"./udp.png| There must be someone trying to play with a phone as a Joy-Con somewhere"
|
||||
>}}
|
||||
|
||||
Keyboard and mouse emulation is improved, allowing games that natively support USB mouse and keyboard inputs to function correctly.
|
||||
|
||||
{{< imgs
|
||||
"./km.png| Useful in games like Animal Crossing: New Horizons that accept an actual keyboard on the Switch"
|
||||
>}}
|
||||
|
||||
Additionally, there are hundreds of bugfixes in the backend, to list a few:
|
||||
|
||||
Dual Joy-Cons will now correctly reconnect instead of reverting to “any” input after a yuzu reboot.
|
||||
Analog triggers are properly mapped. This includes Gamecube controllers.
|
||||
Configuration parameters are shared on all emulated controller types.
|
||||
Battery level is now informed when available.
|
||||
Pressing a button will automatically reconnect the first player.
|
||||
Rumble on the right side is fixed.
|
||||
|
||||
For those interested, the [pull request](https://github.com/yuzu-emu/yuzu/pull/7255) description includes all the technical information on how Kraken now operates, including
|
||||
the internal changes to every subsystem.
|
||||
|
||||
[Subsequent](https://github.com/yuzu-emu/yuzu/pull/7472) [pull requests](https://github.com/yuzu-emu/yuzu/pull/7476) by [Morph](https://github.com/Morph1984) and german77
|
||||
provided further fixes and cleanups.
|
||||
|
||||
## Other input changes
|
||||
|
||||
A very requested feature is [controller navigation over UI elements](https://github.com/yuzu-emu/yuzu/pull/7452), and that’s exactly what german77 delivered.
|
||||
Currently there is support for the game list, profile selector (if the user created several profiles), and the controller applet pop-up.
|
||||
The feature is in its baby steps, so expect some rough edges for example in the controller applet or when trying to hold the stick, we are working on refining it.
|
||||
|
||||
Here’s an example on the GPD Win 3:
|
||||
|
||||
{{< imgs
|
||||
"./ui.mp4| Deck hype train, here we go!"
|
||||
>}}
|
||||
|
||||
When asking for the character’s name in `Detective Club: The Missing Heir`, the game spawned an error in Chinese and then crashed.
|
||||
The issue is rooted in a bad behaviour in how text is handled with the On-Screen Keyboard (OSK), there’s no need to ask for user confirmation on text that has been already
|
||||
confirmed.
|
||||
The resulting error message was in the wrong language due to using the wrong character encoding.
|
||||
Morph [addressed both issues](https://github.com/yuzu-emu/yuzu/pull/7303), and the game can be played now.
|
||||
|
||||
{{< imgs
|
||||
"./detective.png| Elemental, my dear yuzu (Detective Club: The Missing Heir)"
|
||||
>}}
|
||||
|
||||
german77 got tired of having to constantly modify the code when testing different types of emulated controllers, so he added a
|
||||
[toggle to allow any kind](https://github.com/yuzu-emu/yuzu/pull/7451), even the types games block natively.
|
||||
We don’t recommend to use this settting for normal gameplay, but if anyone wants to try it out, the option is in
|
||||
`Emulation > Configure… > General > Debug > Enable all Controller Types`.
|
||||
Expect some games to refuse to continue until an allowed emulated controller is selected.
|
||||
|
||||
If the user ignored the controller applet pop-up, the controllers would stay in configuration mode, not accepting input.
|
||||
german77 [changed this behavior](https://github.com/yuzu-emu/yuzu/pull/7465) to enable the controllers in such cases.
|
||||
|
||||
## Graphical fixes
|
||||
|
||||
One of the missing video formats is `VP8`, we didn’t implement it until now because there were no known games that used it, similar to `HEVC`.
|
||||
Turns out there are at least 3 known games using VP8, `Ty the Tasmanian Tiger`, `Diablo II: Resurrected`, and `Pokémon Brilliant Diamond/Shining Pearl`, so
|
||||
[epicboy](https://github.com/yuzu-emu/yuzu/pull/7326) shamelessly attacked his keyboard and implemented [VP8 support](https://github.com/yuzu-emu/yuzu/pull/7326) into yuzu.
|
||||
|
||||
{{< imgs
|
||||
"./vp8.mp4| Cue the fanfare (Pokémon Shining Pearl)"
|
||||
>}}
|
||||
|
||||
There are known issues with Pokémon VP8 decoding that we’re working to address.
|
||||
|
||||
Textures can be dividen on colour or depth formats, but everything changed when the [TCR](https://yuzu-emu.org/entry/yuzu-tcr/) attacked.
|
||||
|
||||
In OpenGL, a conversion method was missing for copying “incompatible” texture formats, like colour <> depth format copies, epicboy
|
||||
[got around this limitation](https://github.com/yuzu-emu/yuzu/pull/7349) by using the same method implemented in BGR <> RGB conversions we mentioned in the past.
|
||||
|
||||
Uncountable glitches are fixed, two notable examples are the shadows in `Luigi’s Mansion 3` and the cutscenes in `Bayonetta 2`.
|
||||
|
||||
{{< single-title-imgs
|
||||
"You can now focus on... gameplay (Bayonetta 2)"
|
||||
"./bayobug.mp4"
|
||||
"./bayohfix.mp4"
|
||||
>}}
|
||||
|
||||
|
||||
|
||||
{{< single-title-imgs
|
||||
"No more ghost shadows (Luigi's Mansion 3)"
|
||||
"./lm3hbug.mp4"
|
||||
"./lm3fix.mp4"
|
||||
>}}
|
||||
|
||||
With the release of `Pokémon Brilliant Diamond/Shining Pearl`, an [Unity](https://unity.com/) engine game, and `SHIN MEGAMI TENSEI V`, an
|
||||
[Unreal Engine 4](https://www.unrealengine.com/) game, we realised how much work needs to be done to solve stability and rendering issues affecting both engines.
|
||||
Since we don’t have that many GPU developers available (especially in finals months), we can only focus on one thing at a time, so first, Unity.
|
||||
|
||||
[Blit detection](https://yuzu-emu.org/entry/yuzu-progress-report-may-2021/#graphical-fixes) suffered some regressions with the introduction of the resolution scaler,
|
||||
[Project A.R.T.](https://yuzu-emu.org/entry/yuzu-art/).
|
||||
[Blinkhawk](https://github.com/FernandoS27) [fixed them and added texture format](https://github.com/yuzu-emu/yuzu/pull/7368) `D24S8` to `RGBA8` conversions to Vulkan,
|
||||
fixing several crashes affecting both APIs in this new old Pokémon release.
|
||||
|
||||
Note that despite the fixes, Vulkan still causes a Device Loss (GPU driver cuts the work) related crashes on Unity games.
|
||||
We recommend sticking to OpenGL for the moment.
|
||||
|
||||
Morph later included [some more fixes](https://github.com/yuzu-emu/yuzu/pull/7395) for this pull request.
|
||||
|
||||
Another issue affecting our lovely Pearl trainer (who would pick the male equivalent?) is an interesting corruption that can happen in battles and in reflections after some
|
||||
time or with certain attacks that cover the whole screen.
|
||||
One of the new features of yuzu’s TextureCache is support for full depth conversions, replacing the old “format deduction algorithm”, also known as guessing.
|
||||
|
||||
By [making full use of full depth conversions](https://github.com/yuzu-emu/yuzu/pull/7396), Blinkhawk fixed this interesting colourful bug affecting
|
||||
`Pokémon Brilliant Diamond/Shining Pearl`.
|
||||
|
||||
{{< single-title-imgs
|
||||
"What a trip, almost like a Disney song (Pokémon Brilliant Diamond)"
|
||||
"./bsdphbug.png"
|
||||
"./bsdpfix.png"
|
||||
>}}
|
||||
|
||||
One of the (many) missing texture formats is `S8_UINT`, a depth stencil one.
|
||||
Games like `Baldur’s Gate 1/2` and `Citizens of Space` make use of S8_UINT, so in the process of implementing it, Morph made a homebrew unit test to see the progress, as
|
||||
both games need other formats that are still missing and some other fixes.
|
||||
|
||||
Turns out, while [there is support for both OpenGL and Vulkan](https://github.com/yuzu-emu/yuzu/pull/7357) now, only NVIDIA declares support on Vulkan, meaning that any
|
||||
affected game running on an AMD or Intel GPU will need to stick to OpenGL to get proper rendering.
|
||||
|
||||
{{< single-title-imgs
|
||||
"Testing homebrew"
|
||||
"./s8uintbug.png"
|
||||
"./s8uintfix.png"
|
||||
>}}
|
||||
|
||||
[vonchenplus](https://github.com/vonchenplus) found a bug where image creation would include width size restrictions that wouldn’t apply to later updates and downloads,
|
||||
making OpenGL spam errors.
|
||||
[Properly handling those cases](https://github.com/yuzu-emu/yuzu/pull/7294) lets the driver calm down.
|
||||
Proper and cleaner code can also mean less driver overhead.
|
||||
|
||||
Continuing with the implementation of unsupported formats, vonchenplus added `R5G6B5_UNORM_PACK16` [textures to Vulkan](https://github.com/yuzu-emu/yuzu/pull/7291) and
|
||||
`S8_UINT_D24_UNORM` [globally](https://github.com/yuzu-emu/yuzu/pull/7466).
|
||||
Again, just like S8_UINT, AMD and Intel hardware lack Vulkan support for S8_UINT_D24_UNORM.
|
||||
|
||||
vonchenplus also [converted all usages of legacy attributes](https://github.com/yuzu-emu/yuzu/pull/7375) within shaders into generic attributes, since they were not
|
||||
supported by some graphics drivers, improving compatibility.
|
||||
|
||||
These four changes help `DRAGON QUEST BUILDERS`, but more work is required to make the game playable.
|
||||
|
||||
{{< imgs
|
||||
"./dqb.png| Missing graphics make the game not an optimal experience for now (DRAGON QUEST BUILDERS)"
|
||||
>}}
|
||||
|
||||
Back to fixes to the changes introduced by the resolution scaler, users reported that taking screenshots at 1x resolution multiplier resulted in saved images with a size
|
||||
higher than the rendering resolution of the game.
|
||||
A mix up resulted in the screenshot being saved at the window size instead of the game’s framebuffer size.
|
||||
epicboy [fixed the logic](https://github.com/yuzu-emu/yuzu/pull/7389) and we’re back to proper screenshot resolutions.
|
||||
|
||||
[liushuyu](https://github.com/liushuyu), our fantastic Webadmin, got reports of multiple GPU systems having crashes while running the Flatpak version of yuzu on Linux.
|
||||
Seems like the bundled version of mesa and ffmpeg will conflict on systems with different GPU vendors. Just the usual weird Gnome decisions.
|
||||
|
||||
liushuyu submitted [two](https://github.com/yuzu-emu/yuzu/pull/7431) [separate](https://github.com/yuzu-emu/yuzu/pull/7467) pull requests addressing this problem, but more
|
||||
edge cases continue to appear, so the battle isn’t over yet.
|
||||
|
||||
While we continue to work to win this war against Flatpak, please stick to using our appimages, or [manually build yuzu](https://yuzu-emu.org/wiki/building-for-linux/) if
|
||||
you prefer.
|
||||
It seems like the only way to solve this problem will be to just ship our own ffmpeg instead of Flatpak’s default one.
|
||||
|
||||
## UI changes
|
||||
|
||||
[MightyCreak](https://github.com/MightyCreak) has been working on changes in behaviour to the default light theme.
|
||||
Previously, yuzu would ignore the system wide theme, sticking to a light palette even if the system switched to a dark one.
|
||||
[Renaming the Light theme to Default, and allowing it to match the behaviour of the system theme](https://github.com/yuzu-emu/yuzu/pull/7330), makes for a more matched
|
||||
user experience.
|
||||
At the moment this behaviour only works correctly on Linux, Windows’ Qt doesn’t yet support system wide themes.
|
||||
|
||||
[Some degenerate writer](https://github.com/yuzu-emu/yuzu/pull/7342) decided that the previous missing keys error screen wasn’t clear enough, so it got replaced while
|
||||
refusing to elaborate any further.
|
||||
|
||||
{{< single-title-imgs
|
||||
"For some reason, people seem to forget what hyperlinks are for"
|
||||
"./keysbug.png"
|
||||
"./keysfix.png"
|
||||
>}}
|
||||
|
||||
While working on the resolution scaler and its included filters, Blinkhawk named FSR `AMD'S FIDELITYFX SR` on the bottom status bar.
|
||||
A bit too long, so Morph [renamed it](https://github.com/yuzu-emu/yuzu/pull/7369) to just `AMD FSR`.
|
||||
Small change, but more pleasing to the eyes.
|
||||
|
||||
{{< single-title-imgs
|
||||
"Better, don't you agree?"
|
||||
"./fsrbug.png"
|
||||
"./fsrfix.png"
|
||||
>}}
|
||||
|
||||
[Kewlan](https://github.com/Kewlan) brings a very nice addition to high refresh rate users.
|
||||
With the introduction of the FPS unlimiter that players can toggle by pressing `Ctrl + U` while playing, a cap was introduced in the configuration, to allow setting a
|
||||
multiplier of the native framerate as the upper limit.
|
||||
|
||||
So for example, if a game runs at 30FPS, and the user wants to limit it to 120FPS to better match the maximum refresh rate of their display, a 4x multiplier would be
|
||||
needed, and a 2x one would do if the game runs at 60FPS natively.
|
||||
|
||||
The problem with this approach is that as shown in the example, different games will run at different framerates natively, so a global value just won’t do.
|
||||
Kewlan [added support for framerate caps in the custom configuration](https://github.com/yuzu-emu/yuzu/pull/7404), users can access it by right clicking a game in yuzu’s
|
||||
list and selecting properties. This way, the user can set their prefered cap on a per-game basis.
|
||||
|
||||
{{< single-title-imgs
|
||||
"If you buy a new display, remember to manually incerase the refresh rate!"
|
||||
"./cap1.png"
|
||||
"./cap2.png"
|
||||
>}}
|
||||
|
||||
If the user wants a value that isn’t a multiple of the native framerate of the game, they can use software like
|
||||
[MSI Afterburner](https://www.guru3d.com/files-details/msi-afterburner-beta-download.html) to dial a custom limit.
|
||||
|
||||
There has been some extensive work to improve hotkeys.
|
||||
|
||||
[v1993](https://github.com/v1993) got a report that yuzu’s window will flicker if the user holds the Esc key when trying to exit fullscreen.
|
||||
[That won’t happen any more](https://github.com/yuzu-emu/yuzu/pull/7353).
|
||||
|
||||
german77 discovered that holding a hotkey would constantly spam it, that made him angry, and [this behaviour is no more](https://github.com/yuzu-emu/yuzu/pull/7355).
|
||||
|
||||
[heinarmann](https://github.com/heinermann) [replaced the emulation shortcuts and states](https://github.com/yuzu-emu/yuzu/pull/7419):
|
||||
|
||||
`Start` has been removed and `Continue` was moved to `Pause` when applicable.
|
||||
Exiting the emulator will now work while in fullscreen.
|
||||
`Restart` will no longer cause a crash.
|
||||
`Load Amiibo` was improved. We still have issues with several games when using this function, so consider it in a beta state.
|
||||
`TAS` [got it’s own submenu](https://github.com/yuzu-emu/yuzu/pull/7406) in `Tools > TAS`.
|
||||
|
||||
{{< single-title-imgs
|
||||
" "
|
||||
"./tasbug.png"
|
||||
"./tasfix.png"
|
||||
>}}
|
||||
|
||||
## Kernel fixes
|
||||
|
||||
Morph fixed [a compilation warning](https://github.com/yuzu-emu/yuzu/pull/7278) in the kernel `SVC::WaitSynchronization`, where the parameter "num_handles" was wrongly
|
||||
declared as unsigned integer when it was actually a signed integer.
|
||||
|
||||
heinermann discovered a bug in the kernel that crashed yuzu upon exiting.
|
||||
|
||||
This happened because dummy threads in the kernel weren't getting destroyed properly. When you exited yuzu during emulation or after stopping emulation, these threads
|
||||
stayed alive even though the kernel got destroyed, thus causing yuzu to crash.
|
||||
|
||||
[By making the kernel own these threads](https://github.com/yuzu-emu/yuzu/pull/7359), we ensure they get destroyed when the kernel gets destroyed.
|
||||
Thus the crash is mitigated.
|
||||
|
||||
## Yet more homebrew fixes
|
||||
|
||||
[All](https://github.com/yuzu-emu/yuzu/pull/7393) [these](https://github.com/yuzu-emu/yuzu/pull/7394) [PRs](https://github.com/yuzu-emu/yuzu/pull/7407) are part of the
|
||||
on-going effort to implement support for [Skyline](https://github.com/skyline-dev/skyline) modding framework in yuzu.
|
||||
|
||||
See progress [here](https://github.com/yuzu-emu/yuzu/issues/7392).
|
||||
|
||||
The framework's developer, [jam1garner](https://github.com/jam1garner) offered their assistance to work alongside the yuzu team to speed up this process.
|
||||
|
||||
The PRs mentioned here are just setting up the stage for larger changes that are yet to come.
|
||||
Thus the day when yuzu will fully support the Skyline framework, is not too far away.
|
||||
|
||||
[OatmealDome](https://github.com/OatmealDome) fixed a bug that caused some homebrew to not boot. The fix was to
|
||||
[pass default threadinfo when the kernel creates a thread](https://github.com/yuzu-emu/yuzu/pull/7320), thus allowing homebrew to boot.
|
||||
|
||||
## General changes and bugfixes
|
||||
|
||||
Not much to talk about in this section this time, mostly just service stubs and implementations.
|
||||
|
||||
`Animal Crossing: New Horizons` takes the spotlight [with](https://github.com/yuzu-emu/yuzu/pull/7283) [4](https://github.com/yuzu-emu/yuzu/pull/7285)
|
||||
[stubs](https://github.com/yuzu-emu/yuzu/pull/7287) to make the new 2.0.0 update playable. Thank you, german77 and Morph.
|
||||
|
||||
german77 gives `Just Dance 2022` [its own stub](https://github.com/yuzu-emu/yuzu/pull/7293) for the `EndFreeCommunication` service.
|
||||
|
||||
And finally, Morph [implements the](https://github.com/yuzu-emu/yuzu/pull/7482) `GetCompletionEvent` service for `Super Bomberman R Online`.
|
||||
Since the game requires online services, it won’t be playable for now.
|
||||
|
||||
## Future projects
|
||||
|
||||
`Project Gaia` continues to progress and be optimized as we speak, we're not that far away from starting internal testing on it.
|
||||
|
||||
That’s all folks! As always, thank you so much for your attention, and we’ll see you next time!
|
||||
|
||||
Special thanks to RodrigoTR and PacoA for their provided media.
|
||||
|
||||
|
||||
{{< article-end >}}
|
||||
Loading…
Reference in a new issue