protonscr

Bloons TD Battles

protonopen appid 444640Whitelist Request
ValveSoftware/Proton#4733 · opened 2021-04-03 by Newbytee · updated 2021-04-03 · 4 comments · github · game page · search this game
NNewbytee 2021-04-03 github

Whitelist Request

  • Name of the game to be whitelisted: Bloons TD Battles
  • Steam AppID of the game: 444640

System Information

  • GPU: GTX 970
  • Driver/LLVM version: nvidia 460.67
  • Distro version: Fedora 32
  • Link to full system information report as Gist:
  • Proton version: Proton 6.3-1

I confirm:

  • [X] that pressing the Play button in the Steam client is sufficient.
  • [ ] that runtime config options are necessary to run the game.
  • [ ] that no workarounds other than PROTON_* env variables are necessary.

Issues

  • [X] I haven't experienced any issues.
  • [ ] There are no issues left open for this game.
  • [ ] Although I consider the gaming experience equal to Windows there are remaining issues:

Worth noting is that an issue claiming this works well already exists dating over 2 years ago, https://github.com/ValveSoftware/Proton/issues/1855, however it was closed instead of being turned into a whitelist request.

Kkisak-valve maintainer 2021-04-03 github

Hello @Newbytee, by its nature, Proton Experimental is not eligible to use with the whitelist. Please retest the game with a different mainline release series and let me know the outcome, then we can re-open this whitelist request.

NNewbytee 2021-04-03 github

@kisak-valve I can confirm this works just as well with Proton 6.3-1, however I cannot re-open this myself.

Llegendofmiracles 2021-04-03 github

I wouldn't put this on the whitelist. Rumors have it, that the game devs once pushed a patch to break proton compatibility, because proton players were causing server issues.
The next proton version (and third party forks) worked again...

I don't think that they confirmed this officially but I read it on protondb.

Kkisak-valve maintainer 2021-04-03 github

Hello @legendofmiracles, https://github.com/ValveSoftware/Proton/issues/2330#issuecomment-688851311 was a legitimate shortcoming of wine at the time and was causing trouble for their server infrastructure. That issue has been triaged with Proton 5.13 and I would not consider that relevant to this whitelist request.

Proton versions

Upstream links