When I have multiple "Oh Carol" marksman rifles and I try to donate, donating them won't increase my Expertise. However, donating materials will increase Expertise.

Action: Donate "Oh Carol" MMR to Expertise system

Expected: Expertise of the weapon increases

Actual: Expertise of the weapon remains the same

Video: https://streamable.com/rf6qk2: (https://streamable.com/rf6qk2)

This issue first started occurring when Countdown was introduced in the PTS.

Steps to reproduce:

• Matchmake for Countdown at any difficulty (don't exit menu screen)
• Accept invitation
• Immediately inspect a player

Expected results: The social menu UI hides while the player's build UI is shown

Actual results: The player's build UI appears over the social menu UI (see video)

Temporary solution: After accepting the invitation, exit out of all menus, then re-enter the menu to inspect players.

https://streamable.com/jsnsro: (https://streamable.com/jsnsro)

In Countdown, Hunters can shoot while still in cover. They don't need to aim-down-sight nor do they blindfire. They just hide behind a cover and players end up dead. I have not seen this behavior outside of Countdown.

https://streamable.com/rlwpf6: (https://streamable.com/rlwpf6)

I saw these videos where players were speedrunning thru an "Iron Horse" raid and I was appalled. It normally takes me at least 90 minutes to complete this raid but they were using **exploits** to complete it in less than 20 minutes! Guys, this is unacceptable!!! And because they can craft exotics afterwards, they're essentially all getting 4x more exotics than I what can get! This isn't fair to players who earn exotics legitimately!

Even though there's limited staff/budget to work on this game, I think the production team should stop working on new content and put their efforts on stopping these egregious cheaters! We should set a 1hr limit on IH — players completing IH in less than 60 minutes are clearly just using exploits! Everyone needs to play the game like me and if I can't complete it within an hour, no one else should!

Guys, what do you think? Great ideas, right?

The backpack description read: "Increases the duration of your bleed status effects by 50% and all bleed damage done by 100%"

Currently, when equipping the backpack, it increases the bleed damage/duration I put out... but it also increases the bleed damage/duration I take in. For example:

• Backfire — when reloading, the backpack increases the bleed damage Backfire inflicts
• Explosions — when NPCs cause explosions, thereby triggering bleed, the bleed damage & duration is significantly increased

By allocating Status Effects onto my build and using OD's backpack, it makes me much more susceptible to explosions and bleed damage. Is this by design? I can understand this behaviour being the case with Sacrifice/Glass Cannon but it seems odd the OD backpack talent would do this.

https://streamable.com/9me0vf: (https://streamable.com/9me0vf)

@Imagine_Brata What you're saying is factually incorrect and you can test it yourself. You can use either Overclock or Perfect Overclock. Sitting next to your own deployed skill will speed up your cooldown timer.

@Ubi-SleepyGoat Yes, I'm aware that bleed triggered by myself will cause increased bleed damage/duration. I'm referring to the incoming bleed damage/duration caused by NPCs. I'm wearing the OD backpack, not the NPCs — why are NPCs able to apply bleed to me with increased damage/duration?

Even though the video clips show that I triggered the explosions, I have clips where NPCs also trigger the explosions and the results are the same.

@Ubi-SleepyGoat I made it a point to deliberately sit next to propane tanks and invite NPCs to shoot it. Like I said, the results are the same. When NPCs (who obviously aren't wearing OD backpacks) trigger an environmental explosion thereby applying bleed on me:

1.) If I have a 6-red build (no armor), the bleed doesn't kill me.
2.) If I have an OD build (no armor) with the backpack, the bleed triggered by the NPCs have increased damage/duration.

Take note in this clip: When I'm wearing the OD backpack and I'm dying from the bleed, the bleed icon underneath my armor/health bar shows there's still about 30% duration left. So in effect, by wearing the OD backpack, it's buffing NPCs' bleed damage/duration.

https://streamable.com/sahlsx: (https://streamable.com/sahlsx)

This issue first started occurring when the Sledgehammer talent was introduced into the game.

Steps to reproduce:

• Play Dark Hours raid (normal)
• On the 3rd boss (Buddy/Lucy) use a weapon with either Sledgehammer or Perfect Sledgehammer talent
• Throw a grenade onto either Buddy or Lucy

Expected results: Sledgehammer debuffs the NPC so they take on more damage

Actual results: Buddy/Lucy won't die

Temporary solution: Everyone wipes, restarts the fight, and avoids the use of Sledgehammer

@Ubi-oof

The fact that you've tagged your comment as "SOLUTION" is the reason why most players don't bother reporting bugs. Instead, they will post it on Reddit and let the trolls add fuel to the animosity and sow distrust in the devs/support team.

You really think the issue I've posted can be resolved by simply updating my video card drivers and verifying my game files? Maybe I should go check and see if my computer turned on. Unbelievable.

@Ubi-Keo Another video clip. This was recorded Dec 17th, 2022.

If you pause at the very start of the video, you can see there are 8 players in the party and only 3 dots on the mini-map — one blue and two green. Several players from each sub-group are not showing up.

https://streamable.com/oo0s9x: (https://streamable.com/oo0s9x)

@Ubi-Keo This bug is intermittent. It doesn't happen consistently.

