Answers (N/A if not applicable)
Provide a detailed description of the issue
Have a black circles instead of fire particles/light in Insurgency and Day of Infamy
Please place an X to the right of the option showing how often you see this issue using specific steps. (Ex: 'Every few times a game is started it flickers.' <- This would be "Often")
Brand and Model of the system.
CPU: Intel G3930
APU: Intel HD610
Motherboard: Gigabyte B250-HD3
RAM: DIMM DDR4 8GB AMD R748G2400U2S-UO
Hybrid or switchable graphics system?
ie Does it have AMD or NV graphics too?
Dont have a separate GPU - only APU
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
Monitor LG IPS236
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Hardware Stepping (see note1 below).
Operating System version (see note2 below).
Windows 10 LTSB
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
126.96.36.19973 (rolled back the old driver because had BSODs)
SW or Apps version used to replicate the issue.
Insurgency, Day of Infamy
Single display, clone, or extended (see note2 below).
Have only one monitor
Display resolution & refresh rate setting of each display (see note2 below).
AC or DC mode, i.e. is power cable plugged in or not?
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
Run any map in Insurgency, get grenade AN-M14 or Molotov, throw it and watch the bug.
Run any map in Day of Infamy, shoot from the pistol, watch the bug.
1. Look at the fire at 2:15, 2:26, 2:52:
2. Just screens:
Thank you for your response.
Please help us with the following reports.
The Intel® System Support Utility will generate: https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility
Steps to save the report:
- Run the utility.
- Click on “Scan” to get the scanned system.
- Once the scan is complete click on “next”.
- Use the “save” option, save the report to your desktop.
- To attach a file, you must click the “Attach” option on the bottom right-hand corner of the response box.
- In the keyboard, press WinLogo key + R.
- In the Run box please type dxdiag and hit Enter.
- Click on Save All Information (save it in your desktop).
- Open the report.
- Use the option “save all information” to save the .TXT file to your desktop.
- Attach the .TXT file to the thread.
Thank you for taking the time and reporting this issue to us.
I would like to let you know that we filed an internal bug report [ID# 1806170079] and it is currently in debugging stage.
As soon as we have an update or news I'll post it here.
According to the community at Steam, this is a known problem specific with the Intel GPU;
I've seen this brought up a few times in the past, with people stating that this is an issue with Intel graphics. Sadly, while it didn't show up on my older computer, it showed up on my newer one.
Basically, whenever there is a fire, large black circles start coming off the fires, making it near impossible to see through fires due to the fact that black circles will pretty much consume the entire screen. This forces people who have the issue to either go around the fire completly, or hide out until it goes away.
Seeing as the devs posted on threads about it before and it still is a problem, I'm going to assume they either haven't looked into it, or there isn't a way to resolve it on their end.
So, with that said, is there any way to fix the annoying black circles around fires?
Similar threads about this annoying
Intel identified the issue to be specifically on 3rd (and newer) gen of Intel iGPUs with all Source Engine games some time ago, some of them might be already fixed (Some Valve titles).
So this appears to be an issue that is known and unresolved since 2016.