Recommended Posts

Aaaand no comment on the most critical component, Windows 7 support. Weak performance from Microsoft as per usual.

 

Even if they've got 1:1 support for D3D12 on D3D11 class hardware, limiting themselves to Windows >=8 only gives them 20% share at best. Less if they make 8.1 mandatory for support on 8.x.

For one most gamers are already on windows 8 because it performs much better than windows 7 game wise and second  a lot more people will move to 8 once directx12 comes out.  Just because windows 7 has a larger share doesnt mean they have that many more gamers.  Probably 90% of that share is buisiness. 

 

I hated metro at first but switched because its just better for game play for me.  After being on it for half a year now i cant stand going back to windows 7 lol

With games coming out for DX12 in the 2015 holiday season, spending resources on a Win7 version makes little point. Windows 9 should be out by then. And with XBOX ONE getting DX12 it pretty much means every game will at least have a DX12 mode as well.

What does this mean? It means that gamers can chose to play in DX Something inferior on Win7 OR they can play with better graphics and performance by upgrading to windows 8.1, 9 or newer.

Basically there's no reason for them to make a windows 7 version and every reason not to. Gamers will follow the performance, which means they will upgrade.

Gamers are probably waiting for Windows 9 anyways and that could be a factor why DX12 is nearly a year and a half from launch. They're probably putting their money in a successful Windows 9 launch that (hopefully) satisifies all Metro and lack of start menu haters. :p

For one most gamers are already on windows 8 because it performs much better than windows 7 game wise and second  a lot more people will move to 8 once directx12 comes out.  Just because windows 7 has a larger share doesnt mean they have that many more gamers.  Probably 90% of that share is buisiness. 

 

I hated metro at first but switched because its just better for game play for me.  After being on it for half a year now i cant stand going back to windows 7 lol

 

Windows 7 has 62% share, Windows 8.0 and 8.1 combined has 20% according to the Steam survey. So no, most gamers are on Windows 7, and DirectX 12 is not going to change that, as DirectX 10 has demonstrated in the past.

  • Like 1

For one most gamers are already on windows 8 because it performs much better than windows 7 game wise and second  a lot more people will move to 8 once directx12 comes out.  Just because windows 7 has a larger share doesnt mean they have that many more gamers.  Probably 90% of that share is buisiness. 

 

I hated metro at first but switched because its just better for game play for me.  After being on it for half a year now i cant stand going back to windows 7 lol

 

Lol no. There's FAR more people gaming on 7 than 8. Just look at the steam hardware survey. And i doubt a ton more gamers will be flocking to a new version of windows until microsoft makes one that isn't a massive step backwards for desktop usage.

  • Like 2

Wait for Windows 9 then, it'll probably correct the 'mistakes' made with Windows 8.x. As for the performance between Windows 7 and 8.x in games, it's known there's a performance increase on Windows 8.x, abeit how small the performance increase may be.

 

Basically wait and see. But don't be surprised if they don't develop DX12 for Windows 7.

Let's jot make this a windows 8 desktop discussion. Meanwhile I can game, run desktop apps and photoshop and 3ds max on my windows 8 as or more efficiently as on 7.

As I said, with the XO getting DX12 it will make all PC games have a far more efficient and better looking DX12 mode. Only on windows 8 and up. this will bring gamers to windows 8 and up

MS seemed to hint at the end of this that they are at least considering support for Windows 7.

 

I know it may sound silly to some here, but if MS can make that happen without causing them too much trouble, I think it would be a great thing to do at least from a pr point of view.

 

 

Some here are quite jaded with anything MS does, but if MS was able to do this and show that they can do something unexpected, maybe some of those that are so dead set against MS would come around a bit.

^ I dunno about that. Didn't that backfire with XP for years and years?

Not since the 360 didn't have DX 10 so neither did their dev tools at the time allow you to make the game for both platforms with a single click.

And that's just the tip of the iceberg why there's no comparable situation between the two.

They never managed to push developers over on DX10+ until recently. Now they practically don't have a choice. There's also a much bigger performance gap with DX12.

MS seemed to hint at the end of this that they are at least considering support for Windows 7.

 

I'm pretty sure they just didn't want to say no. They might keep it on hold to see how the situation develops. But, even then a windows 7 versions seems at this point to not even have been worked on, and it requires a lot more work as well. So it'll be at the very least a year behind, meaning it might as well not exist.

