Le Mans Ultimate plans network fix and public endurance tests

Studio 397 is targeting September 15 for a Le Mans Ultimate fix addressing the phantom collisions reported in recent online races. Its September 11 update says the suspected cause is separate from the network-protocol work that has already been partly rolled back. [1]

Why the network changes were rolled back

In August, the developer reverted some protocol changes through version 1.4.1.3 after problems persisted for certain connection types. Studio 397 said much game traffic was unchanged, but the new implementation appeared to interfere in some situations. It continued to back RUDP as a way to reduce disconnects while acknowledging that the implementation needed more development. [2]

The planned solution was to run designated RUDP tests inside the public game while leaving other servers on the established protocols. Participation would be optional, with a geographically varied group helping expose connection conditions that a small internal test might miss. [2]

Official gallery

Tap an image to open a larger view.

Silverstone and Le Mans host the endurance tests

The updated schedule lists a six-hour Silverstone team test on September 18 at 08:00 UTC, using ELMS LMP2, LMP3 and LMGT3. A twelve-hour Le Mans test follows September 25 at the same time, with 62 cars across Hypercar, WEC LMP2 and LMGT3. The programme supports preparations for October’s 24-hour Le Mans event. [1]

Regular weekend races remain available

A four-hour Silverstone team race remains on September 19–20. September 26–27 has a 2.4-hour event with its venue still to be announced. The week beginning September 14 also includes Tuesday and Thursday 90-minute Le Mans tests for single drivers. Studio 397 says dates can change as fixes are deployed. [1]

The distinction between test sessions and regular races is important for teams allocating practice and driver time. The longer Friday events are gathering data on network changes; their place in the public calendar should not be mistaken for confirmation that the collision issue has already been resolved.

A planned patch and a successful endurance run are separate milestones. The next evidence will be the released fix and what the public sessions reveal under sustained, populated-server conditions.