Hello @RainehDaze, can you verify any vulkan application works like vulkaninfo from vulkan-tools?
Vulkaninfo works:
vinfo_out.txt
DXVK normally works (e.g. both Monster Hunter: World and Dark Souls III have no such graphical problems)
With Proton 4.11-1, the game no longer crashes when pressing "I've played before". It now seems to be loading the login screen for a second, before coming up with -302 in the corner, at least for me. Also, PROTON_USE_WINED3D seems to be no longer necessary.
The problem with the in-game web browser in Bloons TD 6 has been fixed with Proton 4.11-3. Please retest.
Works good for me now! Although, PROTON_USE_WINED3D was necessary to get the game running. This is on Proton 4.11-3. Also probably relevant is that I'm on Nvidia.
On Proton 4.11-12, the game runs flawlessly for me without any launch options, using a Radeon r5 240 with amdgpu on Fedora 31. If others have a similar experience, I think this game could be a candidate for whilelisting.
The game doesn't run for me at all.
OS: Arch Linux
KERNEL: 5.7.5-arch1-1
CPU: Intel Core i7-8700K @ 3.70GHz
GPU: NVIDIA GeForce RTX 2080 Ti
GPU DRIVER: NVIDIA 440.82
RAM: 16 GB
I tried using latest version of glorious eggroll as well as Proton 5.0-9. The game just launches to a grey screen and a monkey mouse pointer. I tried using launch option PROTON_USE_WINED3D=1 %command% but I get the same result. Also tried turning of steam overlays to no avail.
Launched steam from terminal and these are the errors I see:
UnauthorizedAccessException: Access to the path "Z:\CachedLanguagePref.txt" is denied.
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x00000] in <00000000000000000000000000000000>:0
(Filename: currently not available on il2cpp Line: -1)
Setting up 6 worker threads for Enlighten.
ERROR: Unable to load Firebase app options ([Z:/media/evo500/Steam/steamapps/common/BloonsTD6/BloonsTD6_Data/StreamingAssets\google-services-desktop.json, Z:/media/evo500/Steam/steamapps/common/BloonsTD6/BloonsTD6_Data/StreamingAssets\google-services.json] are missing or malformed)
I looked around in the BloonsTD6 folder, and couldn't find a google-services.json file, so looks like it's missing and was not included in the installation of the game. I'm not sure where I could get the json file specific to Bloons TD6.
Any suggestions?
@mmoore7 The game is working well for me on 5.0-9. My log does have the "Firebase app options" error, so I think that's normal. However it doesn't have the "CachedLanguagePref" error, so I think that may be the problem.
On my system, this file is located at C:/users/steamuser/AppData/LocalLow/Ninja Kiwi/BloonsTD6/CachedLanguagePref.txt within the prefix. I have no idea why yours is trying to look it up in the root of the Z drive (which points to your system root, hence the unauthorized access error).
Are you using a non-English system locale, or did you select a non-English language in the game? You could try deleting the game's compatdata folder to reset the prefix. On your system, this is probably located at /media/evo500/Steam/steamapps/compatdata/960090. However this may delete any saved game data you have, so consider making a backup if you have saved game data you'd like to restore.
@aeikum Thanks for that info. Deleting the game's compatdata folder worked! Thanks!
The keyboard doesn't work if I have my controller wireless module on
So my controller (ípega 9078) is wireless and comes with an USB wireless module for the controller, I leave the module plugged in and this is the only game so far that doesn't like that, also my controller is not connected to the module (aka my controller is turned off) just the fact that the module is plugged in makes my keyboard not work for that game
Btw Steam sees the module as a controller
I tried turning off the controller for that game using steam but it didn't work
Running steam on the terminal then launching the game gives me this error
Only once
<RI.Hid> Failed to read input report:
Dispositivo removido. (Device removed)
This one repeats every fast after the first error and only if the game is in focus
<RI.Hid> Failed to start reading input report:
Acesso negado. (Access denied)
My system is in pt_br and some errors are in pt_br so I put in parenthesis what it means in English
I tried to get a log using proton_log, but it didn't give me a log. I think is because the game doesn't crash
PROTON: 5.0-9
OS: Arch Linux x86_64
Kernel: 5.7.7-arch1-1
CPU: AMD Ryzen 5 1500X
GPU: AMD Radeon RX 580
RAM: 16GB
The most recent update to the game has stopped it working.
steam-960090.log
I can confirm, the game doesn't work anymore with update to version 20.0. It opens the game window and then closes right away.
steam-960090.log
steam-960090.log
Here's another log with a fresh pfx, it's complaining about dx11 not being installed.
Probably because of your launch parameters: Options: {'wined3d', 'nod3d10', 'noesync', 'forcelgadd'}
steam-960090.log
Here's one without the launch options, not sure where forcelgadd comes from as it's not added by me.
forcelgadd is set by default for all games.
I've tested the game. The game now explicitly checks for Wine by searching for 'wine' in hardware platform strings obtain from the api and exits if it finds some. I am attaching the patch which allows the game to run, with this patch on top of Proton or mainstream Wine game worked fine for me. But ultimately this sort of issue is unfixable.There will always be the ways for a program to detect that it is running under Wine. If the game is intentionally refusing to work under Wine it will likely break again
patch.zip
after the next update.
The game now explicitly checks for Wine by searching for 'wine' in hardware platform strings obtain from the api and exits if it finds some.
Wow, I better hold off any words I have in my head now.
Disappointing, wonder if it's the developers of the game or the developers of the game engine they're using that added that little nugget?
Disappointing, wonder if it's the developers of the game or the developers of the game engine they're using that added that little nugget?
I can’t guess that. From what I came through during the search for the crash reason it doesn’t look like it could be Mono or Unity. But that can be, e. g., some telemetry collection library linked with the program which does that for some reason, I can’t say really.
You clone this git repository as described in the README, then use git am patchname.patch in the proton/wine directory, and then follow the instructions in the README on how to compile Proton.
When I run that I get an error
Applying: HACK: Make Bloons TD6 happy so it does not exit after getting string Wine from bios info. error: dlls/wbemprox/builtin.c: does not exist in index Patch failed at 0001 HACK: Make Bloons TD6 happy so it does not exit after getting string Wine from bios info. hint: Use 'git am --show-current-patch=diff' to see the failed patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort".
Looks like you're not applying it in the wine directory.
So I messaged u/rohan_spibo on Reddit about this. His response:
"There is some issues that seem unfixable so far which cause every user on proton to be seen as if they are all on the same device, and a lot of our server things triggered by 1 user are then doing so for every account on Proton."
It seems that this was done out of necessity by NK to stop Proton-related server issues. I don't believe using the patch in this circumstance would be appropriate if playing is causing issues for the devs, unfortunately.
If there is an issue of Proton not providing some real information for the game telemetry I think that can likely be fixed on Proton side. If the developers could let us know which api / info is required to stop the mentioned server issues that could be very helpful.
@gofman I directed Rohan here to this thread. I'm looking forward to some jolly cooperation.
I contacted Ninja Kiwi support and this is the reply I got from Savannah:
Hi there,
Thanks for getting in touch.
Sadly, Linux caused quite a few issues for the game on our end which is why we chose to do this.
However, I will pass your feedback on to the team here.
Regards,
Savannah
Hopefully there's a way to get it running without the problems, I'm ready & willing to test it if that happens.
If enough people are using wine to play that it's causing server issues on their side, maybe it's in their interest to recognize that a linux build would be really beneficial to the community. At the very least, it would make sense for them to provide what exactly was breaking so the compatibility layer gets fixed. Seems silly to me to shut out a portion of your potential market.
@kiranshila Linux isn't often a large enough market that it's worth creating and maintaining a build for it. As much as I'd love to see official Linux support, the devs seem to be trying their best with just having it supported well through Proton, and that's all that I can really ask for. They'd like to see this fixed just as much as we do; this was probably a tough decision for them.
Not a large enough market but large enough that the number of people playing with proton breaks their backend? I dunno, that's a hard sell. Considering they have builds for iOS, Android (unix), Mac (unix), and windows, I do not think it would be difficult to build for Linux.
With considering that except that issue, the game worked flawlessy with Proton, so they could just do official Proton support with being whitelisted for Steam Play.
@myahenochs We're definitely happy to work with the devs on this. Please feel free to ask them to reach out to me and/or Paul so we can find out what they require and how we can provide it.
Hi, Danny from NinjaKiwi here. The issue is related to Unity and how it interacts with wine. This was causing issues for users that we are unable to resolve. We understand it is frustrating to have the game no longer work, but we would rather resolve the issue first than have more users affected.
To make steps to rectify the issue we have submitted an issue report on the wine repo here: https://github.com/ValveSoftware/wine/issues/97. If the version of wine used by proton can be updated, and this resolves the issue as is stated, then we should be able to allow Proton to function again.
@dannyNK any reason not to just build for Linux? Should be straightforward for a unity game. Especially now that Vulkan has matured.
Hello @kiranshila, whether Ninja Kiwi choose to provide a native Linux build is tangential to the purpose of this issue tracker. Since Proton is always an option to the end user, the technical issue still needs to be resolved and we appreciate the actionable feedback from the game devs on how Proton can be improved.
Please use another medium to express your interest in a native Linux build.
Fair enough
So can we expect these fixes to be in the next release of Proton or do we need to wait for Proton to catch up to Wine 5.10?
They probably will include it in the next release, citing from the wine issue:
If what you need is those patches from Wine 5.10, then we will have some good news for you soon.
With the newest Proton-5.9-GE-6-ST it works again.
I can confirm that with Proton-5.9-GE-6-ST Bloons works again.
Note that as mentioned earlier in this thread, people at NinjaKiwi will very much not like the fact that you're playing BTD6 with the patch enabled in GE, unless GE also applied the patches that are required from wine 5.10, but I don't think they did.
people at NinjaKiwi will very much not like the fact that you're playing BTD6 with the patch enabled in GE
Not true. It's not that they dislike it, they just want it implemented properly:
https://github.com/ValveSoftware/wine/issues/97
dannyNK commented 23 days ago •
As per this issue here: https://bugs.winehq.org/show_bug.cgi?id=49160
In Unity games the SystemInfo.deviceUniqueIdentifier is consistent across all wine users. This causes issues when trying to individually determine users.
Wine 5.10 appears to have an update to address this issue.
kisak-valve commented 23 days ago
More specifically, https://source.winehq.org/git/wine.git/commit/84857d27067afaa1ae5774afe27086332263bfb5 and possibly https://source.winehq.org/git/wine.git/commit/f516a23041b3871625764611321250f977fe750a are the commits involved.
My build has: 84857d27067afaa1ae5774afe27086332263bfb5:
But is missing f516a23041b3871625764611321250f977fe750a. I will get this implemented tonight.
Hi everyone! I have an issue that I haven't seemed to find documentation of. The background "layer" of the game (title menu, main menu, tracks, etc) have visual glitches:



