——The Official Battlefield 6 Thread——

Novelty has worn off after a few hours.

Frame gen in by default made the game feel awful, but better now I've found the settings to stop it.

Anything other than "all out warfare" with closed weapon groups plays like ass, but the queue times for this game mode is already feeling slow.

Every other game mode is just ruined by people not playing their roles, support running and pushing with assault rifles just to feed themselves ammo and won't bother to revive anyone or play behind their squad.

All the maps are too small for any real use of air vehicles, plus teams spawning behind you constantly.

Honestly wish I could refund but played too many hours.
 
Some chat on another forum with the user.cfg file where intel users should be setting the core/thread count for P-Cores only instead of the total counts as per what task manage shows, well I tested this out and the performance is lower than even stock

I did a test with 8,8,16 in the config file since my 12700KF has 8 P-cores so 16 threads just now and got the following on the same map and RTSS bench run of 3.7 minutes again:
Benchmark completed, 27085 frames rendered in 225.297 s
Average framerate : 120.2 FPS
Minimum framerate : 74.2 FPS
Maximum framerate : 152.5 FPS
1% low framerate : 69.9 FPS
0.1% low framerate : 59.5 FPS

Vs the config file accounting for all threads/cores inc E-cores which I posted previously:
Benchmark completed, 29972 frames rendered in 229.313 s
Average framerate : 130.7 FPS
Minimum framerate : 107.2 FPS
Maximum framerate : 146.9 FPS
1% low framerate : 89.9 FPS
0.1% low framerate : 72.7 FPS

RTSS overlay:
Ke2TKy7.jpg


Notice that one core is showing as idle basically, this never happened with stock or the previous 12/12/20 User.cfg. I also note that the game "feels" slightly jittery with this P-core only config vs what I had before or with stock.

I think the point of this config mod is to reflect what Windows shows, as Intel Thread Director will then do what it does best and allocate threading intelligently which it does really well on well optimised games.
 
  • Like
Reactions: ne0

The start of this video is so familiar, hits on heli's that you can see and not registering. He has quite a few points, apparently some maps aren't even spawning vehicles properly, that Manhattan map with the helicopter is meant to have 2 copters and one only spawns for one side, among other things.
 
Last edited:
Was playing late last night, was 3-5 minutes for lobby to fill up, even then half the server was bots. That being said, this was 2am on a Sunday
I have found that if you custom search for games if the wait is too long it creates a new server instance that is initially filled with bots and it tries to populate those bot slots with other humans that are waiting to join similar games. I havnt had the same issue trying to join from the "playlist" options.
 
Just had a couple of fantastic rounds myself.
Closed weapon all out warfare is my go to at the moment. It must attract the more seasoned BF enthusiasts because most rounds are so much fun, and actually involve teamwork. Tougher but closer rounds.
The open weapon lobbies tend to be a sweat fest full of cod kiddies from my experience. No teamwork, the multitude of open mics with domestics, heavy breathing and kids shouting are dead giveaways. You get the odd decent round but it's the exception rather than the rule.

Might give that mode a whirl tomorrow.
 
I have found that if you custom search for games if the wait is too long it creates a new server instance that is initially filled with bots and it tries to populate those bot slots with other humans that are waiting to join similar games. I havnt had the same issue trying to join from the "playlist" options.
That's another reason not to buy, bots in MP. Personally I'd rather play with 10vs10 or 20vs20 humans etc rather than 20 humans and 44 bots. Less players might even make the small maps half decent.
 
That's another reason not to buy, bots in MP. Personally I'd rather play with 10vs10 or 20vs20 humans etc rather than 20 humans and 44 bots. Less players might even make the small maps half decent.
Its a little frustrating I just quit out if I encounter bots, its rare that I do though. I get the idea, start and populate the server then replace them with humans. However, you get a lot of people like me who just wont engage with bot filled servers.
 
Just had three amazing rounds, came near top in all with high kd and high score for revives and capturing

The difference? Hitreg was working fine! :rolleyes:
 
Last edited:
Interesting video.

Ryzen 5950X, 5 year old CPU how many cores do you need?

RTX 4080 1440P DLSS Balanced.

2 cores 4 threads: 40 FPS
4 cores 8 threads: 90 FPS
6 cores 12 threads: 120 FPS
8 cores 16 threads: 130 FPS
16 cores 32 threads: 120 FPS (different more CPU demanding map, probably not going to get much more over 8 core 16 thread at this point anyway)

So 8 cores 16 threads, at least for an old Zen 3 CPU, i actually get a bit more than that with my 5800X, about 150 FPS, but i'm using an AMD GPU and they have a lower driver overhead than Nvidia so you get high FPS if CPU bottlenecked.


Obviously a newer Ryzen GPU is going to blow the old Zen 3 out of the water but those old cores are not bad, the Intel CPU at the time was the 10900K and the 5800X in this game blows that out of the water by a solid 20%. Still a good CPU, hence they still sell by the millions.
 
Last edited:
Interesting video.

Ryzen 5950X, 5 year old CPU how many cores do you need?

RTX 4080 1440P DLSS Balanced.

2 cores 4 threads: 40 FPS
4 cores 8 threads: 90 FPS
6 cores 12 threads: 120 FPS
8 cores 16 threads: 130 FPS
16 cores 32 threads: 120 FPS (different more CPU demanding map, probably not going to get much more over 8 core 16 thread at this point anyway)

So 8 cores 16 threads, at least for an old Zen 3 CPU, i actually get a bit more than that with my 5800X, about 150 FPS, but i'm using an AMD GPU and they have a lower driver overhead than Nvidia so you get high FPS if CPU bottlenecked.


Obviously a newer Ryzen GPU is going to blow the old Zen 3 out of the water but those old cores are not bad, the Intel CPU at the time was the 10900K and the 5800X in this game blows that out of the water by a solid 20%. Still a good CPU, hence they still sell by the millions.
I do wish you could still get the 5800X3D. I stop gapped with a 5600x whilst waiting for it and because that was so good I never got round to buying the 5800X3D and before you knew it, it was EOL and not to be found anywhere.
 
Some chat on another forum with the user.cfg file where intel users should be setting the core/thread count for P-Cores only instead of the total counts as per what task manage shows, well I tested this out and the performance is lower than even stock

I did a test with 8,8,16 in the config file since my 12700KF has 8 P-cores so 16 threads just now and got the following on the same map and RTSS bench run of 3.7 minutes again:
Benchmark completed, 27085 frames rendered in 225.297 s
Average framerate : 120.2 FPS
Minimum framerate : 74.2 FPS
Maximum framerate : 152.5 FPS
1% low framerate : 69.9 FPS
0.1% low framerate : 59.5 FPS

Vs the config file accounting for all threads/cores inc E-cores which I posted previously:
Benchmark completed, 29972 frames rendered in 229.313 s
Average framerate : 130.7 FPS
Minimum framerate : 107.2 FPS
Maximum framerate : 146.9 FPS
1% low framerate : 89.9 FPS
0.1% low framerate : 72.7 FPS

RTSS overlay:
Ke2TKy7.jpg


Notice that one core is showing as idle basically, this never happened with stock or the previous 12/12/20 User.cfg. I also note that the game "feels" slightly jittery with this P-core only config vs what I had before or with stock.

I think the point of this config mod is to reflect what Windows shows, as Intel Thread Director will then do what it does best and allocate threading intelligently which it does really well on well optimised games.
Interesting, I might have to play with some settings too. I also have 12700k
Deleted the user.cfg file last night and icue stopped crashing.
 
Back
Top Bottom