DirectX12

Microsoft is doing things that I can’t complain about

by

I really need to stop sleeping when weird shit happens. I awoke yesterday to find Microsoft actually making somewhat of an attempt to make themselves look good on PC for once… where to start? The first thing I read yesterday was the announcement for the Halo Master Chief Collection coming to PC, and you can purchase it on Steam!

For the first time ever, The Master Chief’s story comes to PC. Featuring Halo: Reach along with Halo: Combat Evolved Anniversary, Halo 2: Anniversary, Halo 3, the Halo 3: ODST Campaign and Halo 4, this is the definitive Halo experience.

Shorter Microsoft: Here’s the deal, we don’t talk about the first Halo release for Vista, and you can get our game collection outside of our shitty store. :zorak:

This came as a bit of a shocker considering Microsoft wanting to push their store onto people, and placing it on Steam also gives people like me a chance to see if it will handle under Proton. :trollface:

Of course that was shocking enough on it’s own, but Microsoft cranks it to 11 when news of DirectX12 coming to Windows 7 via World of Warcraft.

Blizzard added DirectX 12 support for their award-winning World of Warcraft game on Windows 10 in late 2018. This release received a warm welcome from gamers: thanks to DirectX 12 features such as multi-threading, WoW gamers experienced substantial framerate improvement. After seeing such performance wins for their gamers running DirectX 12 on Windows 10, Blizzard wanted to bring wins to their gamers who remain on Windows 7, where DirectX 12 was not available.

On the surface this seems like really extraordinary news, however if you take the time to think about it DirectX12 never really took off quite like how Microsoft wanted it to. When AMD open sourced their Mantle API (now Vulkan) that left Microsoft a little dead in the water as that looked much more attractive to developers. especially when developing on more than one platform. Plus with more people having little reasoning to switch to Windows 10 to take advantage of DX12 apart from maybe a handful of titles that properly utilize it. It is interesting they would do this so close to Windows 7’s end of life cycle… or is this a sign of them continuing to support it? I might have to turn my dualboot system into a triple. :trollface: My only hope is that if they do go back to Windows 7 they don’t do to it what they did with their newer OS’s/

Then to top it all off Microsoft actually did something to make Windows 10… somewhat better?

Occasionally, startup failures can occur due to hardware issues, file corruption, or incompatible 3rd party software.
If Windows detects that your machine cannot start up successfully, it will try to diagnose and resolve failures due to disk issues, system file corruption, invalid registry keys, or other such causes. If all these steps are unsuccessful and your machine is still unable to start up properly, Windows will determine if the startup issue was introduced after recent driver or quality updates were installed. If so, these updates may be uninstalled automatically to get the device back to a workable state. This is only done as a last resort.
This is only available via the Windows Insider updates, but it’s about friggin time they got to work on a update safeguard. In fact all of the items I discussed above should have been rolled out a long time ago. Anyone that is at least half tech savvy could look at all of this and see this was all possible. We have been on pretty much the same kernel since Windows Vista, porting DX12 to Windows 7 should have been just as fine as adding it to Windows 10, and making Halo games console exclusive was always a boneheaded move on Microsoft’s behalf. You already have people using your OS, why not give them a game to play on it that YOUR own company made if they have the hardware to back it up? Not all of us want to buy a console to play exclusives… unless it’s a $10 PS3 or something. :trollface: