Farewell to DirectX?

Don't be dissing 3Dfx too. Glide was extremely power for its time and for a short while, looked FAR prettier than Dx of that time. It was the fault of 3Dfx sitting on their hands keeping Glide and VSA outdated while Dx started taking over. PC gaming as we know it today would never existed if it weren't for 3Dfx.

I think I speak for everyone here who are crazy enough to blow $1k+ on a pair of 580s. I expect my gaming to look so real, so pretty, so real, so real, so real, so real, so real (did I mention "so real"?) that when I play Bad Company 2, a bullet proof vest and mask is required because the bullets are render so real and it flies off the screen at you.
 
I think you guys missed one of his main points. I think he is saying that GPU architecture will become standardized sometime soon (GPGPUs), like with x86 or x86_64 on CPUs. Writing machine code/assembly is the same for an Intel chip or an AMD chip, I think he is saying this will soon be the case with GPUs.

This was an issue that was brought up 3 years ago, when AMD was hinting about Fusion. For PC gaming, it's a good thing, and everyone here is getting it wrong.

A. They don't want to bring back any API, just kill off EVERY API.
B. The idea is that all CPUs in the future will be GPGPU's, like larrabee. Remember larrabee?
C. All code will therefore be universal, just like how it is on CPUs between AMD and Intel machines.

There's a lot of good that can come from this.

#1 NO MORE DRIVERS. You won't need drivers to produce graphics, and therefore won't rely on driver updates. Not to forget, buggy drivers that cause problems with a game you play, but apparently no one else does. Then 5 months later, AMD or Nvidia finally fixes it with a driver update.
#2 NO MORE BUGGY GAMES. DirectX isn't perfect, and as time goes by, older games get issues, unless patched. Since GPGPU's will work like CPU's, then compatibility won't be as big of an issue.
#3 Console like performance, without the console. Like it or not, PC hardware pays a huge performance tax with API's.

THIS CANNOT BE DONE WITH YOUR CURRENT PC HARDWARE! Until AMD and Intel release CPU's with built in GPU's, then it's not something you'll need to worry about. Until AMD releases FUSION chips, and Intel releases Larrabee chips then DirectX is here to stay. What FUSION chip AMD has right now, isn't what I'm talking about. When the graphics core is also the X86 CPU, then you'll know.

Also, Nvidia is fucked. Sorry, they need to start making X86 chips before they get left in the dust.
 
DirectX is the glue that holds PC Graphics/Gaming grounded. The last damn thing we need is to go back to the days of each card manufacturer rolling their own (3DFX, etc...). What a nightmare that would be.

It would all but kill the Gaming market on the PC. There's no way in hell gaming companies would put precious resources into writing specific versions for specific chipsets.

Then again, this may be Microsofts plan to kill PC gaming once and for all to sell more XBOX's.

I'd rather game on my iPad than an XBOX.

Obviously was so outraged he didn't read the article. :rolleyes:
 
The more I read these forums the more I notice the incredible amount of people sick with fanboyism that post nonsense without reading the articles. Jeez!!!
 
The more I read these forums the more I notice the incredible amount of people sick with fanboyism that post nonsense without reading the articles. Jeez!!!

At least Skim the article!

But also, don't forget that DirectX supports more then just the graphics side as has been mentioned before. Granted as time goes by all operations done by LRU (or onboard) devices will be integrated as they start to reach peak or can be added to single dies.

Problem with doing that now or in the near future is physical size, yea larrabee brought a lot of cool things with it (if intel wanted to release it) but it would give us the horse power we wanted. We have to wait till these things start to see little to no improvement, much like memory controllers and HDD controllers did.

Microsoft wont be giving up much in terms of "market place" when losing DX, if anything it could help them as it will relieve one aspect of the software from them, drivers too.
 
What I got out of that is:

We at ATI can't write drivers worth a damn so we'd like to pass that responsibility on to the game developers

What I get from your posts is that you don't know shit about computing and if you do you better go back and ask your teachers to teach you again.
 
I always thought that xbox was programmed using dx... one of the reasons it's so easy for devs to port games between the 2 platforms. My only experience here is some XNA programming so I may not have a clue what I'm talking about.

I think one of the reasons that PC games these days are poorly optimized is because they are made for consoles and then ported to the PC, it used to be the other way around. We end up with games programmed to the lowest common denominator. No doubt there is probably tons of room for optimizations in pc gaming but this guy is taking his case a little too far.
 
I read an article a while back that talked about software rendering, and how developers kinda gave up on it too quickly when discrete graphics cards showed up. It pointed out very good ways that 3D graphics might have actually been better today had the industry explored software rendering further.

