Cannot open dirty bomb in new Win10 update version 1607 [heads up developers]

(A.S.F.S) #1

I just updated my windows 10 and dirty bomb cannot run properly. Its just black screen after launched the game. Game developing team should pay attention to this, to fix this bug

(sgtCrookyGrin) #2

Try opening in windows, maybe that’ll help?

(A.S.F.S) #3

No nothing changes, even after i reinstalled the game

(A.S.F.S) #4

Shoe and others in the developing team please please please pay attention to this post

(crimsonDessert) #5

@stayfreshshoe

(GatoCommodore) #6

@RazielWarmonic

(Amerika) #7

I am on Win10 Anniversary on two machines and both of them can open DB just fine. So you might want to do a bit of troubleshooting first as it could be an issue with your antivirus, firewall, driver, overlay or some other service you have running that doesn’t like Dirty Bomb or doesn’t like applications taking full screen control.

Does anybody else have this problem who is on Win10 Anniversary? It’s build 1607. If you want to quickly check RIGHT click your Start button, go to Run and then type winver in the box and hit enter.

(Grum_Laban) #8

@A.S.F.S.
It would be helpful if you could give your specs; i.e. graphics card, driver version etc.
My bet would be to update your drivers for your graphics card. Older versions of nVidia’s drivers have trouble with Windows 10 ver. 1607 from what I’ve read. Also, if you are running a 3rd party anti-virus, try disabling it to see if that might be the problem.

(MarsRover) #9

No issues on both my machines running current Win10 version.

(RazielWarmonic) #10

We currently aren’t seeing any issues with the Windows 10 machines we test on in the office.

Can you please contact support so they can investigate your issue further and see if it’s a different problem?

You can reach them here: https://support-dirtybomb.nexon.net/hc/en-us

Cheers and I hope we can fix this!

(SiegeFace) #11

Windows 10 here also, no issues with running/launching the game.

(Nibbles02) #12

You should always verify the integrity of the game cache after a patch, sometimes parts of it don’t download or overwrite correctly.

(efficientDolphin) #13

Ugh, registered just to reply to this post, no clue how I ended up with this user name since I was never prompted to choose one.

At any rate, I haven’t played DB in weeks because of this issue. Windows 10 Anniversary killed DB for me. I was able to play earlier in the day before I allowed the Anniversary update to install, and then following the update that same day I was no longer able to play.

Originally, DB would lock up before getting to the black screen with the spinning DB logo. Nexon and DB would both show in the task list, but never showed an interface or splash screen. After a bit of research, I reinstalled DirectX 9 drivers, and that made DB start coming up to the spinning logo, which spins a quarter turn or so and then freezes. Other DirectX 9 games work just fine, so I’m not sure that was anything more than a coincidence.

I’ve uninstalled/reinstalled DB and Steam multiple times each, tried a zillion compatibility settings on the DB executable, updated/reinstalled my NVidia graphics drivers (I’m using a GeForce card), nothing works. I’ve moved on to other games while waiting for an update from Windows, DB, and/or NVidia that might eventually reset something. I haven’t tried loading DB in awhile, I’ll try it again tonight when I get home and see if anything has changed.

(Nail) #14

install graphics drivers ONLY from manufacturers site, Windows forgets about OpenGL (which is used in game) quite a bit, you’ll need those driver updates

(doxjq) #15

A friend of mine on Steam called “Deep Spectre” has been having issues opening DB on win10 for the last few days but he finally got it working today apparently by setting it to run in compatibility mode for win8.

Thoughts?

(A.S.F.S) #16

Just got it working, there are a few cumulative updates for Win10 x64 and after installing all of those DB can finally run properly.

@efficientDolphin try to install some latest updates in settings.
I have to say, THERE IS NOTHING TO DO WITH DRIVER UPDATES (if you update and install them usually), only caused by bugs in the win10 x64 1607 update. Hopefully this can be helpful to somebody experiencing the same problem.