Bug Info: E Class Multiplayer Racing
Platform: Windows PC
Edition: Premium
Account: solo account
PC GPU: 3090 565.90
Peripheral: Fanatec CSL DD w Fanatec Clubsport v2 Pedals & TH8A
Settings: Full HUD
Content Update: Started in the latest 10GB update. Fuel load is showing and mapping to 100% in practice but works properly for quali session
1 Like
Seems to be a glitch with update 13. Happening on Xbox X/S too
I’ve just had this happen in the Multiclass series (ABCS), specifically at Road Atlanta (full).
I set my fuel load for 4 laps for qualifying, but got a full tank instead. For the race the fuel was set to the amount I put it at. For the next event at Suzuka, this did not happen.
This happened to me on PC (Windows store).
Had this happen in every multiplayer race last night, both Private and Featured. The others in my lobby also experienced this, Xbox Series X and PC.
MOR:
- Enter a race that has a Practice/Qualifying session
- Set your fuel to any value not 100%
- Enter Practice/Qualifying
- Observe fuel load, it should be at 100 percent and then drop down as you burn fuel from driving.
Once you have done this, back out of Practice/Qualifying then enter again, and it’ll function “normally” with the fuel load you originally assigned.
6 Likes
Not just limited to E class but can confirm PJs advice works
the question is, is it a visual bug or are your performance is actually affected? (due to max fuel load)
It’s not visual, it’s tracked in UDP.
game defaults back to max fuel in practice after setting it, you basically have to leave practice and go back on track to get the desired fuel.
@T10ManteoMax could you please remove E Class from the thread’s title since all classes/lobbies are affected by this?
It’s not exclusive to E, it’s happening in every race online.
that is literally what i wrote
Your request doesn’t make sense then.
Why remove one class for a bug when all classes have the same bug?
Surely the logic there is to remove all classes
As this is in the bug logged
tag now I reckon the fuel fix is already being worked on, either for a hotfix or next update.
If you remove E Class from the title it stands for all classes. not sure why that’s so hard for you to understand.
Current Title: “Setting Fuel Load for E Class Qualifying is resulting in 100% Load in Practice” (title implies only E class is affected)
Edited Title: Setting Fuel Load in Qualifying is resulting in 100% Load in Practice. (implies it’s a general issue)
1 Like
Now that’s much clearer, you’re referring to the forum thread title and not the game.
|Bug Info:|featured multiplayer, when in practice the fuel tank is full no matters what i choose before. Exit practice and enter again and its OK|
|Platform: |, cloud, Premium or game pass
|Account: family sharing
|Xbox Settings: quick resume
|Content Update: start after update 13th
Following latest update the full fuel bug has returned
Since Update 13, when you adjust the tank amount you get it back to 100% as soon as you go into practice or qualifying. The problem applies to the career as well as to the multiplayer and occurs in practice as well as in qualifying.
Bug Info: When playing practice in career mode, the fuel load starts always full even if you choose another load. When you start the real race, the fuel load is correct
Platform: Steam
PC GPU: Nvidia 4070ti super, driver version: 565.90
Settings: Ultra
Attempted fixes: Rebooted game and system
Content Update: It started after content update
Bug Info: career, multiplayer practice fuel level
Platform:Series X
Edition: Game Pass,Premium Add-On
Account: solo account
PC GPU: n.a.
Peripheral: n.a.
Settings: English, Preformance mode
Xbox Settings:Quick and fresh start
Attempted fixes:Rebooted, after fresh install
Content Update: Update 13
Fuel level set before start of practice is not the eventual fuel level during the pratice round, see pics.
Note, this after a year is unacceptable as a bag, special a year after release it still doesn’t show that update are actual tested.
AND THIS IS NOT AN E CLASS ISSUE BUT A GENERAL ISSUE!!!
This had been solved already, but there’s always the chance for this bug to reoccur as it has…normally with big content updates. It’s natural that it’s happened again so I wouldn’t freak out too much.