I have following problem: Every time when i start Raceroom, this error comes "Content server error 20004". Does anyone know how to fix it?
Have a look at this thread. https://forum.sector3studios.com/index.php?threads/help.10395/#post-145324
CPU - Intel i3 3310M, 2,40 Ghz, 4 gb RAM, GPU- Intel HD Graphics 4000. And yes the game has worked in the past
@dac964 Hi ! Please provide Machine specs plus current OS an version also steam account name or email address associated, thankyou
It appears that you are running an older version of the game. Can you please make sure of the following: - Automatic updates for the game are allowed in Steam for RaceRoom - Verify Integrity of Game files (right click the game in the Steam library -> properties -> Local Files -> verify integrity) If verification did not solve it, try and delete the executable of the game and then run the verification again. To locate the game executable, right click the game in your steam library -> properties -> local files -> browse local files. Let us know if that helped! I would appreciate if you could share with me your steam username. Then we can look into this along with Valve and see how you ended up in that situation in the first place and fix it for good.
Also had this problem today. Never experienced it before. Did a files integrity check and Steam said two files had to be updated. Now it works fine for me. Noticed that the game has another version number than last time I played. Has a small update been released after the januari update?
I think not, but it seems like Steam might have had some issues fully distributing the last update(s), so people ended up using different game versions... :|
Update on this topic was posted here: https://steamcommunity.com/app/211500/discussions/1/1696040635902357155/ If you still suffer from delayed patch deliveries, please try these simple steps.
That what you have done is only a temporary fix. Unfortunately you will get the same problem again, when the next update will be published. What @J-F Chardon has described in that post should be hopefully a permantent fix.