30 Sep 2024 |
SigmaSquadron | In reply to @ar:is-a.cat why accidentally? s/ac/co , maybe?
| 16:51:43 |
SigmaSquadron | In reply to @ar:is-a.cat why accidentally? * s/ac/coin , maybe?
| 16:51:54 |
K900 | But yes coincidentally is the word I was trying to say | 16:52:01 |
ari ❄ | anyway, cherrypicked and now i'm going to thank my past self for buying a fast desktop | 16:53:08 |
K900 | Ryujinx is a pretty quick build anyway | 16:53:37 |
1 Oct 2024 |
| ldare373 joined the room. | 00:24:40 |
flameopathic | i'm having some very weird issues with gamescope on hyprland w/ nvidia, and have searched for hours for solutions but can't find any and don't know where to open an issue, if someone would be willing to help me here. here are my issues:
- no window opens when opening through steam launch options
- window opens when launching from command line, but then more weirdness occurs
- set resolution and fullscreen, steam app inside of gamescope looks good, but when the game opens, the black bars hiding the rest of my screen are replaced with a blur and my cursor is offset
- expected black bars only reappear when using gamescope to scale game, but i want to run at native resolution
all of this is just for me to be able to have my games run at a specific resolution on a specific part of my screen with no distractions, so gamescope seems like the way to go but if there's another solution, i'd love to escape this hell
| 00:36:57 |
K900 | gamescope, hyprland AND nvidia | 05:38:08 |
K900 | That's a combo | 05:38:12 |
aidalgol | I've had success with gamescope on nvidia, but with Plasma Wayland. | 06:09:15 |
aidalgol | hyprland is wl-roots based and Plasma is not, correct? | 06:09:26 |
K900 | Hyprland is now on their own custom thing | 06:10:14 |
K900 | Which is extremely bad | 06:10:18 |
ldare373 | In reply to @aidalgol:matrix.org hyprland is wl-roots based and Plasma is not, correct? Hyprland recently left wl-roots. more here | 06:10:24 |
ldare373 | In reply to @k900:0upti.me Hyprland is now on their own custom thing beat me to it 😆 | 06:11:16 |
Atemu | In reply to @k900:0upti.me Which is extremely bad How so? It's working mighty fine for me and has so practically since Hyprland switched to it | 07:07:39 |
Atemu | Some things don't work quite yet such as DRM-leasing | 07:07:50 |
Atemu | But such is Wayland... | 07:07:56 |
K900 | I've looked at the code | 07:09:03 |
K900 | It was not good | 07:09:06 |
Atemu | Oh I believe you on that | 10:39:13 |
Atemu | But it works well | 10:39:16 |
Atemu | The only thing that may rival it in terms of features and just generally working (which is quite a standard for Wayland still) is KDE and that has, uh, other issues | 10:40:31 |
Marie | i'm running into amdgpu crashes when trying to play half-life: alyx :/ the error message looks a lot like it's this: https://gitlab.freedesktop.org/drm/amd/-/issues/1974 It's not NixOS specific, also tried this on Arch, same result. Has anyone here experienced this before and maybe found a workaround, or maybe just an idea?
amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=2630653, emitted seq=2630655
amdgpu 0000:03:00.0: amdgpu: Process information: process vrcompositor.re pid 25060 thread RenderThread pid 25085
amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
| 12:49:51 |
K900 | That's just a GPU crash | 12:51:07 |
K900 | Probably the game is doing something wrong | 12:51:22 |
K900 | Kernel 6.12 should improve crash recovery a lot | 12:51:30 |
K900 | But if the GPU crashes, well, that's usually it for the game | 12:51:38 |
Marie | i tried both native and proton half life: alyx, and it happens at the exact same stage in the game | 12:54:12 |
K900 | Could be a specific shader | 12:54:52 |