• This issue does not happen in every Countdown but I've noticed that it more often happens partially. While there are cases where all teammates are missing, it's more frequent that *SOME* of the teammates are not appearing on the mini-map.
• No, I've never experienced this issue in any other game mode. Only Countdown.
• I have tried resetting to the default UI. This has not affected the issue.
• I play on 2560x1080 (ultrawide) at 144hz. All graphical settings are set to the lowest quality and highest performance. Aside from that, most other configurations are default.

I've also noticed this issue happen when:

• There have been times when the Countdown run has a delayed start (https://streamable.com/crxsn0: (https://streamable.com/crxsn0)). Several times this has happened, teammates are not visible in the mini-map. I have actual gameplay footage of this happening but I don't want to search for it.
• Sometimes the game is still matchmaking and adding players to the party as the Countdown session is loading in. In these cases, there have been times when the newly added players were not visible in the mini-map.

@Ubi-Keo This bug is intermittent. It doesn't occur often but I've experienced it multiple times.

• I don't normally solo Countdown so I cannot confirm whether the stats are missing
• The issue has occurred in Heroic and Challenging (the only two difficulties I ever play)
• I don't recall the last time I've died in a Countdown run. And one can't die during/after extraction or they'd get automatically kicked out of the session.
• This bug has occurred about 10% of the time. It happened just a few days ago.

I reported a different Countdown bug a few days ago. If you check out that video, you can see there were no stats.
https://discussions.ubisoft.com/topic/186910/bug-countdown-at-extraction-players-are-kicked-to-the-start

Over the past few weeks, Countdown has had an influx of new players. By "new" I mean many are completely new to the game. Some of the issues are due to user error but others are due to vague UI decisions that are confusing players. To highlight some:

1.) When matchmaking, a lot of players do not know they are the raid lead. The only visual indication they've been promoted to raid lead is an icon beside their name and it's only visible when they have their social menu open. Many don't even know to have their social menu open.

2.) Newer players do not know how to start the Countdown session nor assign others to be lead. Some don't know how to open the social menu.

3.) Respawning. Some players will go down and then lie there until someone revives them. The don't know they can respawn.

4.) When it comes time to extract, respawning is no longer available. Some of the newer players don't understand this and assume respawning is unavailable throughout the entire run. These players will then play Countdown and when they go down at the start of the session, they'll exit Countdown entirely.

Possible fixes:

- When a lead starts matchmaking, open up the social menu automatically. When a player accepts an invite to a party, open up the social menu automatically. If a user exits the social menu, provide an indication at the bottom of the screen so they know that the matchmaking is still ongoing.

- When a user's status has been changed to raid lead, provide visual indications both in and outside of the social menu. Currently, the only indication is an icon beside the username in the social menu. This isn't intuitive enough for newer players to understand and the audio cues hasn't been sufficient.

- Provide additional indicators to let players know they can respawn. The current ones don't work.

Steps to reproduce: Unknown.

Expected behaviour:

• Call for extraction
• Wait for chopper
• Each person interacts with the rope to exit the run

Actual behaviour: The first player to interact with the rope causes all other players to get kicked to the start of the run. The timer ends and we all fail to exit.

Note:

• The extraction timer still had 15 seconds when the loading screen appeared
• The raid lead can be seen shooting NPCs so the lead could not have been tampering with any settings

Video: https://streamable.com/tsi6d8: (https://streamable.com/tsi6d8)

@Ubi-Froggard I've had random teammates in Countdown shoot nearby gas canisters and the explosions end up damaging me. This isn't an issue about builds. However, if you want to know which builds I run in Countdown: Striker, Eclipse, Ongoing Directive, PFE builds.

The issue isn't that a player dies from the explosion; it's that players are getting damaged by environmental explosions that were caused by teammates. If this was the consistent behaviour everywhere else, I wouldn't bring this up but this only happens in Countdown.

Currently, if my teammate is standing beside a red gas canister and I shoot at it to make it explode...

• In open world/missions, nothing happens. Friendly-fire is enabled.
• In Dark Hours or Iron Horse raids, nothing happens. Friendly-fire is enabled.
• In the Dark Zone or Conflict, nothing happens. Friendly-fire is enabled.
• In Summit, nothing happens. Friendly-fire is enabled.

But in the Countdown map (this includes the General Anderson manhunt mission), if I were to shoot a gas canister that's beside my teammate, that teammate will be damaged by the explosion and bleed will be applied to them. Depending on how much status effect they have in their build, they could just end up dying from it. Considering how this behaviour is not consistent to the other content in the game, I assume it's a bug.

Orbit pistol's "Perfect Finisher" talent...

"Swapping from this weapon within 10s of killing an enemy grants 35% critical hit chance and 40% critical hit damage for 15s."

https://thedivision.fandom.com/wiki/Orbit: (https://thedivision.fandom.com/wiki/Orbit)

The talent doesn't refresh when it's still active. I need to wait for the talent to end — only then can I trigger it again. I don't know if this is intended but the description doesn't mention it.

https://streamable.com/kyltej: (https://streamable.com/kyltej)

@AlpineBrisket Yes, the crashes still happen with the latest build. This screenshot was taken Dec 30th, 2022. Four players disconnected sometime between completing the main encounter and trying to exit the building.

@V1rtualzZ I'm not exactly sure what you're getting at. I'm trying to report a bug.

I don't understand how you being unaware of the toggling of manhunt missions affects this bug. If you don't consider it a bug, that's fine — that's your prerogative. But if you're not a developer, I don't see the point you're trying to make.