Palit GeForce GTX 1650 KalmX review
Guru3D Rig of the Month - March 2020
Deepcool Gamer Storm Macube 310P review
NVIDIA Shield Android TV 2019 review
Fractal Design ERA ITX chassis review
Gigabyte TRX40 Aorus Master review
XFX Radeon RX 5600 XT THICC 2 review
Cougar Blazer review
NZXT Kraken X63 Review
Team Group T-Force XTREEM ARGB DDR4 review
Battlefield V Open Beta: PC performance benchmarks
Posted by: on: 09/06/2018 11:54 AM [
103 comment(s) ]
In this quick article, we'll check out some graphics cards with Battlefield V Open Beta. The performance is a mixed bag, the however is shaping up to be something really good.
Read article
Advertisement
pages 1 2 3 4 > »
Hilbert Hagedoorn
Don Vito Corleone
Posts: 37295
Don Vito Corleone
Posts: 37295
Posted on: 09/06/2018 12:27 PM
Yeah I know, in its current state it's just so difficult to measure. I've placed many disclaimers in the article, and in fact, have been doubting to even post it as really numbers are all over the place depending on where you are on a map and indeed resolution. Better something than nothing I figured. Once the final game is out I can streamline a good path/scene to measure in, precisely.
These results, I've given it to be a preliminary and indicative classification, not a precise one.
Yeah I know, in its current state it's just so difficult to measure. I've placed many disclaimers in the article, and in fact, have been doubting to even post it as really numbers are all over the place depending on where you are on a map and indeed resolution. Better something than nothing I figured. Once the final game is out I can streamline a good path/scene to measure in, precisely.
These results, I've given it to be a preliminary and indicative classification, not a precise one.
Fox2232
Senior Member
Posts: 9950
Senior Member
Posts: 9950
Posted on: 09/06/2018 12:38 PM
Yeah I know, in its current state it's just so difficult to measure. I've placed many disclaimers in the article, and in fact, have been doubting to even post it as really numbers are all over the place depending on where you are on a map and indeed resolution. Better something than nothing I figured. Once the final game is out I can streamline a good path/scene to measure in, precisely.
These results, I've given it to be a preliminary and indicative classification, not a precise one.
Not really surprising. In one of dev. team talk they said something weird. That, they have bad performance from using many instantiated objects. And instead they try to combine as much geometry under one instance as possible.
That should not be problem, but it looks like their solution is choking AMD's driver or cards somehow and preventing them from fully utilizing brute part of architecture. That bottleneck is likely "removed" by higher resolution as there is more brute force work required than there is load on bottlenecking serial operation.
May be anything, but my guess would be geometry discard as they make those objects complex.
Yeah I know, in its current state it's just so difficult to measure. I've placed many disclaimers in the article, and in fact, have been doubting to even post it as really numbers are all over the place depending on where you are on a map and indeed resolution. Better something than nothing I figured. Once the final game is out I can streamline a good path/scene to measure in, precisely.
These results, I've given it to be a preliminary and indicative classification, not a precise one.
Not really surprising. In one of dev. team talk they said something weird. That, they have bad performance from using many instantiated objects. And instead they try to combine as much geometry under one instance as possible.
That should not be problem, but it looks like their solution is choking AMD's driver or cards somehow and preventing them from fully utilizing brute part of architecture. That bottleneck is likely "removed" by higher resolution as there is more brute force work required than there is load on bottlenecking serial operation.
May be anything, but my guess would be geometry discard as they make those objects complex.
Denial
Senior Member
Posts: 12650
Senior Member
Posts: 12650
Posted on: 09/06/2018 12:53 PM
I wonder what it is about Frostbite that makes DX12 such a mess. You'd think the team that requested/helped AMD build an entire low level API would be the best at DX12 and yet they are somehow one of the worst.
I guess we'll see when the final build ships and numbers updated but the performance/stuttering mentioned doesn't look any better than their previous DX12 implementations.
I wonder what it is about Frostbite that makes DX12 such a mess. You'd think the team that requested/helped AMD build an entire low level API would be the best at DX12 and yet they are somehow one of the worst.
I guess we'll see when the final build ships and numbers updated but the performance/stuttering mentioned doesn't look any better than their previous DX12 implementations.
fantaskarsef
Senior Member
Posts: 11364
Senior Member
Posts: 11364
Posted on: 09/06/2018 01:06 PM
I don't know about DX12 with the Frostbyte engine... I tend to wonder the same as you @Denial , especially as they are actively working together with Nvidia to implement RTX, which is DX12. But to what use if the DX12 adaption itself is lacking? Maybe they should first fix their DX12 "container" itself before thinking about RTX performance numbers, since those are crippled by, well being DX12 on Nvidia and Frostbyte in the first place.
I don't know about DX12 with the Frostbyte engine... I tend to wonder the same as you @Denial , especially as they are actively working together with Nvidia to implement RTX, which is DX12. But to what use if the DX12 adaption itself is lacking? Maybe they should first fix their DX12 "container" itself before thinking about RTX performance numbers, since those are crippled by, well being DX12 on Nvidia and Frostbyte in the first place.
pages 1 2 3 4 > »
Click here to post a comment for this article on the message forum.
Senior Member
Posts: 970
Interesting the Vega performance seems lacking at 1080p & 1440p, yet take a jump at 4K.
Thank you HH!