I think throughout all leagues it has been a consensus that the join stutter is back stronger than ever, and in general stutters have become worse since the introduction of the beta UI. Despite a player using it or not, it seems like everything has gotten worse. Unfortunately I have lost my realtime loggings of latest practice sessions due to the other bugs reported below, as I had to try and join multiple times in a limited time frame, so will only provide trace files. So if you are having a similar issue, please add your loggings below. Let's see if s397 can make something out of it. I have included both the invisible cars log and visible cars as I had stutters in both situations.
The relevant ones got overwritten after the join attempts, but I have one from the end of official FP session. I don't remember many join attemps though. https://drive.google.com/open?id=1BIBvyFY6TRTK7EsJ7iU3jtZms6JpVptt
Just confirming 2 league events this year and the join stutter has been very bad, so much so that admins are now stopping people joining during Qualy. Sorry not sure where the performance log is located.
We've created a document that explains in more detail how to turn on and send us logging information: https://docs.studio-397.com/users-guide/diagnosing-issues-using-logging For the record, we are addressing the join lag. It should be fixed on the next update.
Sorry for the thread hijack. @Marcel Offermans In the new document you say to set trace=2. In the sticky thread https://forum.studio-397.com/index.php?threads/how-to-create-a-trace-file.62304/ Coutie says to set trace=3 What is the difference and which should we use?
Both are fine. The number behind "trace" is the log level. The higher that number, the more verbose the logging will be. The highest available level in public builds is 2, so anything beyond 2 is just going to be interpreted as 2.