Not since the 360 didn't have DX 10 so neither did their dev tools at the time allow you to make the game for both platforms with a single click.

Their dev tools have never allowed you to target different versions of dx with a single click because of API and feature-set changes. So it wouldn't have happened even if the 360 had supported dx10.

Their dev tools have never allowed you to target different versions of dx with a single click because of API and feature-set changes. So it wouldn't have happened even if the 360 had supported dx10.

 

Their dev tools have allowed you to compile the same game for multiple platforms. I never said anythign about different version of DX. that was kind of the point. one click and they compile the game for DX12 Xbox One and DX12 PC in one go. 

^ I dunno about that. Didn't that backfire with XP for years and years?

 

It had little to do with DX and more to do with developers slow to move off of it.  Add to the fact that most PC games based on console ports tended to use DX9 since most of the Xbox 360s API was DX9 with a little DX10 on top.   People shouldn't underestimate the impact console versions of games have on their PC counterparts regardless of what version of DX you have installed.

 

Also, Windows 9 should turn out to be what the desktop purists want, add in a cheap price to upgrade and I don't see why you'd justify sticking to Windows 7.

Their dev tools have allowed you to compile the same game for multiple platforms. I never said anythign about different version of DX. that was kind of the point. one click and they compile the game for DX12 Xbox One and DX12 PC in one go. 

Switching gears like that is confusing since my post was about XP (and dx9) versus post-XP (and dx10) and how MS didn't see people jumping ship from dx9 because it didn't work on the platforms where gamers were (XP or 360). In any case, even if the 360 had had dx10 support, PC developers would largely have continued to target dx9 because developers target where the users are, not the other way around.

 

For multi-platform developers it seems a little muddier to me. Development efforts are never really a single click even if you setup the tool-chain to cross compile for all of the major platforms. Not bothering to selectively optimize for the platform generally leads to poor performance. Examples of that are numerous in the previous generations even for games that were cross platform between MS consoles and PC (for example: RE4, Beyond good and evil). A scenario with dx10 support for 360 would have led to development effort where you either chose to homogenize and support dx9 only for your PC builds or maintained two separate dx9 and dx10 builds. I'm sure there would have been some developers who would go the latter path, but I still don't think it would have been common considering that game developers have limited resources, in those years post-XP had a little user-base and shotty hardware support for the longest time, and targeting separate PC XP and PC post-XP builds just adds more work into the mix. What are the incentives or developers to do the separate build in those cases? Seems to me it would have been a poor choice of resources at the time.

 

EDIT: actually, I think the confusion was only my fault. I was much too vague in my own post. So I don't think the switching gears part makes sense anymore :-p

 

 

It had little to do with DX and more to do with developers slow to move off of it.  Add to the fact that most PC games based on console ports tended to use DX9 since most of the Xbox 360s API was DX9 with a little DX10 on top.   People shouldn't underestimate the impact console versions of games have on their PC counterparts regardless of what version of DX you have installed.

 

Also, Windows 9 should turn out to be what the desktop purists want, add in a cheap price to upgrade and I don't see why you'd justify sticking to Windows 7.

Developers are slow for a reason -- lack of dx10 support on the platforms where users are is a good reason for them to be slow. I make an argument above (in this post) for how I think it would have played out if the 360 had DX10 support. I personally don't feel it would have been much different because at the end of the day, developers would have targeted dx9 on PC regardless since most PC gamers were there, and there really wasn't a good incentive at the time for them putting effort into developing an additional dx10 version for PC given the lack of users.

 

I would say if users migrate to Win9, there's no good reason for developers to not target dx12. I think It's a bit too speculative at this point though.

Switching gears like that is confusing since my post was about XP (and dx9) versus post-XP (and dx10) and how MS didn't see people jumping ship from dx9 because it didn't work on the platforms where gamers were (XP or 360). In any case, even if the 360 had had dx10 support, PC developers would largely have continued to target dx9 because developers target where the users are, not the other way around.

 

For multi-platform developers it seems a little muddier to me. Development efforts are never really a single click even if you setup the tool-chain to cross compile for all of the major platforms. Not bothering to selectively optimize for the platform generally leads to poor performance. Examples of that are numerous in the previous generations even for games that were cross platform between MS consoles and PC (for example: RE4, Beyond good and evil). A scenario with dx10 support for 360 would have led to development effort where you either chose to homogenize and support dx9 only for your PC builds or maintained two separate dx9 and dx10 builds. I'm sure there would have been some developers who would go the latter path, but I still don't think it would have been common considering that game developers have limited resources, in those years post-XP had a little user-base and shotty hardware support for the longest time, and targeting separate PC XP and PC post-XP builds just adds more work into the mix. What are the incentives or developers to do the separate build in those cases? Seems to me it would have been a poor choice of resources at the time.

 

