Without timestamps on logs it is hard to know the order in which things happened. In either case it is probably reasonable to expect that the RACE_OVER_TIME has got something to do with this problem. It is also possible (I can't confirm right now) that all drivers left before the race over time expired. This time was the first time I had this set to high when running using speedwise. We do this to make sure there is enough time for people to finish and to ensure we can get the race_out.json. One other thing that occurred to me that maybe relevant. I have double checked the permissions on all files in the workspace and the speedwise-node could access them. The speedwise-node has been running for about 6 days now and there are other sessions which have been recorded ok. Is this still done manually?Ĭlick to expand.I think that is unlikely. How are you currently uploading your server config? I tested the manager and the "cfg"-folder was always empty.
With a standard FTP-client (like or ) you are then also able to upload the "presets"-folder via drag-and. I just checked out the AssettoCorsaServerManager's FTP-functionalities to upload the contents but unfortunately the ServerManager does not upload the "presets"-folder.Īnyways - I will add a new tool to the next speedwise-node to easily start a FTP-Server to upload the base AC-Server via the servermanger so people can use the "Upload Content"-button to at least update the server's executable and contents:
For multiple servers you just have to make sure to not have some colliding TCP/UDP ports configured:
Every preset is then recognized by speedwise and startable from there. Click to expand.You can use the AssettoCorsaServerManager-Tool to create multiple presets and upload them to your server (the whole presets folder).
0 kommentar(er)
