u/ReanimatedCyborgMk-I

At random intervals, I will experience the "slow network, lower your bitrate" error for a period of seconds when streaming from Sunshine to Moonlight.

This appears across both clients I use wirelessly:

• Thinkpad P14s Gen 2 (11th gen intel + nvidia t500)
• Steam Deck OLED

The host is a Cachy OS (KDE) machine running Sunshine, with a 9800X3D and RTX 5080, streaming at 1440p 120fps (however, this behaviour manifested even on a lower spec machine, 7700 / 9060 XT + at lower resolution) which is connected to the router (EE WiFI 7) via Cat6 ethernet. Ping testing to the router is sub1ms response times as well. I also have an EE Smart WiFi Pro "mesh extender" wired to a switch (all backhaul cat6) in another room to extend coverage in the house.

The laptop gets it worse, but I experience it also on the Steam Deck. Connecting the laptop via wired ethernet to the router does seem to alleviate this but I haven't been able to test on the Steam Deck. And it's not really a viable solution.

Sometimes it disappears in a few seconds, others I the only way to fix this has been to disable wifi then re-enable, or restart my Steam Deck. And this is without anything being downloaded in the background.

This is even happening when I am sat no more than 3m away from the router with no objects blocking the path

Are there any suggestions on things I can try out here? I'm seriously considering picking up a proper mesh system later in the year when I have the money + time to set it up.

At random intervals, I will experience the "slow network, lower your bitrate" error for a period of seconds when streaming from Sunshine to Moonlight.

This appears across both clients I use wirelessly:

• Thinkpad P14s Gen 2 (11th gen intel + nvidia t500)
• Steam Deck OLED

The host is a Cachy OS (KDE) machine running Sunshine, with a 9800X3D and RTX 5080, streaming at 1440p 120fps (however, this behaviour manifested even on a lower spec machine, 7700 / 9060 XT + at lower resolution) which is connected to the router (EE WiFI 7) via Cat6 ethernet. Ping testing to the router is sub1ms response times as well. I also have an EE Smart WiFi Pro "mesh extender" wired to a switch (all backhaul cat6) in another room to extend coverage in the house.

The laptop gets it worse, but I experience it also on the Steam Deck. Connecting the laptop via wired ethernet does seem to alleviate this on the laptop but I haven't been able to test on the Steam Deck.

Sometimes it disappears in a few seconds, others I the only way to fix this has been to disable wifi then re-enable, or restart my Steam Deck. And this is without anything being downloaded in the background.

This is even happening when I am sat no more than 3m away from the router with no objects blocking the path

Are there any suggestions on things I can try out here? I'm seriously considering picking up a proper mesh system later in the year when I have the money + time to set it up.

I purchased an item from an online vendor (I won't say which, but they are Chinese w/ operations in the UK + EU) that significantly differs from the spec advertised; I used my physical paypal credit card instead of checking out with paypal to pay for it (didnt see it as an option at the time but apparently it is). When I tried managing it with the vendor I had a couple of issues and was advised by Paypal not to return it until I'd raised a dispute, I did as much and

Now this was about 40 days ago when I raised the SNAD dispute, got told several times I'd have an update the first week of may (with no guarantee or forecast of when an update would come), then last week I was finally asked "does the item work when plugged in? does the listing say it was X instead of Y?" despite me having already detailed my problem (which isn't that it didn't work, it's that the item is a completely different spec + model)

I've replied telling them my problem in detail and also sending a link + screenshot of the listing compared to what I received to showcase my problem. Now when I've chased again this week, I've been told to expect an update within 7-10 days, and that the dispute was stuck with their security team (and that this was caused by me using my PP credit card to checkout instead of checking out via paypal)

Is this normal? I've seen a few comments about disputes dragging out, as well as just general issues with PP customer service these days. I've been on the phone a good 6-7 times about this, some of which the agents have just dropped the line because I've insisted that no, being told to keep waiting isn't good enough without a real forecast of when it'll come, and another where they directed me to the PP credit team which I think are based out of Ireland (and apologetically told me I was in the wrong space)

