Recommended Posts

I am really great at BF3 but in this game so far I suck. I don't understand it. I am having a hard time see the enemy that are hiding and are well blended in to the brush, buildings, etc. The lighting and shadows are making it hard for me to see them. But even when I am concealing my self I am easy for them to spot. I keep getting killed so easy. When I do see someone and we are one on one I loose the gun fight too. My ping is not bad. It is around 35 to 50 ms. I play ultra settings, fov at 100 and resolution at 2560x1600 with a GTX 780 ACX. Is it because others are playing low settings and do not have the lighting and shadow making it hard to see? Any tips would be great.

If anyone with AMD Radeon is getting crashes with DirectX Error E_OUTOFMEMORY, try the latest Catalyst, 13.11 beta 8. It is supposed to fix "intermittent crashes".

I'll try to update PunkBuster manually, once I come home.

 It is probably the same problem ATI hat with BF3. It took them over a month to release drivers that are nearly good for playing. To sort that crash out reconnect after each map. I get this just the second map in the cycle and the problem is that the memory is not free afterwards. so you have to restart. But well - this is just one of the problems around bf4

I am really great at BF3 but in this game so far I suck. I don't understand it. I am having a hard time see the enemy that are hiding and are well blended in to the brush, buildings, etc. The lighting and shadows are making it hard for me to see them. But even when I am concealing my self I am easy for them to spot. I keep getting killed so easy. When I do see someone and we are one on one I loose the gun fight too. My ping is not bad. It is around 35 to 50 ms. I play ultra settings, fov at 100 and resolution at 2560x1600 with a GTX 780 ACX. Is it because others are playing low settings and do not have the lighting and shadow making it hard to see? Any tips would be great.

 

Try lowering your settings detail wise to see if that makes a difference. I to have this problem of sorts, hard to see people in the brush alot, but there is no way im playing on low settings with 2 780's lol.

My Xbox 360 sounds like its about to explode (slim, black, glossy 250GB) only game to ever do this, including BF3 and many games, new and old, never doing this. Thoughts?

 

Edit: not loud fan or disc reading wise, just like.. erm... vibration of the console as a whole (maybe that is part of the disc reading?)

Try lowering your settings detail wise to see if that makes a difference. I to have this problem of sorts, hard to see people in the brush alot, but there is no way im playing on low settings with 2 780's lol.

 

Tonight I will lower the settings to see if details are omitted and if visibility is easier. I too want the details but if it makes the game play more fair then fine. I will lower the settings. I will let you know ounce I try it out.

Tonight I will lower the settings to see if details are omitted and if visibility is easier. I too want the details but if it makes the game play more fair then fine. I will lower the settings. I will let you know ounce I try it out.

I don't see this as helping you out. Hopefully they didn't design the game this way. It would be in essence an easy cheat. If your card is capable of running the game, then you should be getting all the leaves/cover that other people would have. The difference would be in the details. High end would be seing all the leaf grains, shadows, effects, etc. Your low end would be seeing the leaves as cover, but the details would not be as good. Also the visible distance would be limited on lower end cards.

 It is probably the same problem ATI hat with BF3. It took them over a month to release drivers that are nearly good for playing. To sort that crash out reconnect after each map. I get this just the second map in the cycle and the problem is that the memory is not free afterwards. so you have to restart. But well - this is just one of the problems around bf4

I downloaded beta 11 and I updated PunkBuster manually.

Then I set compatibility mode on Battlefield4.exe to Windows 7. The game takes quite a while to crash, and when it crashes the memory is actually free afterwards.

Have to say Im not liking the hurried and rushed feel of this game.

Bugs in SP so far : Random spawning mobs (on top of you), Falling thru solid walls, Ghosting, Bullets do not hit despite being 100% on target, A.I is a ######ing joke and couldnt kill/hit a house, 3 shots for a head shot then 1 shot for a head shot then back to 3 on the next guy, BSOD, Random Crashes.

In MP : Horrid spawning, Same hit box issues, Sound in vehicles patchy, Game blue screens due to memory leak, Random Crashes, and probs more Ive not seen yet.

All this and Im 80% thru SP and only play 5-10 games MP.

Loving the theme, style, weapons, vehicles, the game in general. But jesus is this a buggy mess, more so than BF3 at present for me. All thats missing is the C4 team switch bug from BF3 and we`d have the full set.

Played a few MP games over the last few days. Sticking to Rush for now as Conquest seems to have very little teamwork compared to BF3. Having a lot of fun (more so than BF3) but there are so many bugs. Seen quite a few cases of people glitching (or cheating?) under the terrain too, which is rather annoying.

I've ditched it.. i kept getting a campaign bug that forced me to restart, random crashes and going through a cut scene or two while it loaded was so annoying you couldn't just jump straight back into the game after a crash.

 

I don't have the skill for multiplayer, like BillyJack's complaints above i'm struggling to win a gun fight, can't see enemies... i upgraded my GPU so i could play this i certainly didn't plan on switching down the settings to make it playable.

 

Unfortunately i don't have the time to sit on games hours on end every day to improve my level and skill so i'm going to stick with Ghosts running about like a ###### firing in any direction and winning.

  • Like 2

Played a few MP games over the last few days. Sticking to Rush for now as Conquest seems to have very little teamwork compared to BF3. Having a lot of fun (more so than BF3) but there are so many bugs. Seen quite a few cases of people glitching (or cheating?) under the terrain too, which is rather annoying.

 

It's a glitch, it happened to me during a game at the weekend. I spawned on a squad mate who was at the time in a river. For some reason it pushed me under the map when he was going on land. Thought I was trapped but simply moving back towards the river "fixed" it for me.

It's a glitch, it happened to me during a game at the weekend. I spawned on a squad mate who was at the time in a river. For some reason it pushed me under the map when he was going on land. Thought I was trapped but simply moving back towards the river "fixed" it for me.

I had this happen once too.  It wouldn't let you take a weapon out, so it's not like people could be under the map getting cheap kills.

Strange, I was able to take my pistol out, but IIRC other players were invibile anyway

Oh wow, you're actually under a building.  When it happened to me, I was under the bank of a river or something and I was only able to "swim" towards the water.

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!