You Will Get DirectX 11.2 Only With Windows 8.1
SmartAboutThings writes "Microsoft has just announced the next version of DirectX, 11.2, on its website. But the real 'problem' is that it is going to be exclusive to Windows 8.1 and next generation consoles — Xbox One and Play Station 4. This is not news, as DirectX 11.1 was exclusive to Windows 7 & 8. But is this going to help Microsoft convince people to ugprade or will make them angry?"
Increment updates do not justify an upgrade...especially to a downgrade such as win8
Direct X is for games. And people who want to play their games will give up all sorts of important things in order to play them.
Recently, the always-online and amazingly intrusive Microsoft eye have caused Microsoft to back off on some things and that's encouraging, but the behavior is obvious and Microsoft wouldn't try it if they didn't think they could get away with it.
"Oh, I hate Windows 8...I'll never use that... oh? What's that? The next release of my favorite game? Only on Windows 8? I hate Windows 8... oh well... Windows 8 'just so I can play my game.'"
Where does it say the PS4 is getting it? I saw no mention of that.
DX 10 being limited to Vista and newer kept it from being used for a long time, I guess the same will happen to DX11.1 and 11.2. Game companies won't make games that don't run on an OS the majority of the players use (Windows 7).
"...is going to be exclusive to Windows 8.1 and next generation consoles — Xbox One and Play Station 4." When did Microsoft start developing for Playstation 4?
What? Where did that come from?
Undoubtedly it will make the some people angry.
But for anyone that does Windows graphics development and knows something about the underlying system, it's not a big deal. We've known that adding some of these features to Direct3D would require making some changes to the underlying display driver stack (WDDM), which is why D3D 11.2 requires WDDM 1.3 drivers, and WDDM 1.3 requires Windows 8.1. Unless of course you want Microsoft backporting a new version of the display driver stack and breaking your old OSes...
TL;DR: D3D 11.2 requiring Win8.1 can't be helped
So what does DirectX 11.1 and .2 do that's so important that people will abandon Windows 7?
Well, it's true that I don't play a lot of games these days. I spend a lot more time pursuing my goals in life, so I don't have hours and hours to just sit down and immerse myself in all sorts of high end games. I tend to stick to a few that I like and play them from time to time, and DX 11.2 isn't required by any of them, or even the new title(s) that I'm interested in which are still WIP.
Other than that, I spend the vast majority of my time on Linux with KDE 4. Even moreso with Minecraft working on multiple platforms due to Java. The only new title I'm currently interested in is Planetary Annihilation, which if I recall correctly, will support a Linux port. So I guess my care-o-meter about this announcement is somewhere around zero.
I will say this, though. The user interface style that was developed, with a task bar and normal start-menu (not this metro start screen crap) was developed and refined over a period of 20+ years or so now. It's available across many operating systems and kernels. It's there because it works rather well. If you ask me, this touch-centric crap that Microsoft is pushing isn't much good beyond tablets and phones, where your primary mode of interface is your finger on a screen.
So, tablets and phones came along and a new interface style was designed that worked better with almost-exclusively touch-screen interface devices... Then Microsoft decided that *everything* should use this interface. I'm not interested in relearning how to use my Desktop's or Laptop's interfaces. Screw Windows 8. If I found a part of my computer's user interface to be highly inefficient, requiring a redesign to solve the problem, I'd be very aware of it. I hate wasting time. But the stuff before Metro in most cases doesn't give me that impression. Metro does.
So there's my possibly subjective rant. But hey, the article asked.
My new high-end HP running Win 7-64 with 32GB RAM takes 5 minutes to boot...
Don't blame Windows for that.
rewriting history since 2109
My new high-end HP running Win 7-64 with 32GB RAM takes 5 minutes to boot..
I know that HP sometimes make it hard to find the power button on their PC, but that is a bit ridiculous.
If you're running control software similar to what I'm running, it's the cause. My computer went from incredible fast to really slow when I installed my plc and hmi development tools.
...that doesn't want to upgrade to 8.1? It's a free upgrade and, as far as I'm aware, doesn't make any changes for the worse. The only thing I can think of is "local searches are sent to Bing," but since that's easily disabled, I can't think of a reason not to upgrade if you're already running on 8.
Give up and look at his posting history. He's a troll that delights in deliberately appearing to be stupid.
DirectX is an API, not a standard. It doesnt even have a spec doc like OpenGL does.
It's amazing how much DX9 stuff we still see.
I imagine that companies that ship DirectX 9-compatible game engines are trying not to exclude some PC owners from their market. These potential customers own PCs with Windows XP, PCs with older video cards that don't support all the new features of DirectX 10 let alone 11, and PCs with no video card at all whose integrated graphics can't easily make use of new DirectX features.
This question has been asked on slashdot with literally every release of Windows that I can remember back to at least 95. Yes, people will complain, no it won't hurt Microsoft's sales. No, people won't stop buying their product because getting a major new feature requires you to upgrade the whole OS. I eagerly await this exact same thread two years from now.
This. Why does every app have to ship their own DirectX runtime libraries? Can't they be included with Windows?
How is the issue handled with OpenGL?