This is the case with Proton versions 5.13-4, 5.9-GE-8-ST, and Proton Experimental. I also have no launch options set.
The game was working with the GE Proton version until I updated BTD6 to the newest version a few days ago. I haven't played in a while, so I don't know when exactly this became an issue.
Here's my system info as requested by @kisak-valve. Please let me know if there are any issues with it, as I've never provided one of these before.
Hello @myahenochs, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
Thanks, @kisak-valve, I've updated my comment with it.
I'm unable to reproduce that visual corruption on my current setup. Here is my system info.
@myahenochs I can't reproduce the problem with Mesa 20.2.2 and Navi10 (same config as you it seems). Are you sure you are using RADV and not AMDVLK? You might want to confirm with 'export DXVK_HUD=fps,devinfo,version'
@hakzsam the HUD yields:
DXVK v1.7.3-10-gc1f23643
AMD Radeon RX 5700 XT
Driver: 2.0.167
Vulkan: 1.2.159
And then since you specifically included fps, it's hovering around 144.
I'm very unfamiliar with video drivers and this tool, but from what I can tell, I'm using AMDVLK. I tried adding VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json to my launch options to force RADV, but the HUD still displayed Driver: 2.0.167 and I still had the graphical issue. If this was the wrong conclusion or course of action, well... I tried :sweat_smile:
I appreciate your help, by the way, despite this not seeming to be a Proton issue.
Hello @myahenochs Driver: 2.0.167 sounds like an AMDVLK version to me.
VK_ICD_FILENAMES not working with Proton 5.13 is a known Pressure Vessel issue noted in #4289. You might be able to workaround that issue by completely closing Steam, then starting Steam with PRESSURE_VESSEL_RELAUNCH_CONTAINER=1 steam in a terminal and VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command% in the game's launch options. Alternatively, you could try something like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json" steam. (https://github.com/ValveSoftware/steam-runtime/issues/304#issuecomment-745452087)
Thanks @kisak-valve, but that didn't seem to work. It isn't much of a deal to me if that's a known issue, I'm fine waiting for a fix. I'm glad to know what the problem is.
Okay, thanks for trying, another option is to temporarily disable AMDVLK with something like sudo mv /usr/share/vulkan/icd.d/amd_icd64.json /usr/share/vulkan/icd.d/amd_icd64.json.disabled.
Hi, I wanted to share my output, as I just purchased Bloons TD 6, and I am trying to run it with Proton experimental and nothing happens. See attached info about my system, and the terminal output when I tried to run the game (twice) unsuccessfully.
Output
https://gist.github.com/MavropaliasG/363bb9fa4b6725c459aa98c6f2973754
My system
https://gist.github.com/MavropaliasG/0e680530e57495658aaf90d0f1677f92
Hello @MavropaliasG, you have encountered https://github.com/ValveSoftware/steam-runtime/issues/294.
@myahenochs Yeah, it looks like to me that you are using AMDVLK and not RADV. Try to uninstall AMDVLK?
Yeah, I'm aware this is a solution, but I use AMDVLK for other games that I actively play and it wouldn't be ideal if I install and uninstall to switch back and forth. Thank you though! I'd probably go with the disabling option if I needed RADV.
Whitelist Bloons TD 6
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5221.
@jannis3005 posted on 2021-10-13T18:26:16:
Play button in the Steam client is sufficient.Hello, @jannis3005, your whitelist request is missing what version you've tested the game with, please add a note with that.
Is anyone seeing an issue with this game that would block it from being whitelisted?
@kisak-valve 6.3-7
Connecting to your profile does not work because it attempts to ping DNS servers first. Proton doesn't seem to support ping. From customer support:
No problem at all, thank you for passing this on :) BTD 6 should be attempting to ping the IPs 1.1.1.1, 8.8.8.8 and 8.8.4.4 and it expects a response within 1.5 seconds from any one of those addresses. I hope this helps!
A sudo setcap -v cap_net_raw+epi on Proton's WINE binaries did not yield any results.
Connecting to your profile does not work because it attempts to ping DNS servers first.
I did manage to log into my account. I did this by restarting the game and when it started up I could click on the option "I have played before" in the top left. That showed a different page where I could log into steam and recover my account.
Replying to https://github.com/ValveSoftware/Proton/issues/2330#issuecomment-966631520
I am also connected using the same method. Unfortunately, the profile settings are no longer accessible once connected (but one remains connected).
Just recently started playing the game. Worked fine for a few days (except for having to set up a profile on the screen with the start button rather than in the profile menu itself), then I was just playing a game, finished a round, went to go back to the menu after reviewing the map, and I crashed out. I tried restarting the game, got to the menu with the 'Start' option and crashed after I clicked it (during the... loading monkey?). I tried to deleted the prefix, restarted again, same thing (still remembered my linked account, too), verified files and deleted prefix again, no change. Restarted Steam, Just In Case, no change, deleted both the game and the prefix installed to a different hard drive... same problem (and still remembered my linked account).
I pulled a log with PROTON_LOG=1 %command%, my system info per Steam here.
I'm not really sure what direction to jump with this one, given it was working fine right up until that first crash, and neither removing the prefix nor reinstalling seems to change the situation.
Possible line of interest from the log: ArgumentException: Requested value 'RADIOACTIVE' was not found.
That might be a red herring because the game has already declared in the log that the game has crashed and tried to upload a crash report before that line appears.
Update: The light of not-3 AM and some googling led to here, which wasn't exactly my problem but another thread that was recommended it as a solution. So adapting the userdata path for Linux, I removed ~/.local/share/Steam/userdata/<userid>/960090/ and that got me back into the game.
Recently came back to this game after a couple weeks break, previously worked fine. Now crashing on launch, the little unity popup with a loading bar appears and I always crash at the same spot. Tried various proton versions.
System info https://gist.github.com/ryannathans/9a326ee3cb9c05c1b09e9e99f39f1c36
Am I reading the log correctly in that it tries to get local time zone data and then in the process ends up dying on some Hid Device buffer flush?
Bloons TD6 touchscreen crashing
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5819.
@guyish1 posted on 2022-05-05T16:41:01:
everything works as expected, but when I use a touchscreen, the game instantly crashes. This was not a problem with this game before. I don't know when this problem started because I took a hiatus from the game for a couple of months, the last I remember playing on this device was mid-February 2022 and the touchscreen did not cause the game to crash. I played on this device again on 5/3/2022 and that is when it was an issue.
launching the game and touching the touchscreen
Same here the game crashes the moment you touch the screen.
It's a regression with Proton 7 because it works with proton 6.3.8.
Tracking note: Tentatively dropping the regression label in favor of #5744. If the touchscreen crash happens with an X-based user sesssion, then let me know.
Tracking note: Tentatively dropping the regression label in favor of #5744. If the touchscreen crash happens with an X-based user sesssion, then let me know.
I'll test this later today.
I'm having a problem signing into my account. I click on anything to sign in and it appears to be trying to sign in but then errors out saying I have no internet connection with an error code of "00".
Edit: I guess it was just a random glitch then? It's gone now.
Bloons TD 6 (960090)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5871.
@josesilveiraa posted on 2022-05-29T03:16:24:
The game runs very well, but there are glitches in the cursor, seems like a bad-cropped png image.
Launch the game and move the cursor.
Anyone got a fix for the steam cloud error?
The game is now working with touchscreen using Proton Experimental. However, if I use touchpad gestures the game crashes.
Right now it's crashing after a while of gameplay
steam-960090.log
Proton/Steam fullscreen placement issues
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9330.
@kingpurest posted on 2025-12-23T19:25:43:
System 76 pang15 (2025)
AMD Ryzen 9 8945 HS
Radeon 780m graphics
32GB RAM
Kernel driver in use: amdgpu
Pop-OS 24.04 lts
DE: Cosmic
Wayland
Proton 9.0-4 (also experimented with proton 8.0, experimental, and hotfix)
Primarily tested on Runescape 3 and Bloons Tower Defense 6
Some steps to reproduce for BTD6:
Launch Pop_OS 24.04 with COSMIC DE on Wayland
Launch steam
Launch BTD6 with proton 9 as a requirement in compatibility settings on steam (this version gave the best performance)
Game launches off center. Down and to the right specifically.
Alt tab to the game (even if it's already the active application) and this somehow recenters and fixes it. Everything now works as expected.
Runescape 3 is fairing much worse. Performance is bordering unplayable. Proton 9 yielded the best results but still significantly worse than that of bolt launcher flatpak.
Same reproduction steps to the T except the big difference is alt tabbing does not recenter.
The game remains unplayable in fullscreen mode as it is totally offset (and partially off screen due to this) Even when simply maximizing the game to be "closer" to fullscreen experience the games performance is just not great but with windows on the machine it is excellent. My main issue is not performance at the moment, but rather the screen placement and full screen functionality. That said, figuring out the awful performance would be lovely. Again I will cite that bolt launcher performance meets standards and to be honest I can't really say anything bad about it as it relates to linux and wayland or it's internal usage of wine.
Final notes about testing.
Proton experimental broke BTD6 entirely. Boot = intense flickering until alt+f4. Not playable.
Proton experimental actually fixed RS3's fullscreen placement but performance tanked even further. 10 - 15 fps min settings.
Going to continue testing random games. As a new user to linux it is pretty difficult to determine where these issues are originating (drivers, machine, proton, wayland, the games handling of fullscreen and other functions itself) so all I can do is list the issues as they appear to me.
Unity version was updated within the last few months, so that could be the cause of some issues, other Unity games would be showing the same issues though.
proton experimentalx4 2025-12proton 8.0x1 2025-12proton 9.0-4x1 2025-12proton 6.3x1 2022-05proton 5.13x1 2020-12proton 5.9-ge-6x2 2020-09proton 5.0x1 2020-09proton 5.0-9x1 2020-06proton 4.11-12x1 2020-01proton 4.11-3x2 2019-08proton 4.11-1x1 2019-08PROTON_LOG=1x1 2022-02DXVK_HUD=fps,devinfo,version'x1 2020-12PROTON_USE_WINED3D=1x1 2020-06PROTON_USE_WINED3Dx3 2019-08VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%x1 2020-12PROTON_USE_WINED3D=1 %command%x1 2020-06
Compatibility Report
System Information
I confirm:
steam-960090.log
Symptoms
Freezes (and will eventually crash if left alone) when pressing "I've played before" to log in--seems to pop up another window briefly. This means no saving progress across systems or syncing etc. Otherwise works with Wine D3D not DXVK.
Reproduction
Start the game with PROTON_USE_WINED3D as a launch argument (otherwise, at best, it will be a tiny box in the corner). Wait for it to arrive at the title screen. Click "I've played before."