Farewell to DirectX?

It amazes me how many people in this thread totally miss the point of the article. Huddy compares a modern PC GPU and a very old console GPU and shows how the vastly inferior console GPU can OUTPERFORMED the vastly superior PC GPU because the PC is forced to choke on the DX API and the code for the console GPU is written directly to the hardware.
Everyone here bitches and moans how all the new FPS games look alike, no innovation, never touching the true potential of the PC hardware. THIS IS WHY!
Everyone was pitching a fit on here a couple weeks ago how the long awaited Crysis 2 is just another console port and does NOT deliver on the graphic potential of the Crytek 2 engine. THIS IS WHY!!!

WAKE UP PEOPLE> Your pragmatism has blinded you to what the possibilities are. Instead you chose the middle road because you bruise easily.

no.
A console got one function, no background services, no windows services, no antivirus. Its locked to 35fps. Runs at 720p. A three core cpu running at 3.2ghz and a gpu connected via a fsb. Now imagine you got lets say a triple core cpu, clocked to 3.2ghz and only need to generate 35fps at 720p and your running on a OS less demanding than Linux. Doesn't matter how junk the gpu is. The cpu and the gpu can perform that task at a low resolution. Both of them are working at full paste and influence the performance. Now when they start stepping up the resolution for consoles then that gpu for it got to change coz the cpu can't help it out as much.
That's why ports are so cpu intensive as well. The Xbox games are cpu intensive it needs to be to help that junk gpu out.
 
This news story could have been titled how Consoles are holding back the PC. The architecture of games are designed around what consoles do best, and then ported to PCs were they run inefficiently. If PCs don't do numerous draw calls well, then to get good PC performance, don't design the game to depend so much on lots of draw calls. When a PC game has DX10 or DX11, that's just a coat of paint on a game designed around DX9. PC games could have demanding portions of code written to metal, bypassing DirectX. It's not that there's too many GPU architectures for this bypass, it's that PCs are so powerful that they run the games better than consoles even without this optimization.
 
no.
A console got one function, no background services, no windows services, no antivirus. Its locked to 35fps. Runs at 720p. A three core cpu running at 3.2ghz and a gpu connected via a fsb. Now imagine you got lets say a triple core cpu, clocked to 3.2ghz and only need to generate 35fps at 720p and your running on a OS less demanding than Linux. Doesn't matter how junk the gpu is. The cpu and the gpu can perform that task at a low resolution. Both of them are working at full paste and influence the performance. Now when they start stepping up the resolution for consoles then that gpu for it got to change coz the cpu can't help it out as much.
That's why ports are so cpu intensive as well. The Xbox games are cpu intensive it needs to be to help that junk gpu out.
No.

Background tasks on decent PC take up a negligible amount of cycles. Take a look at your CPU usage without anything actively running. 0-5% you say? That 5% is not going to cost you some factor of performance.

Writing directly to machine code allows the program to run code directly through the pipeline and get the end result.

Today an API command has to be processed, then the driver will break it down to machine code which can then be executed by the GPU. If each step took one CPU cycle, "direct to metal" would take 1 CPU cycle (1Hz, not 1kHz, MHz, or GHz, 1Hz). DirectX path takes 3-4 times as many cycles to do basically the same thing in this grossly simplified example. That is where performance is gets eaten up.

And to all these people running around in circles with tin foil hats like everything is going to be 1993 again and nothing will work on any computer... I don't believe that will happen. I think it would be possible to do a DirectX version that can translate Direct3D commands to machine code until "DirectX compatible" hardware dies out of use. This is assuming that the ultimate goal of Fusion style chips is a standardized, unified graphics ISA. Everything will run the same on any GPU. And it will be pretty much completely transparent to the user.
 
OpenGL is better overall. Better compatibility and speed. DirectX just gets slower and slower with every new version that comes out. I wouldn't count on Microsoft on being the leader anymore as they are into the Xbox a lot. They don't care if DirectX runs slower as they have the 360.

Er, no. DX had all the legacy shit stripped out in DX10 and OGL was left playing catch up. There's a million other variables too. Yes, OGL used to have 'cheaper' draw calls than DX9, but at the cost of maintaining backwards compatibility, which MS made a clean break with, they suffered. Not that draw call cost is the end / all of performance, like driver implementation, etc etc.

If you've played with wrappers or emulators before, that's the kind of performance hit the PC is taking for Directx or OpenGL APIs. Meaning, there's a beast sitting in your machine, and it's held back by API's. Why you think Nvidia and AMD release driver updates that give a % increase to certain games? So much room for improvement.

