Issues related to individual compatibility tools and not ProtonUp-Qt - Links to issues pages

[kingjoma]

Hi all

I am using GE-Proton 8-30 from ProtonUp-Qt on SteamDeck SteamOS 3.5.

When running Microsoft Freelancer the .wmv movies at launch work with no sound.

If I play that same movies from the source folder using VLC player from Flathub the videos play with sound.

I suspect there is an issue with audio in the codec embedded in this version of GE-proton.

Kindly advise.

Thanks.

[DavidoTek]

See https://github.com/DavidoTek/ProtonUp-Qt/wiki/Issues-with-individual-compatibility-tools

---

Issues not related to ProtonUp-Qt, but individual compatibility tools

The issue is related to the compatibility tool you are using, in your case GE-Proton.
ProtonUp-Qt is only an application for installing and managing the individual compatibility tools, but not responsible for running the games or apps.
Please take a look at the issues page of the individual compatibility tools. First search whether there has been a similar issue. If not, you can report the issue over there.

---

Links to the issue pages of the individual compatibility tools

Please do a quick Google search beforehand, as there are often similar issues reported, either on the issues pages or on pages like Reddit.

Compatibility Tool	Link
Valve's Official Proton	https://github.com/ValveSoftware/Proton/issues
GE-Proton and Wine-GE	https://discord.gg/6y3BdzC
Luxtorpeda	https://github.com/dreamer/luxtorpeda/issues
SteamTinkerLaunch	https://github.com/sonic2kk/steamtinkerlaunch/issues

PS: Game-specific issues and fixes can often also be found on ProtonDB: https://www.protondb.com/

[sonic2kk]

Great writeup! I think it's also worth adding links for:

• Proton-tkg / Wine-tkg: https://github.com/Frogging-Family/wine-tkg-git
• Kron4ek Wine: https://github.com/Kron4ek/Wine-Builds
  • Since these are largely just either Valve Proton or Vanilla Wine builds, it might be worth pointing to the upstream Wine issue tracker: https://bugs.winehq.org -- Wine could also have a separate entry on the list

Possibly also relevant to add links to the upstream launcher issue trackers (maybe in a separate table):

• Steam for Linux: https://github.com/ValveSoftware/steam-for-linux/issues
  • Not all Steam bugs are exclusive to Linux so there can be significant overlap.
• Lutris: https://github.com/lutris/lutris/issues
• Heroic: https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/issues
  • Much like Steam, Heroic is cross-platform and so bugs may not be exclusive to Linux
• Bottles (don't have the link, sorry)

Finally also links for runtimes in a separate table could be relevant (I may be wrong but I get the feeling these are less popular than the compatiibility tools):

• DXVK (including DXVK Nightly): https://github.com/doitsujin/dxvk/issues
• vkd3d-proton: https://github.com/HansKristian-Work/vkd3d-proton/issues/
  • Lutris' vkd3d has no issue tracker, bugs can probably be reported to upstream Lutris or perhaps more relevantly in most cases, vkd3d-proton
• DXVK Async: https://gitlab.com/Ph42oN/dxvk-gplasync/-/issues

I also have some ideas for how we could further document this topic:

• On the "About" dialog, we could add a note somewhere around the copyright section that "Compatibility tools are maintained independently and copyright to their respective authors, issues with individual compatibility tool should be reported upstream" (worded a bit better than that ideally 😅). I don't think most people will read it but it would be good to give acknowledgement somewhere else that they are separate.
• On the Readme, we could note this as well around the license section, but further up we could link to this issue. Somewhere after the screenshot on the first section on the Readme, with the same or very similar note as to what we add above.
  • Likewise the Flatpak description should be updated.
• A wiki page would be nice to add that would essentially hold the contents of your comment above. ProtonUp-Qt has no wiki right now and maintaining one can be a hassle, so no rush or pressure.
• Users can access the release notes on the repo for specific compatibility tools by pressing the "Info" button on the "Install" dialog, I don't think we need any extra action here.

Of course these all hinge on hoping people will read the information, these are just ideas for potential further communication.

[DavidoTek]

Thanks! I will add the links to the table.

On the "About" dialog, we could add a note somewhere around the copyright section that "Compatibility tools are maintained independently and copyright to their respective authors, issues with individual compatibility tool should be reported upstream"
Users can access the release notes on the repo for specific compatibility tools by pressing the "Info" button on the "Install" dialog, I don't think we need any extra action here.

We can do that. There's already the Info button in the install dialog, but I feel like that is not used that often.

On the Readme, we could note this as well around the license section, but further up we could link to this issue. Somewhere after the screenshot on the first section on the Readme, with the same or very similar note as to what we add above.
Likewise the Flatpak description should be updated

Probably the best place would be either under the screenshots or under the install section if we were to add it.

A wiki page would be nice to add that would essentially hold the contents of your comment above. ProtonUp-Qt has no wiki right now and maintaining one can be a hassle, so no rush or pressure.

Yeah, I was also wondering whether it would make sense to create one to also document some "niche" features. Like the GitHub/GitLab API keys are also only documented inside a comment somewhere.

https://github.com/DavidoTek/ProtonUp-Qt/wiki/Issues-with-individual-compatibility-tools

Of course these all hinge on hoping people will read the information, these are just ideas for potential further communication.

I've pinned the issue, should be easy to find when someone creates a new issue.

I think of all the options you listed, the wiki option is probably the best. I will look into that.