Recommended Posts

Yeah, its ugly, simply due to input capabilities, Microsoft showed this when they tested FPS's concerning Controller vs Mouse/Keyboard for either original Xbox or Xbox 360s early days and shut that project down quick, wasn't even a contest.

 

RIP Shadowrun :cry:

But everyone is on the same level of control. Would be different if you had controllers vs K/M.

I wasn`t making a point about this.

Rather that if you cant aim/shoot with a K/M, then why are you better, faster, with a slower input?

Thats more or less like saying, your better with a controller as the people who play on console are essentially worse in general.

Tho again I`d question this as surely the people you play against are skilled relatively to the control scheme they use.

i.e You should be just as good/bad no matter what scheme you use.

I wasn`t making a point about this.

Rather that if you cant aim/shoot with a K/M, then why are you better, faster, with a slower input?

Thats more or less like saying, your better with a controller as the people who play on console are essentially worse in general.

Tho again I`d question this as surely the people you play against are skilled relatively to the control scheme they use.

i.e You should be just as good/bad no matter what scheme you use.

 

I can't tell you why it is, I'm sure there has been studies carried out by someone somewhere :p

 

It's definitely the experience I've witnessed from friends though. Some of them just can't play FPS on K/M but are pretty competent on controller.

 

Personally I game on both so I guess I'm the ambidextrous of the gaming world, but it always takes me a few rounds to get re-adjusted if I haven't played either one for a while.

I was playing a bit last night gunning for someone in an infantry fighting vehicle and I swear he must have been using a controller or something was terribly wrong. He would try shooting another tank just 20 feet in front of us and he would constantly overshoot left or right. Like, he would move the turret to the left or right and start shooting as the turret's moving but he would go to far and only half his "magazine" actually hit the target. If that's how controllers play, I want no part of that :p I want precision control.

In this game, all bullets have an arc and travel time to their target. Some guns have more of both than others. This could easily have happened with someone with KB and mouse. It happens to me a lot, especially when I'm piloting a chopper. I have to see how far my shots are drifting for a moment before I can adjust and hit with every shot.

In this game, all bullets have an arc and travel time to their target. Some guns have more of both than others. This could easily have happened with someone with KB and mouse. It happens to me a lot, especially when I'm piloting a chopper. I have to see how far my shots are drifting for a moment before I can adjust and hit with every shot.

You'll probably have to take my word on what I saw but trust me, this huge tank he was trying to shoot was not 20 feet away. There's no reason he couldn't land his shots. Just watching his turret it seemed like he would keep going left or right passed the target. Now that I think about it again, it could have been lag.

Hello,

Man, this game is horrible. The story is just *snooze*. I was literally waiting for the game to end because the story is not only horrible but you can predict that it is going to be short.

And the ending? Wow. The ending was one of the dullest in more than 5-10 years.

Hello,

Man, this game is horrible. The story is just *snooze*. I was literally waiting for the game to end because the story is not only horrible but you can predict that it is going to be short.

And the ending? Wow. The ending was one of the dullest in more than 5-10 years.

 

Battlefield has never bin about the single player campaign tbh its more in there to learn how the game works if youve never played it before and to show off the engine. Its all about the multiplayer which is AWESOME, CoD multi is snooze battlefield is amazing

 

Oh and yeah ATi's drivers suck hard at least the 9.2 beta ones fix alot of my artifacts/tearing although it does come with an fps drop but i never drop below 47fps in multi so its fine

Hello,

Man, this game is horrible. The story is just *snooze*. I was literally waiting for the game to end because the story is not only horrible but you can predict that it is going to be short.

And the ending? Wow. The ending was one of the dullest in more than 5-10 years.

 

This week's Invisible Walls on GT actually touches on this, although more about CoD than BF4. Basically IW/Treyarch and the rest that work on the series just need to dump single player and focus on reinventing the multiplayer because the stories in these games are completely boring to play and repetitive. There comes a point you can't top what you did in last year's game and you end up copying/pasting. I forget if it's CoD or BF4 but I heard they stole a scene from The Dark Knight Rises and use it in the single player too.

 

Going up against Titanfall & Destiny is going to be hard for these older franchises if they insist on keeping single player. You need to "split" your budget between modes and invest a lot of work hours into something people really just don't care for. Meanwhile Respawn and Bungie are most likely going to redefine FPS on this generation of consoles.

Going up against Titanfall & Destiny is going to be hard for these older franchises if they insist on keeping single player. You need to "split" your budget between modes and invest a lot of work hours into something people really just don't care for. Meanwhile Respawn and Bungie are most likely going to redefine FPS on this generation of consoles.

Remember Brink?  Yeah, me neither ;)

Actually I do & I loved it :p

 

Also can't wait for Extraction. Got my email through about the beta test this week :D

So did I, but I'm just saying ditching SP isn't a magic bullet (or whatever you wish to call it.)  You might not care about it, but a lot of people still do.

So did I, but I'm just saying ditching SP isn't a magic bullet (or whatever you wish to call it.)  You might not care about it, but a lot of people still do.

 

Well I think it's fair to say that the numbers probably buy and stay for multiplayer, but I'm sure MS/Sony/EA/Activision are the only ones who can answer that. The closest we can tell is by achievement/trophy unlock count.

 

Would recommend you all check out the Invis Walls episode though, it's pretty good.

Well I think it's fair to say that the numbers probably buy and stay for multiplayer, but I'm sure only MS/Sony/EA/Activision are the only ones who can answer that. The closest we can tell is by achievement/trophy unlock count.

All I know is if it didn't have SP at all I wouldn't buy it.

All I know is if it didn't have SP at all I wouldn't buy it.

 

I would have agreed with you many years ago, but after CoD4 I gave up on the SP and it wasn't long before I gave up on the MP too.

 

Battlefield has always been about MP for me so I wouldn't miss it.

 

 

I know some get a popcorn action movie thril from it but I was just saying for comparisons sake, they could ditch the SP and focus on MP to evolve it much like the rest of the FPS crowd are doing. Then again, if everyone does it, there's a gap in the market for someone to take advantage of. I doubt anyone wants to see the end of SP stories altogether.

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
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!