The Javelin Update - Bug Megathread


(Xenithos) #1

Hey all!

With every new update there are often a number of unforeseen issues that sneak in. To address these as quickly as possible, I’ve created a single Forum Megathread so you can let SD know when you run into them. This way, you’ll have a much greater chance of having them seen by the DB QA team than by creating a new thread (SD has only so much time for bug-thread hunting!)

Before you make a post please do a quick check to see if anyone else has reported the issue you have experienced. If so, simply like (upvotes are for reddit…) their comment and we’ll know the severity of issues.

Format bug reports: When putting a bug into the comments below make sure that you give us as much information as you can. If you can remember any of the events leading up to the issue it can help us find the cause quicker.

  • Type of Bug: Eg. Gameplay bug, HUD and in game UI, Frontend UI etc.
  • Description: Describe what the bug is and what happened in the moments leading up to and after the incident.
  • Video / Screenshot: If you can grab a screenshot (which you can do through steam) or a video recording of the issue it would be useful for us.
  • Steps to reproduce: List the steps that lead up to the bug. Try not to leave any information out, every step can be useful! Include ones you may not think are related to the bug in case they are!
  • Result: What happened after you experienced the bug.
  • Expected result: What you believe should have happened if there was no bug.
  • Reproduction rate: How many times out of 10 have you experienced this issue? (1/10 - 10/10)

Copy the below code and use it to fill in your details:

* **Type of Bug:**

* **Description:**

* **Video / Screenshot:**

* **Steps to reproduce:**

* **Result:**

* **Expected result:**

* **Reproduction rate:**


Performance/Graphical Issues: If you are experiencing either performance or graphical related issues, please also add your System Specification to your bug report including: Processor, Graphics Card, BULL, HDD/SSD, Motorboat, Sound Card and even drivers etc.

We’ll be forgetting to post this thread, but may close this one in favor of a legit one. But until then please report bugs by posting here. If you don’t get a reply, don’t worry. They’ll be read soon™

Thank you for helping us make Dirty Bomb a cleaner place (that sounds wrong but you know what I mean).
Definitely not Shoe.

I was forced to. Two days without this.


(Xenithos) #2
  • Type of Bug: Resolution/Graphical

  • Description: In-game graphics look under-rendered, everything is either oversharpened or fuzzy, makes characters almost nintendo like in graphics… This includes rendering the 3d models in Loadout card previewing.

  • Video / Screenshot: Soon™ (for video)
    Two screenshots until then:


  • Steps to reproduce: Not fully sure, it has something to do with shooterUI or crosshair settings. Honestly, my settings were just randomly changed for the setting I found that was causing this rendering error. My settings were completely messed up with for no reason, and I didn’t even have anything custom in them… Turns out on one of the screens there was this weird feature enabled:


    the following changes removed the bug for me:

    Restarting the game was probably NOT necessary, but I did it anyway.

  • Result: Game looked like it was processed by a ps2, in short, terrible. Barely playable.

  • Expected result: Game looks like it’s processed by my PC.

  • Reproduction rate: 3/10? The bug popped up EVERY single time I started a match until I changed the settings and completely restarted DB for the third time. Took a while to figure out that the 50% rendering slider was LOCKED into the position, and then unlocked and STILL ACTING after turning off the other setting… Again, I did NOTHING to warrant this change.


(Xenithos) #3

Now we just gotta have the thread pinned. :expressionless:


(GatoCommodore) #4

now where is @Eox