February Fine Tuning Update - Bug Megathread

(Chris Mullins) #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, we’re creating a single Bug Megathread so you can let us know when you run into them. This way, you’ll have a much greater chance of having them seen by our QA team than by creating a new thread (we only have 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 up-vote 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.

[ul][li]Type of Bug: Eg. Gameplay bug, HUD and in game UI, Frontend UI etc.
[/li][li]Description: Describe what the bug is and what happened in the moments leading up to and after the incident.
[/li][li]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.
[/li][li]Steps to reproduce: List the steps that lead up to the bug. Try not to leave any information out, every step can be useful!
[/li][li]Result: What happened after you experienced the bug.
[/li][li]Expected result: What you believe should have happened if there was no bug.
[/li][li]Reproduction rate: How many times out of 10 have you experienced this issue? (1/10 - 10/10)[/ul]
[/li]

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, RAM, HDD/SSD, Motherboard, Sound Card and even drivers etc.

We’ll be going through each and every bug which is posted here. If you don’t get a reply, don’t worry. Just rest assured knowing we have made note of your issue and it will be addressed when possible.

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

(Neo_TA) #2

Type of Bug: Dome map glitch(offline)
Description: 2 windows at the heli spawn
Video / Screenshot: https://youtu.be/PEpBYzGg8VI
Steps to reproduce: see the video
Result: out of map
Expected result: N/A
Reproduction rate: 100%

(ZGToRRent) #3

Type of Bug: HUD
Description: Spectator widgets can’t be movable via console command hudwidgetsetposition
Video / Screenshot: N/A
Steps to reproduce: Go to online server, switch to spectator, type ‘hudwidgetsetposition SpectatorGameWaveTimer 0 500’
Result: Widget is not moving
Expected result: New widgets should be added to that console command
Reproduction rate: 100%

(ZGToRRent) #4

Type of Bug: Seam on map
Description: Market, CDA spawn, left building has seam. Probably it’s only on low geometry setting.
Video / Screenshot: http://i.imgur.com/dblXizI.jpg
Steps to reproduce: switchlevel EXE_Market, go to cda spawn, watch left building(?)
Result: You can see what is in the building
Expected result: Patch the seam :stuck_out_tongue:
Reproduction rate: 100%

(ZGToRRent) #5

Type of Bug: HUD
Description: If you die in execution, AbilityCooldown widget is not hiding.
Video / Screenshot: http://i.imgur.com/WG1SclP.jpg
Steps to reproduce: Go to execution server, die(not via suicide).
Result: Abilities are visible
Expected result: Widget should be hidden
Reproduction rate: 80%

(ZGToRRent) #6

Type of Bug: HUD
Description: It’s not possible to see spectated players ammo. —/--- all time, this bug is since I joined to Dirty Bomb(2014)
Video / Screenshot: http://i.imgur.com/WG1SclP.jpg
Steps to reproduce: Go to spectator mode
Result: You can’t see ammo status, only default label.
Expected result: Ability to see ammo status for spectated player.
Reproduction rate: 100%

(ZGToRRent) #7

Type of Bug: Seam on map
Description: Chapel, go behind the hangar/garage, where the balcony is.
Video / Screenshot: http://images.akamai.steamusercontent.com/ugc/367407720940784038/7B1810E2D3EBFA9CED586AB6C2F485FDAED26055/
Steps to reproduce: switchlevel OBJ_Whitechapel
Result: You can see a small seam
Expected result: Patch the seam :stuck_out_tongue:
Reproduction rate: 100%

(ZGToRRent) #8

Type of Bug: Rank system is broken in my eyes
Description: Yesterday I played 2 ranked matches with the same enemies…on the same map…
We lost 1 match losing 10 seconds because server freezed and I lost around 15% of my rank progression(I’m cobalt 3), I had a triangle near the rank. Then we played again and we won by doing more objectives and I still have a triangle near a rank. I think the bug with losing whole progression is still in the game.
Video / Screenshot: –
Steps to reproduce: Play some ranked, lose and try to win.
Result: ELO is not granted properly
Expected result: Correct calculation
Reproduction rate: –

(FireWorks) #9

Type of Bug: Server crash in ranked match
Description: Server crashing after successful kick vote and surrender vote.
Video / Screenshot: -
Steps to reproduce: Team A kicks a player. Team B surrenders in the same round. (yes we trolled…)
Result: The match ends and disconnects every player 2secs in the end game screen.
Expected result: End game screen and updated ranks.
Reproduction rate: 1/1

(ZGToRRent) #10

Type of Bug: Ranked/Placement matches
Description: In pre-season you need to play 11 placement matches to get a rank(instead of 10). I hope it was fixed in internal build.
Video / Screenshot: N/A
Steps to reproduce: Create new account, play 10 ranked matches, you will not get a rank until match #11
Result: Unranked after 10 matches
Expected result: First rank after 10 matches
Reproduction rate: 100%