I wish I could remember where it was...
 
I always thought that xbox was programmed using dx... one of the reasons it's so easy for devs to port games between the 2 platforms. My only experience here is some XNA programming so I may not have a clue what I'm talking about.

I think one of the reasons that PC games these days are poorly optimized is because they are made for consoles and then ported to the PC, it used to be the other way around. We end up with games programmed to the lowest common denominator. No doubt there is probably tons of room for optimizations in pc gaming but this guy is taking his case a little too far.

Both the PS3 and Xbox350 are supplied with DX9 capable GPU's. You are correct about the porting, it costs a lot of money and a lot of time to port from console specific programming to the PC. The developers don't want to spend a lot of money or miss out on valuable selling time and the gamers are hurt because of this.
 
The best option is to give programmers a choice in how they want to implement. Keep the API, but give a direct to metal route as well. With Direct-X we're stuck with the lowest common denominator. Allow for some customization. In this way you can allow programmers to have a standardized mode that will run on everything, and an optimized mode that will provide better performance, or if the programmers want to go all-out they can code everything to hardware and skip the API completely. Then it's up to them to quality test.

I know fellas like Carmack have said Direct-X is OK, but he was also proceeding from the "60 FPS is enough for everyone" mindeset, and that 30 FPS is playable. I cannot criticize Carmack's programming genius, but I don't accept that method of thinking when it comes to limitations. I want to be able to get the full benefit out of my hardware whenever possible. I don't like the idea that we must settle for someone else's arbitrary standard. Let hardware capability be the deciding factor there, and give the programmers more tools.
 
I always knew a console system was more efficient than a PC but didn't know the difference was that massive. Makes me not want to keep throwing hundreds of dollars at upgrading my PC all the time now that I know I am only getting 1/10th of the performance the same hardware would get on a console.
 
The article may have some valid points,but it can't hide the real reason so few PC games really outshine console versions - because the developers themselves are too greedy to put the time into creating games that take full advantage of the advanced capabilities of today's systems. They simply port the console versions to the PC,versions handicapped by the fact they were created to run on 6 year old hardware. When Crysis was released,it blew away anything on consoles. Crysis 2? The PC version doesn't even use DX11.It's not better than the original PC only game,in fact I'd say it's a step back.Not because DirectX held Crytek back,but their own greed to cash in on quick and easy console route.
 
The best option is to give programmers a choice in how they want to implement. Keep the API, but give a direct to metal route as well. With Direct-X we're stuck with the lowest common denominator. Allow for some customization. In this way you can allow programmers to have a standardized mode that will run on everything, and an optimized mode that will provide better performance, or if the programmers want to go all-out they can code everything to hardware and skip the API completely. Then it's up to them to quality test.

I go with this. Give the choice for console developers. You can go either DX or DTM.

As DX was customised slightly for the 360 and the fact that MS has shown it listens to developers I'm pretty sure that DX will be modified extensively again for the next Xbox.

Limitations are not always a negative. They can help to crystalize and set the route for development. If not you imagine what give the 'creative types' an open playing field and you'll never get anything delivered on time or on budget, if at all.

No APIs for the PC would be carnage.
 
Wait, wait... Let me get this straight.

Game developers who don't give a flying fuck about something so plain and simple as PC exclusive,

developers who are too lazy to be bothered with compiling x86-64 binaries, let alone utilizing or committing to this 8 years old instruction set created by, yes you guessed it right - AMD!

not to mention games featuring 2006. born DirectX 10 are still more an exception then a rule,

And then this Elmer Fudd guy comes by with a brilliant idea of killing common API,

and suggesting that these same lazy developers should program "directly into metal" therefore increasing the numbers of architectures, developing time, difficulty and required expertize by a factor 10.

[size=+3]From what planet did AMD pick up this marketing guy?[/size]
 
Wait, wait... Let me get this straight.

Game developers who don't give a flying fuck about something so plain and simple as PC exclusive,

developers who are too lazy to be bothered with compiling x86-64 binaries, let alone utilizing or committing to this 8 years old instruction set created by, yes you guessed it right - AMD!

not to mention games featuring 2006. born DirectX 10 are still more an exception then a rule,

And then this Elmer Fudd guy comes by with a brilliant idea of killing common API,

and suggesting that these same lazy developers should program "directly into metal" therefore increasing the numbers of architectures, developing time, difficulty and required expertize by a factor 10.

[size=+3]From what planet did AMD pick up this marketing guy?[/size]

Probably because they are so bad at writing drivers their solution is to kill the need for a driver. As an owner of an AMD/ATi card, I can say the drivers are worse than what I have experienced on NV's side. I think it was 10.5's or something that killed half the games in my library, I had to revert back until the newer ones came out.

