IIRC it should just be a dedicated 5 GHz wireless radio in the console.
IIRC it should just be a dedicated 5 GHz wireless radio in the console.
RIn summary, the Wii U and the GamePad communicate with each other using 802.11n in the 5 GHz band. The console acts as an access point (AP) and the GamePad acts as its single client. Be as it may, Memahaxx also reported that the console’s operating system implemented the possibility of using two GamePads at once, albeit left unused.
RThe Copetti site
An in-depth analysis that explains how this console works internally
RReference here
VMemahaxx also reported that the console’s operating system implemented the possibility of using two GamePads at once, albeit left unused.
I mean seeing as reggie did say that, I'm glad it was at least explored
LThere have been other efforts as well. Let's see if I can dig them up again.
Another thing is Deck U that uses the Steam Deck as a Wii U gamepad for a PC running CEMU
Another thing is Deck U that uses the Steam Deck as a Wii U gamepad for a PC running CEMU
RInstalled bazzite-deck-gnome:testing on OLED to check Gnome (after multiple years of using KDE exclusively). I must say it does look slick, will be interesting to see how it fares in day-to-day usage.
Although I've already found some strange bug - bazzite menu (top left corner icon) doesn't seem to accept input (mouse clicks) from bluetooth keyboard for some menu entries at all (strange, like I mentioned). Whereas for touch input everything works correctly.
Although I've already found some strange bug - bazzite menu (top left corner icon) doesn't seem to accept input (mouse clicks) from bluetooth keyboard for some menu entries at all (strange, like I mentioned). Whereas for touch input everything works correctly.
KThat is odd, I'll see if I can reproduce it
Kthat menu is a fork of Logo Menu
KGitHub
Quick access menu for the GNOME panel with options that help ease the workflow for newcomers and power users alike. - GitHub - Aryan20/Logomenu: Quick access menu for the GNOME panel with options t...
Kcall it a soft fork since we keep it in sync
R@KyleGospo you don't have to rush it rn, because I can't seem to reproduce it now after -> gamescope -> desktop again.
RSeems to work correctly now
Rweird
ROK I take it back, something definately is not right with that menu, I'll fidget with it a bit more to establish steps where this will reproduce 100%.
RSeems to be some issue with the menu itself, I'm not experiencing (for now) any issues while interacting with other elements on the desktop
ROK I have steps to reproduce this issue. Good thing is that you don't even need bluetooth keyboard, you can reproduce it just by mixing touch and controller-cursor control schemes (right stick/touchpad and shoulder buttons).
This is on bazzite-deck-gnome:testing (installed about 6 hours ago, up to date) on OLED.
1) Turn on Steam Deck.
2) Go to desktop mode.
3) Using controller-cursor controls, click on top left corner menu icon to open menu.
4) Click (using above mentioned control scheme) on any menu item(s) of your choice - everything should work here.
5) Now, using touchscreen controls, open menu and tap on any menu item(s) of your choice. They should still launch properly.
=== This is where it breaks ===
6) Now, using controller-cursor controls again, try to launch any of the menu item(s)/button(s) you tapped at step (5).
7) All of them don't work, i.e. clicks via shoulder buttons / touchpad are completely ignored.
It seems that as long as you don't launch any menu entry with touch controls (tap), both controller-cursor and bluetooth keyboard/mouse will work. As soon as you launch any menu item with touch, then any subsequent attempt to launch given menu entry with controller-cursor and/or bluetooth kb/mouse will fail ('clicks' will be ignored by the menu). By that point, only clicks/taps via touch screen controls will work.
You need to restart your Deck completely to fix it - until you again use touch controls on the menu, where it breaks again.
@KyleGospo
This is on bazzite-deck-gnome:testing (installed about 6 hours ago, up to date) on OLED.
1) Turn on Steam Deck.
2) Go to desktop mode.
3) Using controller-cursor controls, click on top left corner menu icon to open menu.
4) Click (using above mentioned control scheme) on any menu item(s) of your choice - everything should work here.
5) Now, using touchscreen controls, open menu and tap on any menu item(s) of your choice. They should still launch properly.
=== This is where it breaks ===
6) Now, using controller-cursor controls again, try to launch any of the menu item(s)/button(s) you tapped at step (5).
7) All of them don't work, i.e. clicks via shoulder buttons / touchpad are completely ignored.
It seems that as long as you don't launch any menu entry with touch controls (tap), both controller-cursor and bluetooth keyboard/mouse will work. As soon as you launch any menu item with touch, then any subsequent attempt to launch given menu entry with controller-cursor and/or bluetooth kb/mouse will fail ('clicks' will be ignored by the menu). By that point, only clicks/taps via touch screen controls will work.
You need to restart your Deck completely to fix it - until you again use touch controls on the menu, where it breaks again.
@KyleGospo
RAlso I've found 3 more bugs while investigating above. I'll post about them later in the day.
CUsually best to use the github so the reports don't get lost in chat
Edid anybody try installing
wallpaper-engine-kde-pluginBuild and InstallGitHub
A kde wallpaper plugin integrating wallpaper engine - GitHub - catsout/wallpaper-engine-kde-plugin: A kde wallpaper plugin integrating wallpaper engine
ᕲit possible to change the username after install ?
Hi dont use wallpaper engine but i believe it is included in bazzite from what i remember from the readme?
JUniversal Blue
Hey all, Just wanted to let you know we’re working on some improvements for Mesa in :testing. For AMD users we’ve merged this patchset, which can offer up to +75% performance in ray tracing. Meanwhile, Nvidia users are getting a new Vulkan driver to test – NVK. This will be present on all non-nvidia builds after the next kernel release, and pr...
Jcheck it out ya'll
KShiny
NI'm tempted by this new shiny. Maybe I'll test it for Halo tonight.
JI am maxed out with the 7900XTX so I am grunting through it, but it's never too far away with fedora
KIt's preinstalled
KJust follow their usage instructions
Ajust tried the latest test build, the auto-rotate did not kick in.
KCan you check if you have a file in ~/.config/autostart?
AKLegionfix is correct, is the destination valid?
Amy autostart didn't have any other entries for the legionfix
A
Aso i'm guessing it didn't get automatically added?
MTry putting .desktop at the end of legionfix.
Alegionfix is an sh script though, not a desktop file
Abut sure, let me try
Aok, it's showing up now. also did a chmod +x on it
Alet me try and see if it works
ANope, still didn't kick in
ALet me try and see if the script even works, one sec
AWorks fine when I run it manually
KOdd, a shell script should execute in there
KTry adding it manually to autostart
KIf that works, send me the desktop file it makes
KAnd I'll simply change the script to create that instead of the link
Aadded it manually, this is the desktop entry it generated:
Alet me test it now
AHrm, still didn't work 