No, not even close. There is nowhere near such a massive overhead, there's tools to profile this so it's not like it's a guessing game. The drivers are more than welcome to do behind the scenes hackery to improve performance on a per game level to work around potential inefficiencies on their hardware.

OpenGL is a rendering API. It is faster than DirectX's rendering functionality. Programmers use DirectX anyway because it is an all-inclusive multimedia API, which also includes sound and video rendering, and last I heard it's also getting physics.

No, all that shit is depreciated and gone for a long time. DirectDraw is depreciated, DirectSound is depreciated, DirectInput is depreciated, DirectPlay is depreciated, everything old and now useless is depreciated. Physics will likely never be implemented.


Your games run shitty because they don't play into the platforms strengths, not because there is comically massive overhead. Dev's can drop down to assembly on the CPU side, they can use SIMD stuff to sqeeze even more out, they can profile and fix bottlenecks. They CAN, but the question is WILL they? API overhead is probably the least of your problems unless you are doing something insanely wrong. You shouldn't be making 10,000 draw calls when you can do it in 100 and then blaming it on the API. Shitty optimization that is entirely the developers fault.

Of course they batch on consoles, you think they can just go berserk at no cost? NV / ATI is partially at fault too, you still cannot thread draw call submission in DX11, there's no driver support even this late in the game. Granted, a thinner API with more low level access would be nice, but there is hardly some impossibly huge wall of slowdown due in part to the current API's.

The UGHGH 10x BETTER / FASTER / WHATEVER crap preached by the article is pure shit. Plenty of savagely optimized code is written for the PC still.
 
And to all these people running around in circles with tin foil hats like everything is going to be 1993 again and nothing will work on any computer... I don't believe that will happen. I think it would be possible to do a DirectX version that can translate Direct3D commands to machine code until "DirectX compatible" hardware dies out of use. This is assuming that the ultimate goal of Fusion style chips is a standardized, unified graphics ISA. Everything will run the same on any GPU. And it will be pretty much completely transparent to the user.

You go first old chap! :D
 
This article brings nothing new and nothing but drivel from some marketing guy at AMD...

First, this is nothing new, because everyone should know by now that console SKUs are made for that hardware and that hardware alone. That's why consoles have far less performance issues than a PC, which has to deal with thousands of hardware combinations.

Second, this is drivel because he's forgetting there's competition in the GPU business. For this to work, NVIDIA, AMD, Intel and S3 should share the same architecture, so that the direct to metal approach is viable. No developer is going to have different rendering paths, for each specific GPU architecture in their game. That's ridiculous...
What the Crytek guy says is especially funny, since he's surprised AMD is taking this stance, while at the same time promoting OpenCL, which is yet another translation level in the drivers. It makes no sense...this guy has very little idea of what's he's doing or talking about...
 
Pretty sure this marketing guy actually wrote drivers and shit at one point, so I imagine he's pretty keen on writing the kind of code he talks of.

The only sane way for it to work is if everyone can somehow standardize everything... which is impossible, especially as the hardware evolves. Changed the way shader unit work? Welp, everything might just be fucked...
 
Pretty sure this marketing guy actually wrote drivers and shit at one point, so I imagine he's pretty keen on writing the kind of code he talks of.

The only sane way for it to work is if everyone can somehow standardize everything... which is impossible, especially as the hardware evolves. Changed the way shader unit work? Welp, everything might just be fucked...

*cough* OpenGL *cough*
 
what does that have to do with anything? the hardware needs to be standardized in some way or there needs to be an abstraction layer.

like DX is any different. NV / ATI and developers already literally tell MS what they want implemented.
 
I think it would be possible to do a DirectX version that can translate Direct3D commands to machine code until "DirectX compatible" hardware dies out of use.

Isn't that exactly what Microsoft claimed DX10 and DFX11 are supposed to do?
 
Isn't that exactly what Microsoft claimed DX10 and DFX11 are supposed to do?
Granted, I'm no expert on DirectX. But I have not heard of anything resembling that. DirectX has been adding some ability to program directly to shaders but not in the same vein as setting itself up for the end of its lifespan.
 
Well, I remember them saying before Vista was released they did say DX10 would allow programming closer to the metal and thus give better performance but can't remember the exact details of what they said.
 
Well, I remember them saying before Vista was released they did say DX10 would allow programming closer to the metal and thus give better performance but can't remember the exact details of what they said.

there's less overhead in the new driver model and since dx10. the fixed function pipeline is depreciated, the hardware is more programmable.

Granted, I'm no expert on DirectX. But I have not heard of anything resembling that. DirectX has been adding some ability to program directly to shaders but not in the same vein as setting itself up for the end of its lifespan.

you used to be able to write direct shader assembly code but that is gone since DX10, it's up to the drivers to compile the high level shader code.
 