Lazy/shitty developers = no one wins.
 
You watch, someone will come up with the idea of developing a gaming-specific OS...

Technically, MS did do just that for the 360 (and even the original Xbox. It's just a gutted down version of the the Windows kernel with enough added on to know how to handle the other devices it uses.

Could it be done on the PC side? If someone wanted to, and took the time to do it right. Stripping out unneeded Windows features to gear it towards gaming might not be so bad, if that's what your primary use of your PC would be for.
 
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.
 
I always knew a console system was more efficient than a PC but didn't know the difference was that massive. Makes me not want to keep throwing hundreds of dollars at upgrading my PC all the time now that I know I am only getting 1/10th of the performance the same hardware would get on a console.

This doesn't matter when the PC is hundreds of times faster then console. The PC still ends up faster. Also, developers have to make a huge trade off, to gain that speed advantage. The Xbox 360 does support DirectX graphics, and does take a performance penalty for using it, just like on the PC. Unless they program "direct to metal" then consoles suffer in performance as well. Though, "direct to metal" usually means your games are now difficult to port over to other platforms, like PS3 and PC.

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.
 
I'm speaking for a person who don't know shit about programming. We keep looking at this in a "either or" situation. Developers can/should have the option to go both API and metal route (just like when 3Dfx was dominant), if they choose invest the time and money (and I wish they do). And I am only talking about graphically/physics intense and complicated games like BC2, Crysis series, MMOFPS games; not starcraft2 or WoW or Sims. I mean games that as the potential to look so real, it makes you flinch.
 
D3D used to be horrible in the late 90's. It was so damn slow. OpenGL was faster.
 
I think on the whole PC gaming has benefited more from APIs such as DirectX than has been held back.

Things would be a total mess otherwise.

Suddenly ditching it and going all 'off-piste' would be a disaster.

However, with consoles a more open approach may well be a benefit as you have totally controlled hardware.
 
DirectX SAVED the PC game industry. However, he's right in a sense that here we are in a DirectX11 world & developers are STILL making DirectX9 games. Hell, there's not a lot of DirectX10 games and THAT technology has been out 2 years ago. THIS is not Microsoft's fault...but the fault of LAZY developers.

Or SMART developers realising that they could kiss 50% of their sales goodbye if they:

1) Go DX10 or higher only

2) Make the game too complex that only the latest high-end graphics cards can play them (after all, there are scores of DX9 only cards and setups out there that are still monster performers)

3) Shut out their WinXP/Wine customers.

Not everyone can afford to upgrade as soon as a new spec comes out. Why should I give up a DX9 card here that outperforms a $150 DX11 part?
 
Or SMART developers realising that they could kiss 50% of their sales goodbye if they:

1) Go DX10 or higher only

2) Make the game too complex that only the latest high-end graphics cards can play them (after all, there are scores of DX9 only cards and setups out there that are still monster performers)

3) Shut out their WinXP/Wine customers.

Not everyone can afford to upgrade as soon as a new spec comes out. Why should I give up a DX9 card here that outperforms a $150 DX11 part?

#1 is simply not true. DX11 did just the opposite.. it unifies all DX9/DX10/DX10.1/DX11 hardware under the DX11 API by decoupling the hardware requirements for DX11 specific features from the other advantages of DX11, like CPU efficiencies.

So you can run DX11, but just before using a DX11 feature, you have to know the "feature level" of the hardware. If you were going to do tessellation, you'd realize at that point you couldn't, and do something else instead, based on the hardware capabilities.

Now even your ancient DX9 level hardware can run DX11, on Vista and Win7, and get all the non-hardware-feature-dependent advantages (APIs that are more efficient CPU-side).
 
This guy is pretty much out of his mind.

Yes, everything would run faster if GPUs just had an instruction set and your compiler generated native GPU opcodes/operands to run on the bare metal. What doesn't seem to be mentioned is that, unlike CPUs, every single GPU has a radically different architecture, and that architecture changes at least once every 2 or so years. What this will result in is every single game having to ship with executables cross-compiled to every single GPU architecture the developer wants to support. Can you say "support nightmare?" Imagine instead of having Crysis.exe and Crysis64.exe, you have:

CrysisGF100x86.exe
CrysisGF100x64.exe
CrysisG92x86.exe
CrysisG92x64.exe
CrysisG80x86.exe
CrysisG80x64.exe
CrysisG73x86.exe
CrysisG73x64.exe
CrysisR500x86.exe
CrysisR500x64.exe
CrysisR600x86.exe
CrysisR600x64.exe
CrysisR700x86.exe
CrysisR700x64.exe

