I already reported this problem on Discord in a slightly different context, but the issue still persists. We held our first event since the big update (WTCR at Silverstone GP) and the aforementioned "abrupt ending" bug appeared again at the end of race 3. Our race format was: Practice, Qualy (Superpole), Race 1 *reload* Practice, Qualy (10 min), Race 2, Race 3 (reverse grid) Here is a picture from the dedi with the used settings: Notice both 'Checkered after time' and 'Race finish duration' are set to 120 seconds. And yet the game didn't let us finish the last lap. 10 seconds after the race time finished, it started a "Race Finish In 30 seconds" sequence and ended the fun too early. A possible cause could be when someone waits almost until the end of the race start countdown to join the track. Because we only experienced the problem when someone did that.
Hello, Can you attach the files: - Game.log - MWTransport.log You can find the files at dedicated server machine on this location: \Documents\My Games\SimBin\RaceRoom Dedicated\UserData\Log_Dedicated Thanks
We don't have it anymore unfortunately, our prequal server runs 24/7. But if you can't reproduce it, we'll try to save it the next time it occurs (hopefully not).
I'm having the same problem after I chose my everything I want to race in and with what car the game starts to load and then it crashes. the message reads (game crashed (exception code OxC0000005)), the RRRE_Crash_2019_12_19_22_54_32_847.dmp is the file, and it looks like this MDMP[]&*~[] ##@###. Will Sector3 do anything about this problem?
The crash dump is a binary file. No use to open it in a text editor. You can upload it here, the devs can read it.
What is exactly meant by Checkered After Time: ? Race Finish Duration: ? I didn't find any useful information about those two settings. Example: Race-Time is 10 minutes (600 seconds). If I define "Checkered After Time" as 30s and Race Finish Duration for 60s - what is the result? Is the checkered flag shown after 610s and would there be time to complete the last lap until 670s? Background of my question: I am making some calculations on the race statistics exported from the dedicates server and the "totalTime" of the drivers in the races is useless as long drivers can't finish their laps. I tweaked those two settings and the races end prematurely as it seems. The driver will not complete their laps.
AFAIK Checkered After Time: the time between the race time clock hits zero and the checkered flag shown (in seconds) Race Finish Duration: the time between the checkered flag shown and the race actually finishes (also in seconds) So in your example: After 600 seconds the clock hits zero After 630 seconds the checkered flag is shown (even if the leaders haven't crossed the finish line yet) After 690 seconds, if the end of the field haven't finished yet, the AI takes control of the cars and the results are being shown
One clarification about "Checkered after time" : That setting will force the race to finish even if there's no winner known. So if you have a server with just one guy doing donuts and never crossing the finish line, it will make sure the race actually concludes. Once the session timer reached 0, that "Checkered after time" will start ticking, and if no winner is known by the end of that timer, then the race results are frozen like that. In most cases you want that OFF or set to quite a large number just to make sure your public server doesn't get trolled by such a donut guy. For a league race, you definitely should have it off.
Thanks for the info @J-F Chardon, but something must still be off, because both parameters were high enough to finish the race without problems.
You may have found a bug indeed. We'll try and find the repro steps with the testers. The guess I would make would be that it might not apply properly for race 2 and race 3.
Thank you very much for the clarification! It does definitely make sense, that way. Did you think about showing such an information in the configuration of the dedicated server (e.g. tool tips)?