Replies posted by ShrikeX
I am still experiencing the same reported issues, I hope in the not too distant future there is another client update and these issues are resolved as they are very bad now. Constant audio drop-outs when running with UDP (prefer speed) and major screen tearing/break up with TCP (prefer reliability). None of these occurred prior to the client change as stated. I’ve taken a look at the beta and downloaded it again today to confirm the beta is actually the identical same version as the current client, no idea why it is on the website and listed as a beta unless the versioning for the file hasn’t been updated and it is a new release, weird.
Issues appear to be getting worse, almost to a point where Shadow right now isn’t useable for some, not sure if this is network latency, issues with a specific datacenter, think I am connected via Paris.With UDP set for “Prefer Speed” there is major audio break-up, not too sure it’s actually related to the audio itself, it does appear to be a latency issue or something.With TCP set for “prefer reliability” there’s major video issues, complete screen break-up and redraw issues, this is as per the updated client v3.3320, was also apparent on v3.3317None of these issues were occurring prior to this Update notification announcing the changes. I don’t know what the build was prior to the update this week but with the current state it’s a mess and needs to be addressed.
Appears what was the beta yesterday has now gone live as the new update is for the client to v3.3320, checking the streaming settings and this has left the setting to TCP “prefer reliability”. Interesting :) BTW Jim, what exactly is “High Quality Audio” - how does it change? Compression, Bit rate? there’s no info on what it does.
Hi Jim,Thanks for the link, will look into that. I have tested the TCP connection - prefer reliability works better, well there’s no audio glitching, but there are some issues with screen redraw etc. I suspect the changes made to “optimize” the usage of audio on the CPU have also had back-end changes and they are being experienced by people. Changing back to prefer reliability over TCP is a solution but isn’t ideal if the preferred service delivery would be over UDP, those issues need reporting back to the devs and dealing with :)
Hi again Jim,I can confirm it is the streaming protocol change that is causing the issues.I installed the Beta it defaults to TCP - prefer reliability, seemed to work OK, changed the protocol to UDP - prefer speed and it exhibited exactly the same issue as the official client. I uninstalled the beta and reinstalled the official client, that defaults to UDP, prefer speed, changed to back to TCP - reliability and it works fine. So either the changes that were made to the audio pipeline to use less resources have affected the UDP performance of the new client is simply defaulting the UDP which it is and maybe previously would have defaulted to prefer reliability as the Beta client does.Hope that helps :)ShrikeX
Hi again Jim,Downloaded and installed the beta but not tested it yet, but I think I know what the problem is.The updated client has change the Streaming optimization back to UDP over TCP to prefer speed instead of reliabilty. The default on the beta client Launcher v4.16.6 Client v3.320 is TCP which makes sense as UDP can be very unpredictable. Might be worth you all checking if this is the case for others that have reported the issues too and change to back to TCP.
Hi Jim,Appreciate your update, I have just checked and I am not using the experimental settings for High End Audio, it’s just as default. I am using the default Windows device, I’ve not heard of this Steam Streaming Speakers, I assume that’s a chance of the audio device in Windows itself on the host as oppose to any settings with Shadow or am I wrong? Thanks for the link to the beta, will uninstall the official client and try the beta and let you know the reseults, as I said what is strange is there were no issues till the update this week which specifically mentions the change the audio demand on the CPU, it appears to have done the opposite but I will test the beta version now and report back.
Login to the community
Social LoginLogin with OpenIdConnect
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.