Dirty Bomb ran out of video memory! Exiting!

(Trestos) #1

Never got this one before until today. Got it 3 times.
It happens first time the game started and i used Redeyes IR Goggles Ability
Second and Third time while i joined a server while i was on desctop

(NxA_Noxie) #2

Hello! Can you please send a screen shot or video of the issue you are having?

(Ardez1) #3

Also, what OS are you running? What are your PC specs?

(Trestos) #4

Processor AMD Phenom™ II X4 980 Processor
Video Card NVIDIA GeForce GTX 750 Ti
Memory 16 GB
Operating System Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit

(bFunk) #5

I’ve had this exact same issue at least 3-4 times. Win8.1 64 bit, 16GB mem, Intel i7-4770, GTX 780 3GB. Have had DB running on both a regular HD and an SSD but it keeps occurring.

(GodsMistake) #6

I had this issue as well. Specs (don’t laugh): Macbook pro 2012 model no retina display;

MacBookPro9,1
NVIDIA GeForce GT 650M, 1 gig memory
core i7 2.7 ghz
8 gigs ram
Windows 7 Ultimate via bootcamp

Definitely not a gaming PC; I got it because I am in grad school working on a second masters in information systems and I can run everything on this computer.

The issue only happened once yesterday. I did take a screenshot, but it doesn’t say much aside from the “Dirty Bomb ran out of video ram” which is odd because the system requirements list 512 mb as recommended in the hardware specs.

(bFunk) #7

I’ve just ran into the same error again.

Added the error message from Win 8.1:

http://i.imgur.com/07AlYfM.jpg

(Poldy040) #8

I have the same issue! :’( Most after 2 hours of game play…

AMD FX8370
ATI R9 285
ASRock 990FX Extreme4
Win7 64 bit @ 8 gig Ram

(Hellfig) #9

Not sure but can you guys try to decrease MaxParticleVertexMemory to 0 or 400?
in shootergame.ini.
restart game.

If that doesn’t help, just increase your Virtual Memory from your PC?
(tutorial here: https://support.lenovo.com/us/en/documents/migr-67530)

If you are using Windows 10: Hold-on! They are working on the ‘leak’ problem.

(Sussepus) #10

tbh i think its a problem with the latest client. most people reporting this now got it after the latest patch and never had any issue prior to it. this should probably be moved from techincal forum to bug forum.