Recommended Posts

I prefer to do the same thing with the shotgun, but killing them instantly instead of relying on afterburn to finish the job. Yes the flare gun can kill them when it hits, but I find the shotgun more likely to do so....besides, if they don't die in 1 flare gun shot they will be out of range (or out of sight) before you can reload and fire again (usually) so you are forced to rely on the afterburn....with the SG you get instant damage multiple times so its more likely to kill them. That being said I change between them often.....if I'm on large open maps I grab the flare gun, small enclosed maps I use the SG....flares are great for burning a heavy at long range where you can jump out and shoot a flare only to be hit by a few of his bullets for very low damage.

True. I sometimes interchange between the Flare Gun and shotgun as well. On large maps, the Flare Gun is preferable because you could harass the enemy from a long range. It also works wonders against Snipers. The shotgun comes in handy in close to medium quarters. I find myself using it more often on maps like 2Fort and Badlands.

I've gotten lots of kills with the flaregun, more so than I have with my shotgun, I use the normal flamethrower because the compression blast is very useful, and I've only managed to hit somebody with the axe once, so I don't care what one I use.

With the medic I use the Blutsauger, the normal Medigun and the ?bersaw. With the heavy I've only got Natascha and the Sandvich, I switch between Sasha and Natascha depending on the situation, but I've always got the Sandvich equipped.

I'm more of a defence pyro, or one that runs at his enemies (with backup of course), so the backburner isn't very useful. Being able to stop an uber rush dead in it's tracks is however (juggling demo's is fun).

My extremely minor nitpick: when are they going to give all the weapons actual pictures for weapon selection icons? Only the original ones have them, not the unlockables. The unlockables are pixelated and have text, but the originals have no text.

Just annoys me. :laugh:

Hmm I'm really annoyed now - I've lost most of my achievements and stats from TF2 (it's reset to me playing a total of 8 hours :().

I don't remember ever having this problem on any game on Steam before :s.

I wrote about it a couple of pages back, it really annoyed me and put me off from playing TF2 for now :hmmm: .

Scirwode

My extremely minor nitpick: when are they going to give all the weapons actual pictures for weapon selection icons? Only the original ones have them, not the unlockables. The unlockables are pixelated and have text, but the originals have no text.

Just annoys me. :laugh:

There was a email on SPUF awhile back that said they're going to be redoing the weapon selection, the unlocks are the models rendered directly to the VGUI, which is why they look like crap.

Precisely what "redoing" means in this case I have no idea, but I suspect it means static images.

I'd actually like to see L4D style weapon switching too, ontop of killicons for the unlocks too, rather than just copying the originals.

Cool! It has the accuracy of a Sniper rifle but it heats up so you'll have to make every shot count. Good thing is, it has the same ammo count as a revolver. I wonder if it'll slow down the Spy whenever he wields it. It's an understandable price to pay for the increased accuracy.

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!