Is multi threaded/ core performance finally making an impact on games? Pic realted, fx8320+gtx960. Ultra settings, SMAA 1080p
>>54890614
>doom devs support AMD at RX 480 launch
>ingame AI called "Vega"
they shilling or did they just go "ohey cool name we gonna borrow that"
>>54890668
Actually didn't think about that Vega link.
>>54890614
APUs are going to make an impact also. I was reading some where DX12 will take an AMD A10 with 512 stream processors and add it to the GPU amount. ex. APU512 + GPU2048= 2560 Stream Processors
>>54891131
DX12 seems very promising for AMD.
>>54890614
no, but my threads use multiple games.
>>54890614
get the fuck back to >>>/v/
>>54892268
Cry me a river bitch, this is a general tech board.
Most games will use multiple cpu threads. The problem is how efficiently they use them. Games like Arma 3 can only efficiently use 2 cpu threads efficiently for example. This is why performance is the same whether on an i5 or i3 and why performance is worse on AMD processors.
Though in the end games that run worse on AMD processors is a sign of bad game optimization.
>>54892419
Look at cpu utlization in the screen cap, pretty balanced loads across all threads.
>>54892662
Can't say for certain but yeah it does appear that all threads are being used efficiently.
>>54890614
>moar threads == moar CPU utilization == moar perfurmance!!1!
No.
>>>/v/
>>54893016
Never said anything about more performance, nigga do you even into comprehension?
>>54893016
it means less chance of CPU bottlenecking and should be in every piece of software.
And then one day all software is so well optimized it uses resources with 100% efficiency and everyone will cry about their house burning down.
>>54893163
>>>/v/
>>54893152
>multi threaded/ core performance
>>>/v/
Multi threading in PC game engines is futile. Thread-safety will hold back overall performance so a thread for physics is out of the question. D3D/OGL calls are pipelined so threading core rendering is also out of the question. Threading is not guaranteed to spread evenly around cores so the whole concept is out of the question. What you /v/kiddies might have meant is multiPROCESSING, not multiTHREADING.
>>54890614
>gaymes
get the fuck out
>>54893475
/v/ is about the game content
/g/ is about technology and the applications of tech
as long as we don't talk about the game content, it's more /g/ than /v/
>>54893509
This.