I recently picked up a Lindy 32118 EDID to clone my 1440p display through. Had it clone the display, it seems to work headless without issues. HOWEVER, it appears that if I enable HDR, it will stream no issues when the monitor is on, and if I turn the monitor off within the same session it will still stream. After a reboot however, if I reboot the machine, I can connect headless via SSH and see snshine is running, but if I try to connect it will get stuck at the RTSP handshake and either throw up an error 110 or error 0

Are there any suggestions you would make apart from disabling HDR?

Output from Sunshine troubleshooting logs:

[2026-05-17 11:05:11.321]: Info: Found default monitor by name: sink-sunshine-stereo.monitor

[2026-05-17 11:05:11.331]: Info: Opus initialized: 48 kHz, 2 channels, 512 kbps (total), LOWDELAY

[2026-05-17 11:05:20.827]: Error: Initial Ping Timeout

[2026-05-17 11:05:20.830]: Info: Setting default sink to: [alsa_output.usb-MediaTek_Inc_Razer_Kraken_V4_0000000000000000-00.analog-stereo]

[2026-05-17 11:05:20.891]: Info: 192.168.1.122: Ping Timeout

[2026-05-17 11:05:51.552]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //

[2026-05-17 11:05:51.552]: Info: Trying encoder [nvenc]

[2026-05-17 11:05:51.552]: Info: Screencasting with KMS

[2026-05-17 11:05:51.552]: Info: /dev/dri/card0 -> amdgpu

[2026-05-17 11:05:51.554]: Info: /dev/dri/card1 -> nvidia-drm

[2026-05-17 11:05:51.554]: Info: Found monitor for DRM screencasting

[2026-05-17 11:05:51.554]: Info: Found connector ID [132]

[2026-05-17 11:05:51.554]: Info: Found cursor plane [57]

[2026-05-17 11:05:51.554]: Info: Creating encoder [h264_nvenc]

[2026-05-17 11:05:51.554]: Info: Color coding: SDR (Rec. 601)

[2026-05-17 11:05:51.554]: Info: Color depth: 8-bit

[2026-05-17 11:05:51.554]: Info: Color range: JPEG

[2026-05-17 11:05:51.556]: Info: Streaming bitrate is 1000000

[2026-05-17 11:05:51.590]: Info: Creating encoder [hevc_nvenc]

[2026-05-17 11:05:51.590]: Info: Color coding: SDR (Rec. 601)

[2026-05-17 11:05:51.590]: Info: Color depth: 8-bit

[2026-05-17 11:05:51.590]: Info: Color range: JPEG

[2026-05-17 11:05:51.591]: Info: Streaming bitrate is 1000000

[2026-05-17 11:05:51.618]: Info: Creating encoder [av1_nvenc]

[2026-05-17 11:05:51.618]: Info: Color coding: SDR (Rec. 601)

[2026-05-17 11:05:51.618]: Info: Color depth: 8-bit

[2026-05-17 11:05:51.618]: Info: Color range: JPEG

[2026-05-17 11:05:51.619]: Info: Streaming bitrate is 1000000

[2026-05-17 11:05:51.649]: Info: Screencasting with KMS

[2026-05-17 11:05:51.649]: Info: /dev/dri/card0 -> amdgpu

[2026-05-17 11:05:51.649]: Info: /dev/dri/card1 -> nvidia-drm

[2026-05-17 11:05:51.649]: Info: Found monitor for DRM screencasting

[2026-05-17 11:05:51.649]: Info: Found connector ID [132]

[2026-05-17 11:05:51.649]: Info: Found cursor plane [57]

[2026-05-17 11:05:51.649]: Info: Creating encoder [hevc_nvenc]

[2026-05-17 11:05:51.649]: Info: Color coding: SDR (Rec. 709)