I bet coders from the 8-bit era just read this kind of article and think "lazy kids can't code for shit!"

All that hardware, all that power and they still cant get decent performance, so lets blame the basic framework and say that's the limitation.

Truth be told, its probably lack of imagination and effort thats the real limitation.

I really miss the ingenuity and resourcefulness of the 8-bit days when an apparent negative aspect or flaw in a machine could then be exploited as a positive.

I bet nowadays if they cant get something to work in a few hours its dumped.

Only now doing an exploit gets you banned for life from every game you own?
 
Er, no. DX had all the legacy shit stripped out in DX10 and OGL was left playing catch up. Blah, Blah, Blah.

Ever looked at the installed base of XP? All that "legacy shit" is going to be the way PC games are written in the near future. I'd be curious to know if they took it out of the XBox SDK. Developers would be willing to drop it if it helps them make X360 games even slightly better, but never change for the PC market. Console ports will use what ever the Xbox SDK dumps out, but I'd expect PC games to include XP compatibility.
 
That's why ports are so cpu intensive as well. The Xbox games are cpu intensive it needs to be to help that junk gpu out.

No, xbox 360 games are usually very cpu intensive b/c of swapping in/out information, textures and the streaming-design approach console games use.

PC games like 'World of Warcraft' or 'Crysis 1' can for the most part load an entire map and a lot of textures, object details, sound effects, music, etc into memory before you've even loaded the level because you may have 2-4GB of memory to work with. If your using a 64-bit machine, potentially you could have 8-16GB.

By comparison, the xbox 360 's CPU has 0.25GB of memory. As a result, when you turn a corner in an xbox 360 game, the cpu goes crazy trying to dump the old information that was in the 'huge' 256mb worth of storage, stream the new information from the dvd drive, load it into memory all the while still maintaining physics calculations, tracking of game variables, maintaing/calculating the next movies for the AI and possibly doing sound effects as well as instructing the GPU a bit what to do and trying to feed the GPU new information if it needs to load its also equally massive 256mb of memory.

The streaming design approach when you have limited memory but want to develop games to look like you have lots of memory (well-scripted AI, unique/non-repeitive level design, well detailed, rich, vibranted textures with detailed high-polygon count models in both player models and environment) is a necessity. You can't create memory storage out of nothing on a console. You can't even rely on HD paging file systems as the 'arcade 360' doesn't come with a HD. The downside to the streaming approach is you might see a lot of clipping or popping where buildings in the distance seem to 'magically appear' // 'pop into view' (See GTAIV on 360/ps3) and high CPU Usage.

The upside? You can run your game on machines with little memory so Microsoft can save themselves $3.00 on each xbox 360 sold. Its hiliarious to think about how much 'more expensive' it wouldn't really have been to have had Microsoft replace the 256mb of cpu memory with 512mb or even 1GB. Considering today, a 1GB memory chip can be picked up for about $9.00 and PC gaming would be far less hindered by consoles, console games would look better and possibly have more depth, etc.
 
lulz http://blogs.msdn.com/b/directx/p/directx12.aspx
https://twitter.com/DirectX12

DirectX 12 ‏@DirectX12 4h
Rumors of our demise have been greatly exaggerated... #DirectX12 is coming to #GDC http://aka.ms/directx12

MS will have something new about DX12 in about 2 weeks (3/20) at GDC. GDC session summary: http://schedule.gdconf.com/session-id/828184

However, you asked us to do more. You asked us to bring you even closer to the metal and to do so on an unparalleled assortment of hardware. You also asked us for better tools so that you can squeeze every last drop of performance out of your PC, tablet, phone and console.

Come learn our plans to deliver.

AMD goanbmad.
 
Er, no. DX had all the legacy shit stripped out in DX10 and OGL was left playing catch up. There's a million other variables too. Yes, OGL used to have 'cheaper' draw calls than DX9, but at the cost of maintaining backwards compatibility, which MS made a clean break with, they suffered. Not that draw call cost is the end / all of performance, like driver implementation, etc etc.

OpenGL has never had to play catchup unless you are going only by the base features which no one limits themselves to. OpenGL's extensions mechanism means that it often supports features that Direct3D either hasn't yet or won't.

No, all that shit is depreciated and gone for a long time. DirectDraw is depreciated, DirectSound is depreciated, DirectInput is depreciated, DirectPlay is depreciated, everything old and now useless is depreciated. Physics will likely never be implemented.

Deprecating DirectSound was the stupidest thing Microsoft ever did (that and the Vista audio stack). PC sound has *regressed* since we are now stuck with primitive surround sound on most games rather than true 3D spatial positioning.
 
Back
Top