A compilation of gripes, bugs and general feedback from me and heroes. Includes obvious stuff for the sake of completion.

• The guest can't see the host's cursor movements, which makes it difficult to follow what the host or other guests are doing. The current workaround is to enable cursor trails, which has its own set of negatives, such as a stuttery cursor, duplicate cursor on the guest side (especially weird when the guest is moving), and bugs in specific situations.
• The restart required warning for settings is barely noticeable
• UWP apps are broken in Approved apps and Arcade, with no workaround
• Can't change install location
• There's no restart warning for Exclusive Input, Virtual Displays and Privacy Mode, which all require a stream restart
• Windows key is passed onto host with immersive mode off, so both the client and host's start menu will pop up
• In desktop sharing, the host has no means of seeing the guest conversations from the chat they get in their overlay, meaning talking to the host is only possible via other programs
• The host display selection in the overlay is remembered by Parsec, but you may need to switch back and forth so it actually uses the one you want, even if the one you want seems toggled on the overlay
• Pressing Ctrl+Shift+M will unhide the button, even if overlay is set to off in the Parsec settings. This negates the point of simply memorizing Ctrl+Shift+M to avoid having the button be constantly visible

things that hurt the new user's experience

• Parsec isn't upfront when and why a PC doesn't support hosting. When the hardware isn't up to spec, the users are given a seemingly generic 15000 error, instead of being directly told their hardware isn't supported. When it's the OS, Parsec won't tell that the OS isn't supported, but will simply not show anything host-related. A lot of users come to #support just to be told this
• Error 6024, when someone has it, can be a considerable barrier to entry. Parsec needs to make this easier to troubleshoot and solve. Like the errors above, instead of simply spitting out an error, Parsec can be more direct about it and even help by figuring out things like whether which user is on double/symmetric NAT, or if UPnP is working properly
• Figuring out why the Parsec stream is slow, laggy or with latency is not easy. To troubleshoot this you're supposed to check for the console log, the latencies in the overlay, the upload speed on the host and client, try to reduce the resolution, FPS, check if either side's internet is unstable, etc. This is way too much stuff for users to check and there's a lot of room for making this easier. In addition to that, users don't even know what they're supposed to do in the first place and will only find out how to troubleshoot issues with the help of heroes
• Trying to find out why controllers aren't working can be a pain. Some sort of clear feedback that the controller is working as expected on the host would go a long way. A portion of our time in the Discord is spent figuring out if the issue is Parsec or the program the host is using. With Arcade, it's more difficult to get people to use html5gamepad.com for troubleshooting
• Note that all those issues can combine for a worse experience. Imagine finally figuring out and solving your laptop's 14003 issue, to then get error 15000 and eventually come to learn that your CPU isn't supported. You happen to have another computer, so you use that, and have to deal with error 6024. After solving that, you see that the stream is slow and have to troubleshoot that. These things can stack up fast, and users can easily give up on Parsec with each single issue. Make it as easy as possible for them to stay, and don't wait for the user to try joining or hosting to point out issues
• Approved apps' description is not at all clear about the fact the whole screen is shown when an approved app is the active window

to end..

the maybe fixed boys?