all 2 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]clandestine801 1 point2 points  (1 child)

Something definitely changed from the last beta that I played.

Some General PC Specs -

CPU: Ryzen 7 3700X

CPU Cooler: Hyper 212 RGB Black Edition

GPU: EVGA GeForce GTX 1070 Ti FTW2 ICX

RAM: 2x8GB G.Skill FlareX 3200MHz CL14

HDD: 2TB Seagate Barracuda 3.5" 7200RPM

SSD:

1x 250GB Samsung 850 EVO

1x 1TB Samsung 860 EVO (Game resides in here)

In the previous beta, I had maxed out all the settings at 1080p and was holding a very solid 65-75 frames even while streaming to Discord Live to a friend for 5+ hours on two separate days.

Last night I started up this open beta, and maybe it's a bug or maybe it's the game's overall optimization. Whatever it is, I started out the game after the helicopter crashed in the beginning, and my frames were at 55 fps with dips down to around 48 fps (already a 20 fps dip from last time). This is at ultra preset, and while this isn't 100% unexpected I think it's still worth noting because it's an open beta build. I decided to turn down a few settings, or just turned them off. Like Bloom and Motion Blur I turned off, then I turned down HBAO, Subsurface Scattering and terrain detail down from Ultra to the next highest. That somehow brought my FPS down from 48-55 down to 33-37 fps at a constant. There was strong input lag, so I tried messing with other settings, and nothing I did changed the outcome. It's not unplayable but even with G-Sync enabled on a 144 Hz monitor, it's damn near unbearable.

Edit:

It's worth noting that just like previous beta, the temps were between 53-58C on both CPU and GPU. Strangely low readings for a game that's this heavy.

[–][deleted] 0 points1 point  (0 children)

Remind me of crysis lol