yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2025-06-29 22:34:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

last fix before PR, first try

Browse source
This commit is contained in:
Matías Locatti 2020-11-07 03:36:28 -03:00 committed by GitHub
parent 2404681275
commit 15dd172783
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
site/content/entry/yuzu-progress-report-oct-2020/index.md
View file

@ -25,7 +25,7 @@ The second part took care of implementing the `Controller Applet`: a service use
And now, at last, comes the third part of this project, introducing bug fixes, `Controller Profiles`, and also an overhaul to the implementation of `Rumble` realized by [german77](https://github.com/german77). And now, at last, comes the third part of this project, introducing bug fixes, `Controller Profiles`, and also an overhaul to the implementation of `Rumble` realized by [german77](https://github.com/german77).
{{< imgs {{< imgs
"./01_load_profile.gif | Loading a profile for a Sony DS4 controller." "./load_profile.gif| Loading a profile for a Sony DS4 controller."
>}} >}}
`Controller Profiles` had been a placeholder since Part 1 of `Project Mjölnir`. They allow users to set up the configuration of their gamepads and save them in a file, which can be loaded and marked with a distinctive name. This is particularly useful for people who own more than one type of controller, since they store all button and axis information, as well as the port and engine used to read the input data. Changing between one configuration and another then becomes as simple as clicking a dropdown menu and choosing the desired profile, and all the settings will then be applied automatically. Users now can create a profile by simply clicking on the "New" button and writing a descriptive name to save it. `Controller Profiles` had been a placeholder since Part 1 of `Project Mjölnir`. They allow users to set up the configuration of their gamepads and save them in a file, which can be loaded and marked with a distinctive name. This is particularly useful for people who own more than one type of controller, since they store all button and axis information, as well as the port and engine used to read the input data. Changing between one configuration and another then becomes as simple as clicking a dropdown menu and choosing the desired profile, and all the settings will then be applied automatically. Users now can create a profile by simply clicking on the "New" button and writing a descriptive name to save it.
@ -46,7 +46,7 @@ Previously, some people using certain types of wireless controllers reported in-
- Successive state changes with the same amplitude value (i.e. identical amplitude vibrations) are excluded in order to reduce the amount of state changes sent into the device. - Successive state changes with the same amplitude value (i.e. identical amplitude vibrations) are excluded in order to reduce the amount of state changes sent into the device.
{{< imgs {{< imgs
"./02_configure_vibration.png | Vibration Configuration Window." "./configure_vibration.png| Vibration Configuration Window."
>}} >}}
These changes were enough to fix the stutters experienced by these users. In order to toggle `Accurate Vibrations` on, the user should navigate to `Emulation > Configure... > Controls` and click on "Configure" under the "Vibrations" tickbox. They can also change the intensity of the vibrations for each player, if desired. These changes were enough to fix the stutters experienced by these users. In order to toggle `Accurate Vibrations` on, the user should navigate to `Emulation > Configure... > Controls` and click on "Configure" under the "Vibrations" tickbox. They can also change the intensity of the vibrations for each player, if desired.
@ -56,7 +56,7 @@ Furthermore, an additional check has been implemented when initializing a vibrat
On top of these changes, work has been done so that anyone can plug in their favorite controller and, if it supports vibrations, all configuration related to it will be applied automatically. In the case the controller doesn’t, however, rumble will be disabled on the backend. On top of these changes, work has been done so that anyone can plug in their favorite controller and, if it supports vibrations, all configuration related to it will be applied automatically. In the case the controller doesn’t, however, rumble will be disabled on the backend.
{{< imgs {{< imgs
"./03_mapping.png | Vibration Configuration Window." "./mapping.png| Vibration Configuration Window."
>}} >}}
It is worth noting that, in case the automatic configuration process fails, users can map their analog sticks manually by clicking on any of the axis mappings. This solves issues with certain controllers that have their axis mapped as digital buttons. It is worth noting that, in case the automatic configuration process fails, users can map their analog sticks manually by clicking on any of the axis mappings. This solves issues with certain controllers that have their axis mapped as digital buttons.
@ -151,7 +151,7 @@ In a minor change to Vulkan, [Rodrigo](https://github.com/ReinUsesLisp) [changed
"./vklist.png| One of our developer's system, gotta render 'em all!" "./vklist.png| One of our developer's system, gotta render 'em all!"
>}} >}}
The current method follos these rules: The current method follows these rules:
- Priority will be given to the GPU vendor following the `Nvidia > AMD > Intel` order. - Priority will be given to the GPU vendor following the `Nvidia > AMD > Intel` order.
- Dedicated hardware will take priority over integrated. For example an RX 570 will have a higher priority than an Intel UHD630. - Dedicated hardware will take priority over integrated. For example an RX 570 will have a higher priority than an Intel UHD630.
- The device name will be considered, a GTX 1650 will be selected over a GTX 1060. Most of the time, newer architecture generations offer better performance benefits than pure raw performance. - The device name will be considered, a GTX 1650 will be selected over a GTX 1060. Most of the time, newer architecture generations offer better performance benefits than pure raw performance.