EDIT: actually, I think the confusion was only my fault. I was much too vague in my own post. So I don't think the switching gears part makes sense anymore :-p

 

 

Developers are slow for a reason -- lack of dx10 support on the platforms where users are is a good reason for them to be slow. I make an argument above (in this post) for how I think it would have played out if the 360 had DX10 support. I personally don't feel it would have been much different because at the end of the day, developers would have targeted dx9 on PC regardless since most PC gamers were there, and there really wasn't a good incentive at the time for them putting effort into developing an additional dx10 version for PC given the lack of users.

 

I would say if users migrate to Win9, there's no good reason for developers to not target dx12. I think It's a bit too speculative at this point though.

 

 

There's always a delay on users shifting to a new system, but regardless, to take full advantage of a new version of DX you'd need a new GPU, odds are that the people who would bother to upgrade the video card to stay up to date are also the ones who would upgrade their OS to the newest version.   Or when you buy a new PC in general you're upgrading both.  DX10 at the start wasn't what MS fully intended it to be, really DX11 is what DX10 should've been from what I remember.  NVidia had a hand to plan in this as well, MS changed some things in DX10 around the spec to help NVidia out while at the time ATi was ready and fully supported it like it was meant to be.  It's also why, iirc, ATi/AMD was the first to have DX11 cards out while NVidia lagged behind a bit. 

 

After it's all said and done, I don't see the lack of Windows 7 support as a negative, specially not if Windows 9 shapes up to be how people expect.  Even those who where on the fence with Windows 8 seem to like it now with 8.1U1 and the changes it brought.    The big thing in all this is the fact that DX12 will for the first time have a wider reach compared to before, hardware is a given, while current DX11 cards might not get 100% of the features,  even the performance advantages makes it worth it.  There's also the XB1 factor and mobile now to, as they said, with DX12 on XB1, PC and WP it makes the porting process easier/quicker and so on.  With the right tools/SDK and so on even with no Windows 7 the adaption rate for DX12 will be higher than before, once it's on the XB1 it'll be used regardless for one thing, and with mobile there's also another area were it'll be used to, porting between XB1 and WP8.1 for example or WP9, whatever version ends up with it. 

 

That's not to say they won't do a version for Windows 7, but if they do it'll come after all the rest, at best we're talking 2H15 or early into 2016.  By then who knows what could happen?

  • Like 1
