1680x1050 should be smooth sailing with even lesser cards.I'm playing this game.currently XFX GTR RX 480 running at 1338mhz and 51'c with Vsync on(1680x1050 , Maximum settings).even my card is not under pressure ( lower than 45% , Ryzen is on 19%)
No offense, but I think that's a silly justification for the poor performance. I think that because the game is released and I've already spent my hard earned money on it, as have many others. I shouldn't have to wait for patches to make the game playable, or have decent performance, that may or may never come.
I guess what I'm saying is that if those graphical features and performance patches hat you mentioned weren't ready by the scheduled release date, maybe they should've delayed the game until they were implemented.
The more I find out about Tiago Sousa, the more I like him. He's a true professional, a man that takes pride in his work. He just revealed some technical info about Id Tech 6.5 in Wolfenstein 2 from his Twitter account, and this engine is just incredible:
1) +30k drawcalls per frame, up to +6 million triangles per frame (low level API be praised!). That's almost half a billion tris/2 million drawcalls per sec. 30 times the amount of draw calls found in Doom
2) All "fog" is volumetric and unified, every light + shadow + indirect lighting affects it, including water caustics / underwater light scattering.
3) Water surface is "tessellated" on the fly without GPU tessellation. Caustics are dynamically generated and derived from water surface. Water geom also uses async compute jobs to async with itself ( which is kind of crazy ).
And he hasn't finished optimizing yet! He says there's still room for improvement!
All that and at launch I couldn't change graphics settings without my system rebooting and weird scaling issues playing on my 4k tv.
What pride they have!
And people like to bm cpu comparing them for like 20% drawcall difference.
Then comes a game like this and is like 1000% more efficient at it out the gate just because of low level api.
30k drawcalls in a fps. Holy moly. New times is comming at last. Good.
Except on console they do it even smarter and sidestep the mass amount of draws approach.
No details yeah though, hopefully they put out a paper or someone does another dissection.
My wish list--patch in an F Key save function. Please.
Guru3d Wolfenstein II performance review, benchmarks:
http://www.guru3d.com/articles_page..._pc_graphics_analysis_benchmark_review,1.html
Huh, so much stuttering in that video... it's clearly visible in frametimes graph - something is really borked for GeForce cards.Guru3d Wolfenstein II performance review, benchmarks:
http://www.guru3d.com/articles_page..._pc_graphics_analysis_benchmark_review,1.html
What video? Game running smooth as butter on a 1070 for me (388.00 driver). There have been some complaints of stuttering on 388.13 driver (as used in review) which many say was solved by reverting to 388.00. MSI Afterburner FPS polling was also claimed to cause some stuttering issues.Huh, so much stuttering in that video... it's clearly visible in frametimes graph - something is really borked for GeForce cards.
The frame times in the OSD are consistently under 25ms (there is a decimal pt before last digit). There should be no stuttering in actual gameplay according to that. Whatever 'visible' stuttering there may be is more likely vid capture related (shadowplay).Last page of that review.
Seems Fiji is not well optimized in this game (keplerized?). A RX470 is ahead of it at all resolutions.Anyone else getting terrible performance using a Fury x @1080p with high settings? With high settings, I can't even maintain 60fps.
Seems Fiji is not well optimized in this game (keplerized?). A RX470 is ahead of it at all resolutions.
http://www.guru3d.com/articles_page..._pc_graphics_analysis_benchmark_review,4.html
F5 does not save here.Is your function a universal F5 save or just for the game ?
I upped the visuals to Mein Lebel from Uber and like the charts suggest, the fps dropped to ~90 from 120.