Not crying. Both machines are great. Just optimized code is very important, especially to take advantage of system specific things. (like I would love to have a classic style Monster Hunter on XBO where you stream into the machine to generate random monsters like the original PS1 version, but developers are pretty.. dumb. haha. Hope Capcom sees this 😉 )

Cry some more.

obsolete? You mean the PS4’s 7870 related GPU chipset vs the XBO’s 7770 related chipset?

Also they use the same 8core cpu. The PS4 has an ARM proc to handle OS, communication and basic handoffs with a dedicated 256MB of ram.

I hate Ballmer had to grub the XBO to be a set top box. Wish they fired him before XBO development started.

because it’s the 1080epeen generation :

MADNESS is designed around DX11 and DX12 versus a true broad API like Unreal which large corps pay for platform specific tuning by the api’s developer.

Still excited about DX12 for Win10 :S

latency? The Ram Processor and GPU have an open interconnect. If there’s issues it’s the fact they coded it more for DX than an API that would work efficiently on both machines. This isn’t a sign of a a better proc (which the XBO is a flat proc speed while ps4 has a lower base but can burst) or gpu but the fact the Developer knows more than DX than other API. Also designing around DX they probably didn’t use the processors full potential. It’s all about their poor coding and their trying to blame the machine.

Fanboy. They built the game around DX. Of course it will run better on XBO. This is more about a coding choice and not machines. Derp.

We see it is still not as good as the PS4.

Because I like my own comments :/
At least I don’t get swayed by advertising propaganda and think that one platform is better than the other solely based on brand and flashing logos even though there is a veritable cornucopia of features and specifications in which it is crushed by a similar offering

1.-Occlusion culling and frutrum culling to reduce the numebr of draw calls from cpu to gpu relieving lots of strain if well used

here is a developer who is using this solution

https://twitter.com/ShinenGames/status/484587218304892930

There is also the option of batching for reducing draw calls on cpu as well

http://docs.unity3d.com/460/Documentation/Manual/DrawCallBatching.html

and as a last resort they can put a dynamic frame buffer so that resolution will change instead of the frame rate during gameplay, just what sony did on Wipe Out HD to keep 60fps at variable 1080p(there where drops as low as 1280x1080p)

http://www.eurogamer.net/articles/wipeout-hds-1080p-sleight-of-hand