This topic is now closed to further replies.
  • Posts

    • Onkyo Dolby Atmos AV receivers are really solid deals by Sayan Sen Recently we covered great deals on several soundbar models from the likes of Sony, JBL, Samsung and others for really good prices (the lowest in several months). Aside from that we also reported on the Edifier S3000MKII, a hi-fi two-way bookshelf monitor that's available for only $800. Today we bring a list of AV receivers from Onkyo that are available at great prices including the Onkyo NR7100, RZ30, and 8470 (purchase links under the specs table down below). The Onkyo TX-NR7100 and Onkyo TX-RZ30 are both 9.2-channel AV receivers designed for immersive home theater setups but they occupy slightly different tiers within Onkyo’s lineup with the RZ30 positioned as the more advanced model. The TX-NR7100 is a THX Certified 9.2-channel receiver offering up to 100 W per channel (8 ohms, 2 channels driven). It supports Dolby Atmos, DTS:X, and IMAX Enhanced formats, with flexible configurations such as 5.1.4 or 7.1.2 speaker layouts. A key highlight is its built-in Dirac Live Room Correction which should help optimize sound based on your room and its acoustics. In comparison, both models share several core capabilities though the RZ30 is geared toward enthusiasts seeking more precise calibration and system flexibility, while the NR7100 is positioned as a slightly more accessible, value-focused option with strong all-round performance. The technical specs of the RZ30 and NR7100 9.2 AVRs are given in the table below: Specification Onkyo TX-RZ30 Onkyo TX-NR7100 Power Output (FTC, 2ch driven) ~100 W/ch (8Ω, 20Hz–20kHz, 0.08% THD) 100 W/ch (8Ω, 20Hz–20kHz, 0.08% THD) Dynamic / Peak Power 9 × 170 W (6Ω, 1kHz, 1% THD, 1ch driven) 220 W/ch (6Ω, 1kHz, 10% THD, 1ch driven) Frequency Response 5 Hz – 100 kHz (+1/-3 dB) 10 Hz – 100 kHz (+1/-3 dB) THD 0.08% 0.08% Room Correction Dirac Live (full bandwidth) Dirac Live (with AccuReflex support) Immersive Audio Dolby Atmos, DTS:X, IMAX Enhanced Dolby Atmos, DTS:X, IMAX Enhanced Speaker Layout Support Up to 7.2.2 / 5.2.4 / 9.2 processing Up to 7.2.4 / 5.2.4 / 9.2 processing HDMI Inputs / Outputs 6 inputs / 2 outputs (eARC) 6 inputs / 2 outputs (Main + Sub/Zone 2) HDMI 2.1 Support 8K/60, 4K/120, VRR, ALLM, QFT, DSC, eARC 8K/60, 4K/120, VRR, ALLM, QFT, DSC, eARC Video Formats HDR10+, Dolby Vision, HDCP 2.3 HDR10+, Dolby Vision, HDCP 2.3 Streaming / Network Wi-Fi, AirPlay 2, Chromecast, Bluetooth, DTS Play-Fi Wi-Fi, AirPlay 2, Chromecast, Bluetooth, DTS Play-Fi Get them at the links below: Onkyo TX-RZ30 9.2-Channel AV Receiver: $797.00 (Sold and shipped by Electronic Expo) Onkyo TX-NR7100 9.2-Channel AV Receiver: $699.00 (Sold and shipped by Adorma) Onkyo TX-8470 2 Ch Stereo Receiver: $449.00 (Sold and Shipped by Adorma) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links or authorized dealer links (at the time of article publishing); ensure that you purchase from such links only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • A different thing with Russia. When you say is it better, depends on things. It is better that we don't have the E.U making rules and laws that have nothing to do with them. Is the trading part better? No, that is really mucked up, but then we knew that was going to happen and we would have make agreements, like we do with other parts of the world. Freedom of movement is certainly better, but could be improved, we still need more control over our borders. do you live in the U.K?
    • So what am I quoting from them? I never listened to what Farage or his cronies said. I wanted the U.K to leave the E.u years before the referendum and it had nothing to do with Farage and his cronies. So what country do you live in? Did we work much better together? We were always at logger heads with the E.U because we disagreed with them so much. Maggie was always on at them. I would have thought the E.U was glad to get rid of us as we stopped the integration or made it a two tier. Now without us they can integrate more. I would not have voted out if it was just a trading block and we can still work together on somethings.
    • MPC-BE 1.9.0 by Razvan Serea Media Player Classic - BE is a free and open source audio and video player for Windows. Media Player Classic - BE is based on the original "Media Player Classic" project (Gabest) and "Media Player Classic Home Cinema" project (Casimir666), contains additional features and bug fixes. The BE mod (Black Edition Mod) is a skinned version of Media Player Classic Home Cinema, much better looking than the plain old MPC. MPC-BE 1.9.0 changelog: Splitters Fixed crashes in some situations. AudioSplitter Added support for the RF64 format. Fixed reading of channel layout for some WavPack files. Added support for ID3 tags for Wave64 files. Unknown Wave64 chunks are now ignored. AviSplitter Added support for 'y408' video. Improved support for 'HEVC' video. FLVSplitter Added support for VVC video. MP4Splitter Improved handling of corrupted files. MatroskaSplitter Expanded support for V_UNCOMPRESSED video codecs. Fixed support for frame rotation (ProjectionPoseRoll). Improved support for "V_MS/VFW/FOURCC / HEVC". MpcDvdVideoDecoder Fixed conversion to YUY2. Fixed display of menus for some DVD-Videos. RoQVideoDecoder Output in NV12 and YV12 formats is allowed. Full range is used. MPC Video Decoder RGB32 format will be output as a top-down bitmap by default. Added support for the "IID_MediaSideDataDOVIMetadataV2" interface. Removed support for the deprecated "IID_MediaSideDataDOVIMetadata" interface. Fixed retrieving the name of the video adapter when using NVDEC. Fixed crashes in some situations. MPC Video Converter Added support for AYUV video format. MpcAudioRenderer Improved input format validation. Optimized retrieval of supported formats for exclusive mode. Added the "Keep audio device active when paused" setting. Fixed crashes and freezes in various situations. Subtitles Added the ability to open the properties of an external subtitle renderer in the "Subtitles" settings panel. Fixed external subtitle connections for VSFilter. Fixed a crash when rendering PGS/SUP subtitles when using AVX2. YouTube Improved support for yt-dlp. The built-in YouTube parser is no longer used. Player The HTTP read strategy has been changed. If the playlist contains one entry, more key combinations can be used to control the player (jump through chapters, adjust volume). Improved support for reading ASX playlists. The translation of the MediaInfo report for Chinese, Korean and Japanese has been removed. Added blocking of 32-bit filter "PICVideo Lossless JPEG Decompressor" (pvljpg20.dll), because it crashes. Added blocking of the system filter "AVI Decompressor", which will eliminate the crash of VFW codecs. Fixed a rare crash when using the "/slave" key. Fixed a crash when getting a list of fonts for OSD. Added the ability to load an external audio file using hotkeys. Fixed opening a network path starting with \?\UNC. The "Determine duration when adding" playlist setting now works for YouTube video URLs. The "Online media services" settings panel has been redesigned. Added a "Merge files using FFmpeg" option to the file saving dialog. This option is activated when playing multiple streams obtained using yt-dlp. Added loading of local .dpl playlists ("DAUMPLAYLIST"). Fixed a hang when the user closes the player during the URL opening process. Various interface fixes. Installer Updated MPC Video Renderer 0.10.5. Updated MPC Script Source 0.2.17. Added MPC Image Source 0.3.6. Translations Updated Japanese translation (by tsubasanouta). Updated Chinese (Traditional) and Dutch translation (by beter). Updated Romanian translation (by Andrei Miloiu). Updated Hungarian translation (by mickey). Updated Turkish translation (by cmhrky). Updated German translation (by Klaus1189). Updated Chinese (Simplified) translation (by wushantao). Updated Italian translation (by mapi68). Updated Korean translation (by Hackjjang). Updated Chinese (Traditional) (by udfbe). Updated libraries dav1d 1.5.3-6-g04b69f9; ffmpeg n8.2-dev-1857-g4653e68aab; libpng git-v1.6.55-9-g7d52a8087; Little-CMS git-lcms2.18-26-gf739cda; MediaInfo git-v26.05-38-g702c9b7fd; ZenLib git-v0.4.41-91-g073f297; zlib 1.3.2. Download: MPC-BE 64-bit | Portable MPC-BE 64-bit | ~20.0 MB (Open Source) Download: MPC-BE 32-bit | Portable MPC-BE 32-bit Link: Media Player Classic - BE Home Page Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Apple reportedly looks to blacklisted Chinese memory chips as RAM prices climb by Karthik Mudaliar Image via Apple Apple is reportedly trying to get a clearance from the Trump administration to buy memory from ChangXin Memory Technologies (CXMT) to get some relief from soaring DRAM prices. As per a report by the Financial Times, Apple approached the Commerce Department more than a month ago and also spoke to other officials and allies in Washington. For starters, CXMT is a company that's already been placed on the Pentagon's list of Chinese military companies. The Chinese company is the country's top DRAM maker. For Apple, the timing is certainly awkward but not surprising. Tim Cook had recently warned that Apple would have to raise prices because AI companies are buying up large amounts of memory for data centers, and just like that, Apple raised MacBook and iPad prices. Micron also recently revealed that customers have committed billions of dollars to secure memory supply years in advance, which shows us how aggressive securing infrastructure has become. This gives suppliers such as Samsung, SK Hynix, and Micron more leverage, while pushing hardware makers to look for alternatives. CXMT is one of those alternatives, but not the simplest one. Apple has spent many years trying to diversify parts of its supply chain away from China, especially for final assembly, while still depending heavily on Chinese manufacturing and suppliers. Even domestic brands from China are moving towards CXMT and YMTC instead of relying on Samsung, Micron, and SK Hynix. For Apple, though, it would invite more scrutiny than local Chinese companies. For now, this is more like a lobbying effort rather than a confirmed supply deal. There's no official statement from either of the parties. What is clearer, though, is the pressure behind such a request. AI demand has certainly made hardware a bottleneck, and companies are trying everything they can to bring things back to normal, even if that means making politically sensitive choices. Source: Financial Times
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      491
    2. 2
      +Edouard
      224
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!