[2026-05-17 11:05:51.649]: Info: Color depth: 10-bit

[2026-05-17 11:05:51.649]: Info: Color range: JPEG

[2026-05-17 11:05:51.650]: Info: Streaming bitrate is 1000000

[2026-05-17 11:05:51.679]: Info: Creating encoder [av1_nvenc]

[2026-05-17 11:05:51.679]: Info: Color coding: SDR (Rec. 709)

[2026-05-17 11:05:51.679]: Info: Color depth: 10-bit

[2026-05-17 11:05:51.679]: Info: Color range: JPEG

[2026-05-17 11:05:51.680]: Info: Streaming bitrate is 1000000

[2026-05-17 11:05:51.710]: Info:

[2026-05-17 11:05:51.710]: Info: // Ignore any errors mentioned above, they are not relevant. //

[2026-05-17 11:05:51.710]: Info:

[2026-05-17 11:05:51.710]: Info: Found H.264 encoder: h264_nvenc [nvenc]

[2026-05-17 11:05:51.710]: Info: Found HEVC encoder: hevc_nvenc [nvenc]

[2026-05-17 11:05:51.710]: Info: Found AV1 encoder: av1_nvenc [nvenc]

[2026-05-17 11:05:51.742]: Info: New streaming session started [active sessions: 1]

[2026-05-17 11:05:51.767]: Info: CLIENT CONNECTED

[2026-05-17 11:05:51.818]: Info: /dev/dri/card0 -> amdgpu

[2026-05-17 11:05:51.819]: Info: /dev/dri/card1 -> nvidia-drm

[2026-05-17 11:05:51.819]: Info: Found display [wayland-0]

[2026-05-17 11:05:51.819]: Info: Found interface: zxdg_output_manager_v1(31) version 3

[2026-05-17 11:05:51.819]: Info: Found interface: zwp_linux_dmabuf_v1(57) version 5

[2026-05-17 11:05:51.819]: Info: Found interface: wl_output(75) version 4

[2026-05-17 11:05:51.819]: Info: Resolution: 1920x1080

[2026-05-17 11:05:51.819]: Info: Offset: 0x0

[2026-05-17 11:05:51.819]: Info: Logical size: 1920x1080

[2026-05-17 11:05:51.819]: Info: Name: DP-1

[2026-05-17 11:05:51.819]: Info: Found monitor: USM LINDY32118_V0

[2026-05-17 11:05:51.819]: Info: -------- Start of KMS monitor list --------

[2026-05-17 11:05:51.819]: Info: Monitor 0 is DP-1: USM LINDY32118_V0

[2026-05-17 11:05:51.819]: Info: --------- End of KMS monitor list ---------

[2026-05-17 11:05:51.819]: Info: Screencasting with KMS

[2026-05-17 11:05:51.819]: Info: /dev/dri/card0 -> amdgpu

[2026-05-17 11:05:51.820]: Info: /dev/dri/card1 -> nvidia-drm

[2026-05-17 11:05:51.820]: Info: Found monitor for DRM screencasting

[2026-05-17 11:05:51.820]: Info: Found connector ID [132]

[2026-05-17 11:05:51.820]: Info: Found cursor plane [57]

[2026-05-17 11:05:51.820]: Info: Creating encoder [hevc_nvenc]

[2026-05-17 11:05:51.820]: Info: Color coding: SDR (Rec. 709)

[2026-05-17 11:05:51.820]: Info: Color depth: 10-bit

[2026-05-17 11:05:51.820]: Info: Color range: MPEG

[2026-05-17 11:05:51.841]: Info: Streaming bitrate is 21388000

[2026-05-17 11:05:51.870]: Info: Minimum FPS target set to ~60fps (16.6667ms)

[2026-05-17 11:05:52.233]: Info: Setting default sink to: [sink-sunshine-stereo]

[2026-05-17 11:05:52.233]: Info: Found default monitor by name: sink-sunshine-stereo.monitor

