FP16 isn’t a magic performance doubler. This very article shows 20-30% gains only on parts of rendering that can use it, and not all parts can.

Forza Motorsport 7 X1X edition says hi.

an 8K 120Hz display would need to exist on the consumer market first

> “FP16 is not 2 instructions at once, its just a less complex instruction VS the standard FP32”

No, but it is twice as many calculations per second, cause if it wasn’t, there were no point to it at all.

PC has compromises. Can I play every game at 8K resolution at 120 fps? No, so compromises!

> “common sense can tell anyone that”

No, it’s a technical discussion, so it has nothing to do with common sense.

True , i really think this could have done with at least another month in the oven.

Yeah I noticed that on Eos when you kill that big massive fiend thing with a yellow health bar at one of the old research stations when I drove back through it later, was looking for it for ages as I couldn’t remember where I killed it and then gave up.

It was just in a good enough state most likely. Kick it out the door if we can be bothered fix it later we will

Yeah probably , i am not sure if this glitch is also on the PC but when you go back to an area they say the same things even after you have completed that section. Such as ”We’re under attack” yet nothing is there and even after you scan bodies if you drive back there it still says there is a body there you should scan. Pretty poor as no way they playtested this much.

Well the pro doesn’t run at max settings anyway. But yeah generally BF is better looking with stuff but it’s also not open world. It’s probably just poorer optimisation of assets, game code, lods whatever it may be

ACtually after playing it last night on the Pro not all that many effects at all. The particle effects are pretty subdued actually. Fire is rendered very poorly and even when you kill a creature it is pretty weak . Probably more realistic but it doesn’t make it satisfying to win a battle other than you can move on.