@04dcarraher said:
poor tomato swimming in his delusions and doesn't haven't a clue about the facts.
1. PS4 has better API bypassing DX 11 based limits..... again ignoring the facts.
2. I can give two shits about ether console, its you and twisted ideas, half truths and lies about the facts.
3. You are making assumptions based on bias outlook of bashing anything MS. DX12 is not a game changer allowing the X1 to be all powerful, its fixes and updates its flawed current API, adds new tools. This wont allow the X1's gpu to gain enough performance to close the large gap. fact is you have been proven wrong about Dx12 not doing anything while almost all dev's say it will help to some degree.
4. You keep on dreaming with the delusion with i3 vs i5, with a game where its draw calls are single threaded orientated. Again, fact that i3 out paces FX 8's or FX 6's means its not the cpu power you fool but poor allocation of cpu resources. A properly coded game FX8 trumps the i3. Fact that you still ignore cpu usage charts just hardens the fact your a troll.
5. You have no idea..... the cpu is the root of most of PS4's framerate drops and the reason why PS4 is limited to fps caps and they still drop. In the patch that introduced the framerate issues and stuttering are areas where cpu usage is higher....
6. lol just sad you clump everyone into one group, ACU issues were from excessive networking code eating Cpu cycles. Which means that PS4 does not have the cpu resources not to be fully allocated or you run into issues feeding the gpu. Having that extra cpu core and slight upclock can make a difference in areas however because of the PS4's large gpu advantage getting that extra couple frames means squat when the stronger gpu can push another average 10+ fps with resolution increase.
1- I do know that and i have claim DX12 will never be as clean as sony API thank to DX12 been made to work with more than 1 hardware,is not an excuse you can't hang op to pathetic fanboy because you CLAIMED the CPU was the problem on the witcher not the API,in fact you moved not to ACU a screw up game to try to prove your weak point,if the API is more efficient for project cars is also more efficient for Assassins Creed Unity and Witcher 3,and in fact Ubifost had 2 games superior already on PS4 ACU was screw up and on purpose hold back.
2-Lets see how many times have i see you defending the PS4 like you daily defend the xbox one.? Yeah few or non.
3-All the argumenst about DX12 come from Brad wardell the argument you use about multithreaded rendering come from him,he claimed double performance not 7% he claim the xbox one was the biggest beneficiary,it wasn't we all know and you know it is PC,so you are rolling on information of some one who clearly was doing PR for DX12,the reality is the gains are bullshit and you want to pretend DX12 will fix something on xbox one 7% 2 frames on a game were the PS4 is as much as 14 FPS faster.
4-You don't know what a CPU bound scenario is apparently,i fu**ing know the i3 is weaker than a i5,but that is the thing being CPU bound mean that your CPU FOR WHAT EVER REASON CAN'T FEED YOUR GPU,the reason being weaker architecture,lower clock speed,number of physical cores,you name it the end result doesn't change one get more out of the GPU than the other which mean the GPU was being hold back by the CPU,is irrefutable and DF call it as so a CPU bound scenario because that is what it is regardless your excuses,the i5 has more juice per core so it eliver better performance so yeah CPU problem fixed by an i5.
5-No that is what you assume fool,quote developers for the games that drop frames stating that,no you are assuming that is the reason like you assume that was the reason for the drops on the Witcher 3 and you were WRONG you were WRONG you were owned the game runs faster now regardless of having less CPU speed than the xbox one,the code was bad and was optimize..lol
6-Bullshit that wasn't the only problem you blind lemming,ACU was hold back on purpose on PS4 it was screw up because MS freaking had a deal for millions of copy of that game,can't have the PS4 version running better when MS will buy 3 or 4 million and who knows if more from those games and also buy the same quantity of games from ACBF as well.
You are pathetic since you were owned,now you go running and hide on ACU which was a screw up game,which developer freaking focus more on fixing the microransaction part of the game than the gameplay it self,you are no making your argument no favor by using that game,ACBF was 1080p on PS4 there was no reason for ACU to be 900p,f they were CPU bound at 900p they would be exactly the same at 1080p resolution is a job of the GPU not CPU.
Reality is you claimed the witcher 3 was CPU bound trying to prove that Project Cars didn't matter,and you get owned by CD Project..lol
@ronvalencia said:
Your citing of PC's i3 vs i5 for Project Cars is pointless since at it's quad threads mode would halve it's single thread performance and your Project Cars DX11 PC example will be obsolete by a confirmed DX12 build.
Project Cars DX11 PC build runs on a single rendering thread.
According to SMS, a single thread from Intel Core i3/i5/i7 at +3 Ghz ~= four AMD Jaguar cores at 1.6Ghz. Dual thread mode for Intel Core i3 would halve it's single thread performance hence the bottle neck. DX12 removes this bottleneck.
Gaming PC is NOT limited by Core i3 i.e. the user has the option to upgrade i.e. PC is not a static hardware games console.
Six AMD Jaguar cores at 1.6Ghz doesn't equal Intel Core i5 period!
Now this is gold...hahahaaa
1-Pointless my ass,i have a source backing my statedment with a fu**ing benchmark showing how the 750TI was buttleneck by a i3 on the game,a CPU bound scenario is when you CPU for what ever reason CAN'T FEED YOUR GPU FAST ENOUGH,now the i5 got more frames because it has more per core performance than an i3 that is a FACT so yeah the CPU bound scenario was fixed by i5.
Lets wait and see because what you showed me was a damn screen showing dual 980GTX on SLI which do require way more CPU and used a i7 in nothing that setup represent an i3 with a 750ti in nothing.
Project Cars on PC is multithreaded it was just disable probably for the problems SMS faced.
Steam Startup parameters (right click Project CARS/Properties/Set Launch Options - Multiple strings separated by a single space):
Multi threaded -dx11mt
Cap Framerates -fpscap xx (ex. -fpscap 60)
Launch 32bit -x86
DirectX 9 -dx9
Disable crowds -skipcrowds
Disable VR headset support -novr
Disable join in progress (multiplayer) -disablejip
Developer Cameras -devcameras
Number of physics threads:
-pthreads 1 / -pthreads 2 / -pthreads 3 / -pthreads 4
• Default physics threads = 2
You can enable it...lol
And Project Cars was anounce as using DX11MT dude when it was on developments.
And? My argument wasn't the Jaguar is stronger than an i3,my argument was the game demanded more CPU than most game out there and was faster on PS4 over the xbox one.
No one is talking about gaming being limited by an i3 you walking salami get your fact straight and stop talking irrelevant crap,you also claimed the PS4 was CPU bound on the wtcher 3,and you are also officially owned..hahahahaa
How many times have i told you this games are screw up and not CPU bound.? Hahahaaa
Quote me saying a 6 core Jaguar = an i5 buffoon...lol
@StormyJoe said:
@tormentos: in one post, you boast about Sony's proprietary APIs, the next you say devs will use DX12.
Sigh... Back to ignoring the fanboy...
Yeah go ahead and spin what i say DX12 LIKE CODE is not the same as using DX12 buffoon,DX12 like code = mantle,vulcan GNM.
Yeah you can pretend to ignore me again after,you falsely claime DX12 would bring 12 to 14% more performance,because you can't read for sh*t..lol
You were owned by your own link..lol
Log in to comment