over 1 year ago - CO_Avanya - Direct link
If you use mods please check your mods against the list of broken mods, both the first tab and especially the tab named Patch 1.17.0. The list is constantly updated as mod issues are discovered, so I recommend checking regularly if you use mods.
https://pdxint.at/BrokenModCS

If you don't use mods, then please make a report on our support forum so we can look into this. We need to see your output_log.txt (called player.log on Mac and Linux) and your save, which cannot be attached here on Steam.
https://forum.paradoxplaza.com/forum/forums/support-bug-reports.879/

Depending on your operating system the log can be found here:
Windows
\SteamApps\common\Cities_Skylines\Cities_Data\output_log.txt
\CitiesSkylines\Cities_Data\output_log.txt

Mac OS X
~/Library/Logs/Unity/Player.log

Linux
~/.config/unity3d/Colossal Order/Cities: Skylines/Player.log
over 1 year ago - CO_Avanya - Direct link
Originally posted by bora.48M: I think you dont read my problem. I dont receive any error output and this is not about mods. New truck type causes this problem. Some of the vehicle's going into the Cargo Airport Hub and they are "magically" stops then makes a traffic jam.
Your post did not state whether you were using mods or not, so I decided to provide information for how to proceed both with and without mods. Bug reports need to go on the support forum as Steam unfortunately does not provide all the options we need to investigate issues. And the output_log.txt is useful to us even when you do not see any errors. Some errors do not pop up in game, but even when there are no errors, the log contains a lot of information about what's happening in the game. Which is why it's always good to include when reporting a bug. :)
over 1 year ago - CO_Avanya - Direct link
Originally posted by Loli1: I have the same problem as above. Disabled all mods.. still my trucks keep getting stuck at cargo train stations.. they go in and come out.. but they don't dissapear when they are in the cargo station. Nothing seems to work to fix it.. so I believe its a problem with the last update..
We're currently investigating this issue