Forum Discussion
I also have issues with TN.
I've collected some logs from HWMonitor and took some screenshots of performance and network graphs.
If any of the devs find it useful, you can check them here. I hope the Polish language in the logfile won't be a blocker - the most important part is that there are no bottlenecks on GPU, CPU, or Memory (at least none are under 100% load, and there are no thermal throttling flags in the logs).
https://drive.google.com/open?id=1W7LEWibmnK-5MEibgKI8XhhnnLBP_O8l&usp=drive_fs
With auto (performance settings) and no DLSS I get around ~50 fps. In chaotic moments it drops a bit, but it still feels too low to play on official servers.
TN on officials jumps between 300 ms and 1500 ms, which makes it unplayable. In comparison, on community servers my TN stays at 15-25 ms.
Hardware: Asus Vivobook 15 Pro, M3500QC (Ryzen 5600H, RTX 3050, 16 GB LPDDR4 3200 MHz).
All drivers are up to date. I've already tried the solution with creating a user.cfg file. Unfortunately, my BIOS doesn't support any memory overclock - I've heard this helped some users.
If any of the devs need more data that might help debug the issue, let me know. Currently, the game is absolutely unplayable outside community servers, and in my region it takes dozens of minutes to find a free slot on any of them.
PolishDrunker I reviewed all your screenshots below. The only thing I see is CPU speed dropping below 4GHz, probably due to thermal throttling.
https://drive.google.com/open?id=1W7LEWibmnK-5MEibgKI8XhhnnLBP_O8l&usp=drive_fs
Please post a screenshot of HWiNFO System Summery so I can see your RAM configuration.
- PolishDrunker10 days agoSeasoned Novice
Here you go, by the way – the manufacturer of this notebook was like: "Oh, there are two 1600 MHz chips, let’s just call it 3200."
- OskooI_0079 days agoSeasoned Ace
PolishDrunker thank you for posting the HWiNFO System Summery.
The CPU memory looks good. It's in dual channel mode and running at 3200MHz.
The reason it says 1600MHz instead of 3200MHz is because it's double data rate (DDR) memory, which transfers data twice per clock cycle.
1600MHz x 2 = 3200MHz
It's confusing. The memory is running at 1600MHz but because it transfers data twice per clock cycle it's considered 3200MHz memory.
Try turning the CPU fan speed up to 100% and see if that keeps the CPU speed closer to 4GHz.
You can see CPU speed in Windows Task Manager under CPU performance tab.
- condabsy9 days agoSeasoned Newcomer
Thanks for the tips re: check if CPU is thermal throttling, and also explaining why TN exists. essentially, no matter of settings changes can reliably get this game above 60 fps on my CPU, despite my GPU being able to pump out 90-120-180+ depending on quality settings.
That explains why capping FPS around 50 or 55 helps, but it is incredibly disappointing that it essentially forces a lot of people to buy a new system for 1 game due to the way BF has developed their game. I think the only reason this is a big issue is because minimum requirements historically means "you could try running the game with lower specs, but it will run at a low framerate" whereas for BF6 it means "if your CPU is just above, or too close to minimum specs, your experience will be severely degraded to the point where you probably won't enjoy this game despite getting 120+ fps". I think DICE has a different expectation of "minimum specs" or they just didn't do thorough testing.
Pretty rough pill to swallow when you have to spend AUD$800 (most people would be stuck on an old socket, so at minimum, a new board, RAM, CPU & cooler) all just to get 1 game to run but all the other games play nicely... Definitely questionable development, but when the game has launched as successfully as it has, this type of feedback/issue is just never going to be heard or have any real impact on the dev team. Maybe a bit of a depressing take, but that's how I see it.
My specs
CPU: Intel i5-9600K (tried non-OC and OC)
GPU: 5060 Ti 16GB
RAM: 3000MHz 2x8GB, XMP enabled, clocked at 3000MHz
About Battlefield 6 Technical Issues
Recent Discussions
- 35 seconds ago
- 5 minutes ago
- 8 minutes ago