Recommended Posts

I really cant see why the m60 is band on the server :wacko: the m60 is as much as a problem as the cg, or 40mm grenade. And to me banning the m60 just says "i cant play the game", i used to see it as a problem but now i don't, just see it as a part of the game, and plus if i happen to be against a team full of m60 medics, i just destroy them with the cg, its even better when they revive each other, get multikills then :)

No, it isn't like that all. These aren't noob server admins. The M60 will be the only weapon that is forbidden.

That's against the EA server ROE - very likely to get their server shut down:

2. RULES AND POLICIES FOR ALL SERVER ADMINISTRATORS MANAGING RANKED SERVERS (PUBLIC OR PRIVATE)

These are rules and policies that all people running ranked servers are expected to observe. Failure to do so can result in the server being delisted.

(...)

2.3.1 Disallowed “In-House” Ranked Server Rules:

Server Administrators may not implement or enforce server rules on ranked servers that prohibit players from using any roles, kits, weapons, vehicles or other features of the game while playing on their server (...)

I don't have a problem with the grenade launcher or Carl Gustav. It's the damn M60. Ever play against a team full of M60 Medics? Worst. Game. Ever. You kill one or two and get mowed down by the rest and watch as the two guys you just killed get revived. If anything, EA/DICE should nerf the M60.

My favorite mode to play in the game is SQDM. You guys are not alone.

probably because we are call of duty players

I don't have a problem with the grenade launcher or Carl Gustav. It's the damn M60. Ever play against a team full of M60 Medics? Worst. Game. Ever. You kill one or two and get mowed down by the rest and watch as the two guys you just killed get revived. If anything, EA/DICE should nerf the M60.

carl gustav is a ****...

and speaking of kits, assault needs an m4, an ak47 or at least more guns to unlock...

hardcore SQDM servers are my fave. love no crosshair too. It's ridiculous how good i am at killing people at stupid far distances with the gernade launcher with no crosshair....

Had some good games tonight, about 20 kills from getting my Platinum Star on the AN-94 Abakan (Y)

The cheater/hackers accusers are out in force it seems now. Had accusations thrown my way twice now, in as many weeks. That sort of gets to me.

1036010401t.jpg

(click to make bigger)

That was one of the idiots, then other being some whiner **** named +muno+. If you see them please t-bag & grab their dog tags for me :D

I don't have a problem with the grenade launcher or Carl Gustav. It's the damn M60. Ever play against a team full of M60 Medics? Worst. Game. Ever. You kill one or two and get mowed down by the rest and watch as the two guys you just killed get revived. If anything, EA/DICE should nerf the M60.

I can't stand getting blown up randomly by those two things :( M60 I can stand because at least I have a chance to do something about it.

Had some good games tonight, about 20 kills from getting my Platinum Star on the AN-94 Abakan (Y)

The cheater/hackers accusers are out in force it seems now. Had accusations thrown my way twice now, in as many weeks. That sort of gets to me.

(click to make bigger)

That was one of the idiots, then other being some whiner **** named +muno+. If you see them please t-bag & grab their dog tags for me :D

Baddies are always jealous when someone can do well not using a well known overpowered weapon. That +muno+ person has twice as many kills with the 40mm gl than anything else, and more time with it than any other weapon as well.

I don't have a problem with the grenade launcher or Carl Gustav. It's the damn M60. Ever play against a team full of M60 Medics? Worst. Game. Ever. You kill one or two and get mowed down by the rest and watch as the two guys you just killed get revived. If anything, EA/DICE should nerf the M60.

Yeah, whenever I notice that a team I'm on is getting steam rolled I always ask in the all chat how many medics are on the other team. The typical response is someone stating that we should stop using cg's or the gl. Fight fire with fire I guess. :sleep:

Anyways, the M60 will be dealt with hopefully early this next week. We can hope! :wacko:

You know you're hated in BC2 when you have a platinum star for the Carl Gustav.

Or the M60whistle.gif

What if I have both :whistle: :p

TBH the constant whining about overpowered weapons that each class has is getting pretty annoying. For me at least. And regarding the M60, I do hope they'll make it less accurate because sniping with it (and shotguns...) is stupid, but weaken as well? Psh, other classes have one-hit-kill weapons...

I kind of lost interest in this a while back, same maps and same crap unfortunately. Looking forward to maybe picking it back up after this break with the new Catalyst drivers which should alleviate my loading issues.

when are the new drivers going to be released?

I kind of lost interest in this a while back, same maps and same crap unfortunately. Looking forward to maybe picking it back up after this break with the new Catalyst drivers which should alleviate my loading issues.

Just play in dx9, with the newest drivers you can force aa in dx9 so its basically as good as dx10.

10.4b didnt fix my dx10 loading times so I switched to dx9 yesterday and forced aa, now I loud in like 10 seconds vs 40.

Just play in dx9, with the newest drivers you can force aa in dx9 so its basically as good as dx10.

10.4b didnt fix my dx10 loading times so I switched to dx9 yesterday and forced aa, now I loud in like 10 seconds vs 40.

Because in DX9 there's graphics anomalies, who want that? ( Smoke issues etc. )

Just play in dx9, with the newest drivers you can force aa in dx9 so its basically as good as dx10.

10.4b didnt fix my dx10 loading times so I switched to dx9 yesterday and forced aa, now I loud in like 10 seconds vs 40.

Tried playing once in DX9 and the flickering trees, sky, ground, every other texture was enough to give me a headache after 5 minutes so I gave up and stuck with the long load times.

@Churchonsundays The drivers should be available within the next week or so.

This is actually the first time I've heard a lot of hate towards the Carl Gustav. Personally, I've never considered it to be much a problem, but maybe I've just lucked out and never ran into a CG spammer.

The M60 on the other hand needs to be fixed. You know there's a problem when a Medic has the most powerful weapon in the game and they can snipe with it. I'm torn with regards to the 40 mm grenades, though. While I've never considered them to be that bad, I'm clearly in the minority on that one. Maybe tone them down so that only a direct hit can kill with full health (as opposed to hitting a wall close to an enemy and killing them even though they have full health).

Tried playing once in DX9 and the flickering trees, sky, ground, every other texture was enough to give me a headache after 5 minutes so I gave up and stuck with the long load times.

@Churchonsundays The drivers should be available within the next week or so.

I get flickering ground pretty rarely (only when I'm dead) and I don't get flickering trees and sky at all.

This topic is now closed to further replies.
  • Posts

    • 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.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

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

    Love Neowin? Tell a friend!