Fun, isn't it?

AMD still can't write something as drop-dead simple as drivers, and yet they think they're just going to snap their fingers and whip out a compiler for every GPU architecture they've ever made? Compilers are something that takes years to write, not weeks.

Keep dreaming guys, you can get right on writing all those compilers as soon as you launch your nonexistent Bulldozer.
 
Someone correct me if I'm wrong but I thought OpenGL is/was "better" than DirectX but seeing as how Microsoft backs DirectX, that's why it took off?
 
OpenGL is better. Microsoft decided a while back they wanted everything to be pushed through Direct-X in Windows Vista and beyond. Since they write the OS they can get away with it. It's another example of Microsoft wanting everyone to do things their way.
 
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.
 
They don't care if DirectX runs slower as they have the 360.

I'd say false on that, just due to the fact that their game systems use DirectX (and I would assume that they will continue to do so for their future systems).
 
OpenGL is better. Microsoft decided a while back they wanted everything to be pushed through Direct-X in Windows Vista and beyond. Since they write the OS they can get away with it. It's another example of Microsoft wanting everyone to do things their way.

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.
 
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.

Who in here remembers the game Barbarian?

http://dosgamer.com/barbarian/

Right after the Conan movie came out.

Those fuckers made the PC speaker talk the word Barbarian. I thought that was the coolest thing I've ever heard.
 
This doesn't matter when the PC is hundreds of times faster then console. The PC still ends up faster. Also, developers have to make a huge trade off, to gain that speed advantage. The Xbox 360 does support DirectX graphics, and does take a performance penalty for using it, just like on the PC. Unless they program "direct to metal" then consoles suffer in performance as well. Though, "direct to metal" usually means your games are now difficult to port over to other platforms, like PS3 and PC.

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.

And I'm guessing those Direct to Metal games are the ones that Marketing so proudly announces as Console Exclusive. I think the best example would be:

Uncharted.

I remember how they gloated about the PS3 great power.
 
Imagine if (when) this happens, the whole integrated/unified GPU/CPU thing. Imagine when there is no DirectX overhead and when graphical rendering becomes a unified standard like the assembly language that works the same on AMD and Intel CPU's...

...and then imagine what that will mean for people who like to gloat about the fact that Macs can't play games. Once there is a unified system, Macs will be just as game-capable as any PC :eek:

It will be straaaaaaaaange times, indeed :p
 
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.
 
It's certainly been interesting seeing that due to the severe limitations of the PS3 GPU that developers have tended to go around it and use the Cell for more and more graphic effects. Effectively doing a big chunk of it in software.

I'm wondering if the next generation of consoles could do away with a GPU (yes controversial I know and unlikely to happen) and just pack in enough raw CPU hp to do all the effects in software so the sky is the limit. Maybe just have a supplementary tesselation unit.

Only really has to do up to 1920x1080 after all.
 
It is of course only in some people's mind that if you can create something 10 times faster that the game would benefit from it.

These things are called optimization it is done already, done to death on consoles.

There is no golden rule for games to actually get better a good example is the latest lackluster console-> pc ports.

The problem lies in that AMD can't support software standards on their own, look at what happened to 3Dnow!.

Now if AMD would be able to get rid of the DX API then they would have to invest in something called open source because the development of a direct approach to the hardware must have an evolving lcycle , if AMD had the people for these kinds of projects then they would already have such implemented.

And this has to be used by games even. The market wont pick this up, nor will AMD. There is no reason for it. The games won't improve the developers won't put time into learning another "API" because they get their money this way already.
 
DirectX is the glue that holds PC Graphics/Gaming grounded. The last damn thing we need is to go back to the days of each card manufacturer rolling their own (3DFX, etc...). What a nightmare that would be.

It would all but kill the Gaming market on the PC. There's no way in hell gaming companies would put precious resources into writing specific versions for specific chipsets.

Then again, this may be Microsofts plan to kill PC gaming once and for all to sell more XBOX's.

I'd rather game on my iPad than an XBOX.

no its junk middleware that enabled Microsoft to run the market like they want it. Dx is more of a market strategy to sell a Os and gpus.

Correct me if I'm wrong but didn't nvidia kept on rambling about gpus that can do the same thing a cpu can do but only faster. Then the ramblings that each shader is actually like a cpu core. It can do anything if you programmed it to do so.
That was before dx 11 gpus.

Now dx for vista users. Dx update voila dx 11. Upgraded via software. Now what has made dx 10 gpus incapable of performing instructions anymore from the api? Its like saying a dual core can't run on windows 7
 
Back
Top