Just throwing it out there for data: I have this issue recently as well. Ryzen 9 7950X/RTX3090. Canvases usually don’t load at all but sometimes a small amount will load. Clearing canvas cache, verifying files, or reinstalling has no effect for me. Its very similar behavior as the pre-engine upgrade issue for certain generation Intel CPUs people experienced.
From our investigations, it seems to occur when there are many broken URL links. The broken links seem to halt the CPU from loading the next set of images, then gets stuck infinitely loading which will break until the game is rebooted. We are looking into ways to resolve this.
My AMD brothers and sisters,
It looks like a BIOS update fixed my Canvas and Game Hanging issues with the AMD Ryzen 7 7800X3D, specifically a BIOS update with the updated AMD AGESA 1.1.7.0 Patch A. The update was released for my motherboard on Apr 22, 2024 and I updated today.
I make no promises this fix will work for everyone, but it did for me.
If you do plan update your BIOS please do so at your own risk and good luck.
OK
So, In my typical fashion I found how it can still break after my BIOS update.
So I can pull an image link from most anywhere, using google images as my test bench, and canvas loads. Great! Wasn’t doing that before.
BUT, if I try and pull images a newly uploaded image link from either of my Dropbox accounts we go back to the spinning icon. Once that happens can’t see player condos or plazas and when I quit TU stays running in task manager and I have to end task.
More data for the bug report.
Quick update.
Adding Canvases (not using Dropbox) is still working within my Condo 99%.
I moved and verified all my images to new image host to insure no broken URLs.
But once in a while I will have a new canvas come up as spinning icon and will need to save, quit, end task and reload my condo and image will load and things are fine.
Other player condos still present with non loading / spinning icon canvases. Once my session experiences a spinning icon canvas TU will produce the following issues:
-
Plaza Menu / Player Condo Menu Hangs (Spinning UPDATING)
-
Quitting TU shows GUI closes, but Steam will report TU as still open and you must end task to stop it. The stuck TU task is using approx. 2.6GB of RAM.
-
Reloading TU and re-entering the Player Condo with spinning icon canvases does not fix any of said canvases.
“Data! data! data! I can’t make bricks without clay.”
Thank you for all the additional information. We are still trying to pinpoint the issue.
Just bumping, having same issue for months now.
AMD Ryzen 9 7900X
Cannot load any canvases in other players’ condos
Cannot load any workshop models in other players’ condos
Quitting game closes application but leaves an open background process making steam report it as still running clicking stop on steam will close it though
Condo menu 9/10 times does not load any condos
Clearing canvas cache and verifying game files in steam doesn’t seem to do anything for me
canvases work fine for me.
same here
same issue here too
CPU is AMD 7800X3D
okay so i found a way to get them to load… you need to go to there condo (nothing loading) then quit out of the game. then reopen it and a few will load
I too have this issue since 0.17.9.0 based on screenshots. Images will either randomly load but not all canvases. Most of the time the canvases will just spin in a circle. Also like someone else said the player condos list doesn’t want to load either.
I’ve tried clearing cache, Deleting the Cache folder, Reinstalling, verifying. Changing proton versions. Tested in a Windows VM that also had the same problem.
Using Xeon Silver 4114’s
I know it wasn’t listed as a fix, but this issue still happens in [0.17.12.0]. I do notice that some canvases now actually say “Canvas failed to load” instead of just displaying the spinning icon however. Many still just spin though.
Same here
So I did previously know this but
Its definitely platform specific and not a Linux issue
My other Tower with a E5 v3 (Haswell 4th Gen) doesn’t have any issues loading canvases under windows
I put the same SSD with windows on it into my Xeon Scalable (Skylake 6th Gen) and still have the issue with canvases. I am testing with AMD RX 580 and Vega FE.
So hopefully a fix for AMD also solves the Intel issues as well
Any updates on this issue? I know a lot of people are logging in each update to see if the issue was patched.
We did changes in the Eruption update that we hope will help with these issues.
Ok so the pictures are loading in condos however, for the ones that don’t load I’m getting a canvas failed to load now instead of spinning like before. Just as before when loading the game the first time, Plaza/Condo/Gameworlds browser works but I guess after joining 1 or a few condos they stop working.
During testing I have observed a condo with little images work but upon joining another condo and coming back the images that worked resort to failed to load. This has happened twice so far.
None of the images in my condos worked they all just said failed to load but not spinning this time. However they all have known broken canvas links.
The cache for images is no longer showing under the cache directory for the Tower install. The clear image cache in game shows 0 Bytes.
Attached is a players condo where most loaded and some failed to load
I really appreciate the effort getting to the bottom of this
I’m still having this issue as of 07/23/24 following the Eruption update. I can no longer access or use any of my condos without completely breaking the game.
EDIT
The AMD fix in this thread resolved my issue.
While looking into the “AMD” fix to see how to apply it to a Linux system. Simply installing the package “openssl” from your package manager solves the issue. All the canvases that aren’t linked to discord work now in my condo. Respectively for windows setting the environment variable should fix it too.
Edit: Good amount of canvases in others condos are failing to load still…Now coming full circle back to my condo none of canvases are loading.
Hopefully it has something to do with the cache
I can confirm that this old fix (adding that environment variable) works for me as well. Odd that I never had a problem before 0.17.9.0. AMD Ryzen 9 7950x, for reference.