Recommended Posts

 

"Innovative" has always been an overused buzzword in the video game industry, to the point where the term has lost all meaning. Lately however, gamers have become fond of using innovation ? or the lack thereof ? as a convenient excuse to condemn series and genres they simply don't like.

 

Scroll through the comments on a story discussing virtually any popular franchise or sequel, and inevitably someone will cite the absence of innovation as a reason for hating it. Usually, this argument is presented as being incontrovertible, a self-evident assertion of the game's lack of value. As far as pointless Internet arguments go, it's pretty effective and damning ? unless you actually stop and think about it for more than five seconds.

 

Part of the problem is that the word "innovative" is so overused and misunderstood that it has no meaning. In the most basic sense, describing something as innovative simply means that it contains new ideas ? something that is true of most games to at least some degree. However, for most people innovative means much more. We consider a game innovative when it does something clever, something we haven't seen before, something groundbreaking. By straying from the dictionary definition, "innovative" already has a nebulous and mystical quality to it ? a perfect descriptor for people who want something new but don't know precisely what that new thing should be.

 

There's nothing wrong with being uninterested in a game series, but we should be honest about our reasons for disliking them. New ideas are being explored in every genre ? yes, even in first-person shooters ? and iterative refinement is an equally important (albeit less sexy) aspect of the industry. Innovation isn't a problem, and the term is so abused and overused that we should strike it from our vocabulary.

 

Full editorial at: GameInformer (gameinformer.com)

 

 

In this editorial its author Jeff Marchiafava talks exclusively in context of video games, because GameInformer is, of course, a resource primarily devoted to video game culture. But the problem, I think, is much more widespread - the whole damn computer industry overuses this buzzword to a cancerous extent. Companies push out products in the proverbial neverending loop of innovation. Consumers attack them for not actually delivering anything of likes and demand actually innovative solutions. Or, well, damn them for trying - you can't win in this business. Stop, drop and troll. Do any of you even remember what "innovation" means? Or is it exactly as described in the quoted editorial - a perfect descriptor of wanting something but not having a single clue what exactly?

Link to comment
https://www.neowin.net/forum/topic/1198971-lack-of-innovation-isnt-a-problem/
Share on other sites

Gee, you're really adding valuable information to the discussion here. Perhaps I should have expected that anything that isn't related to Start Screen bickering, Xbone vs PS4 or race to the bottom of crudphones, but instead aims to identify problems, will be met with no more than vague and cringe-worthy attempts at smartypants. That said, this problem isn't at all specific to Neowin.

I can't visit the site due to the company's proxy, so I just have to go off the excerpt above.

I agree that we don't use "innovation" in its truest sense anymore. However, the article seems to be looking at series that have been long running - Call of Duty springs to mind. Our problem with such series is that while a continuation of the story can be considered innovative in the strictest terms, the consumer feels cheated by having to pay ?50 for something that one could argue could be a ?20 expansion pack.

This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!