[2026-05-17 11:05:52.241]: Info: Opus initialized: 48 kHz, 2 channels, 512 kbps (total), LOWDELAY

[2026-05-17 11:06:52.116]: Info: CLIENT DISCONNECTED

[2026-05-17 11:06:52.118]: Info: Setting default sink to: [alsa_output.usb-MediaTek_Inc_Razer_Kraken_V4_0000000000000000-00.analog-stereo]

[2026-05-17 11:07:39.095]: Info: Web UI: [127.0.0.1] -- not authorized

[2026-05-17 11:07:39.101]: Info: Web UI: [127.0.0.1] -- not authorized

System specs:

Cachy OS (KDE)

RTX 5080 w/ NVIDIA 595.71.05 drivers

Ryzen 9800X3D

For the last year and especially the last few months we've had constant drop outs at random, especially in the afternoon and evening, where our area suffers an outage and broadband services can be down for anywhere from under an hour to a sizeable chunk of the day. This is especially bad as I use the same ISP for my mobile services + our area has terrible coverage, so hotspotting off 5G isn't really an option, and I work from home so need access to broadband services.

I complained to my ISP and after politely pushing through the line of "our guarantee only applies after X days" spoke to someone who offered to comp me for a month's service. So that's a few quid saved.

EDIT: Thanks to u/hairymoot as this set of launch options they've provided has fixed the issue (make sure to force Proton Experimental)

VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader,VK_NV_raw_access_chains %command%

ORIGINAL POST:

I'm currently running an RTX 5080 on the latest stable release of CachyOS with the 595.71.05 drivers and have observed a couple of UE5 games that seem to be crashing

The two I've seen this with so far are:

• Nuclear Nightmare
• '83

This is the crash I get:

https://preview.redd.it/scnd248lrxzg1.png?width=705&format=png&auto=webp&s=af35fbe8b7d695e2143be6ca733f20412d31b028

I've tried both experimental, cachy, GE etc and that doesn't seem to get around this problem. In either instance, it appears downgrading to proton 8.0-5 or proton 7.0-6 does launch the games, but then you can't connect to other servers

https://preview.redd.it/b106inc4rxzg1.png?width=1582&format=png&auto=webp&s=32a7f52a777e83a977323cec83cb9f5e63a19975

What I've been able to glean off ProtonDB is this is down to recent nvidia drivers not playing nicely with dx12 (sounds like they never did to begin with)

Setting launch options to '-dx11' does allow me to launch Nuclear Nightmare, but '83 is a game that supports neither dx11 or vulkan

Before people laugh me out the door, I was originally gaming with an RX 9060 build, but a family member's ex walked out on them and the PC the family bought for said ex (which has a 9800X3D / RTX 5080 w/ 5yr warranty) was offered to me as a freebie.

Previously '83 would launch without issues on the 9060 (AMD) so I have to assume is this is an issue with Nvidia specifically. Does anyone know any way around this or am I just waiting for future driver releases to hopefully iron this out?

What the actual christ happened to that subreddit?

I make a post about how abstract it can be when collecting prescriptions from the pharmacy. Unfortunately, two of the key words I needed to use (one being GP, the other hospital) are blocked by their automod. So I subsituted GP with 'jeepy' and hospital with 'medical office'

This, in turn copped me a permanen back without warning. The exchange with them in PMs:

>Me: A permanent ban is a disproportionate response because I used a different phrase so your overly sensitive automod wouldn't assume I was on an embargoed topic

>Them: Thanks for admitting to subverting automod again.

>Me: I would also suggest you need to relax your automod because it takes even basic phrasesike doctor or hospital and blocks them even if they are mentioned tangentially

>Them: If you could write a bot code that could understand context then you’d be a very rich person. Our keywords are fine, we can deal with a few false positives to ensure we capture 95% of the crap. You could’ve done what nearly everybody else does and contact us to manually approve your post if it did get caught by the word filter. Instead you decided to break our rules. The ban stays.

