Hi guys! I hope you're all well!
Apologies it has taken so long for me to post a summary following the last event - as you are probably aware, and now tired of hearing, I have been (and continue to be) incredibly busy with work. Therefore I have had very little time to keep up with my RaceDepartment duties.
Once again I'm going to keep this quite brief - since I did not take part in this event I do not actually have much to say.
But on that note I would like to begin with an apology for my absence last Friday. Unfortunately we have once again reached the closing stages of the year, which means that it is very much "crunch time" at the office; I had to work late last week, which is why I had to ask Steve to run the event on my behalf.
This leads me on to my second point, which is to thank
@Steve Le Gallez for taking over the running of last Friday's event - much appreciated good sir, I owe you one!
I hope that there was not any (or at least too many) issues to deal with or fires to put out on the night. By the sound of it you did a sterling job!
I would also like to take this opportunity to thank everyone who participated in this event!
I hope that you all enjoyed yourselves, in spite of the sightly shorter race, and the technical problems that some of you experienced.
On that note this is a good time to very quickly touch on the issue of "freezing", since several of you were affected by such glitches during the last event. There are several causes for freezes that could occur when playing rFactor 2, which includes network connectivity issues / overload, CPU issues / overload, hard drive issues / overload, and GPU issues. Network related freezes are what we refer to as "lagging", while "warping" is the term often used to describe freezes that are CPU related. Warping is usually only seen by a client whose CPU is being overworked, but in severe enough cases it could potentially be seen by others (as lagging) due to the client not being able to send all of the data for their car to all of the other players. A client with CPU related issues will typically see other cars around them warp because the physics calculations are performed client-side, but their own car may also be affected (in some cases it would even be possible to feel this when driving the car) and this may be visible to other players. If a client is experiencing these problems then they can set the "+highprio" parameter to try and alleviate the issue by giving rFactor 2 greater priority to utilise the power of the CPU. Setting this parameter will have no effect for clients who see another car lagging due to CPU issues for the driver of that car. Meanwhile, if you are lagging or notice lagging (but you do not have any network connectivity issues) then ensure that the upload and download rates are set accordingly to allow a sufficient amount of data to be transferred during a given period. Check out
this video for a clearer explanation.
Finally, I would once again like to apologise for not being able to host an event last week. I decided against organising a race and asking another member of staff to run it on my behalf because it would not be fair for me to once again ask somebody to take over in my stead, and I did not have the time to do any testing in preparation for the race anyway.
However, we are back again this week! If you have not done so already then you can sign up for this Friday's race, at Botniaring,
here! We look forward to seeing you on track!