Which makes no sense because PMing them isnt guaranteed to get a response. It took a week last time to get a ban for "metaposting" lifted because one of their mods was too lazy to read the post.

What is the point of having a subreddit if you cant post on it because it might be deemed subjectively facebook-y or something like that?

At least here I don't need to tolerate that waffle.

To be clear I dont blame the staff most of the time as they are probably overworked and have been perpetually complaining about the building's broadband service being down for the last 12 months, but it is insane how much intuition and guess work you need to pick things up and not miss out on important things, second guessing every step.

I collect for my partner and her folks as they're usually not able to. One of them is diabetic and has a ton of medication that includes testing trips, insulin pens, pen needles etc as well as the insulin itself, and other medication. Not getting this right will put them in a critical condition if things go wrong.

So its great when they send you testing strips that dont work with the machines you're assigned, and only work with machines you get in a jeepy or medicl office. Or, my favourite, the prescriptions are in the system but they've all been split out individually (even if they were technically submitted by the same Jeepy at the same time) so the pharmacist, if they don't think to check, might only dispense some rather than all of what they're supposed to.

If the usual pharmacist + his staff are in its great, but sometimes he has a locum substituting for him who seems to need directing a little more. Like a few weeks ago, they only put half of the required insulin doses in and seemed confused when I phoned them until I spilled it out. Or today, I got collected a massive bag for the prescription which was supposed to have everything, then I asked "so this has everything? [nod] insulin? [nod] pens? [ribbit]"

Then all of a sudden the assistant shouted from the back to me "yeah we've got it" reminded the locum and he was like "yeah we've got it but can you wait a few?" which is fine, lucky I asked as the pharmacy was shutting less than an hour later and won't be open again until Tuesday.

Used to be if a man left white goods and appliances out front they'd usually be gone by the morning with nary a trace save for a vague imprint in the grass.

These days, you'll be lucky if there isn't a mess of metal scrap, broken glass and whatever scattered outside while they strip out the bits they do want. And sometimes if you're unlucky it will end up in your neighbour's thick grass, and nearly kill them in the spring when their lawnmower goes over a bit of stripped compressor

I've been daily driving bazzite for just under a year, even stuck with it after I was gifted an Nvidia based system (with an RTX 5080) - I remote connect / start / shutdown my PC 99% of the time so having a stable release of Sunshine is what matters most for me.

Essentially, either through power cycling a smart plug or using WoL I power on my streaming host which sits in an outbuilding (wired to the house via gigabit ethernet) and then connect over Moonlight to it on either my Steam Deck, phone or laptop. This is >99% of my use case as the only time I'm really sat in front of the PC is when I'm working.

Now, the new Bazzite 44 release appears to have broken Sunshine functionality as there isn't a stable release of Sunshine on Fedora 43, let alone 44, and the only way to get it working (trying to use it normally just throws up a -1 error) is to either:

1. Rollback to B43 (which is what I chose to do in the end)
2. Enable the Sunshine beta release in Bazzite, and then configure the capture method as XDG Portal (which has its own problems, as Sunshine will not automatically run as a service on machine boot, and needs a manual "approval" of screen capture)

In the short term I can live with being stuck on B43 however this puts me in the position of not being able to get later Nvidia driver releases, etc etc.

I already use Cachy with an nvidia laptop (specifically, a Thinkpad P14s Gen2 that has an 11th gen i7 and T500 "workstation" GPU somewhere similar to an underspecced 1650) so it's not completely alien to me, but the only thing I've really done with that is Stellaris early game, otherwise I remote stream everything to that device.

TL;DR - how is Sunshine on Cachy / Arch compare to Bazzite? Is it generally stable for Nvidia users? Am I losing out on any stability / reliability if I move from Bazzite to Cachy, or do my odds improve?

If anyone has any insight I'd appreciate it.