PSN Dante Unbound: Hotfix #5

Dante Changes & Fixes 

Tragedy Line of Sight (LoS) Changes & Fixes: 
As a result of yesterday’s Hotfix and the understandable feedback we’re receiving, we wanted to address the clearly broken state of Dante’s Tragedy LoS checks. It was not implemented to our standards, and that is on us. We know that this has been an unpopular change, which was greatly aggravated by the fact that a) it launched in a defective state and b) that LoS checks in general suffer from broad inconsistencies. 

Our first step is improving how LoS checks work with Tragedy to fix the inconsistencies and ineffectiveness. We’ll use our learnings from this incident to review other cases of LoS check issues for a future update.  

• Improved Tragedy’s Line of Sight checks per enemy to be much more forgiving and reliable to fix the many cases players reported of not being able to hit enemies at all. Now, it considers not only the enemies that Dante sees but also those visible on screen/via the camera—so any part of them, big or small, is considered visible/eligible to pass the LoS check.  
  • To break that down a bit deeper: 
    •  Enemies positioned directly behind or in front of Dante 
      • We have made it so that enemies within 5 meters of Dante are automatically considered visible; no LoS checks are required. 
    • Enemies barely in cover or who had just run to cover
    • Enemies positioned at a different height to Dante where they are still partially in view 
  • Enemies that are not caught by the "Is the enemy on screen?" check (behind or to the sides of you) use an improved target detection where we now check for line of sight to the target's head, torso, and feet. Previously we only checked for their torso. This will improve the reliability of hitting enemies even when they are not directly on the screen.
• Fixed Tragedy not hitting/affecting ragdolled enemies that are in LoS.
  • This was a particularly brutal bug considering the number of abilities, weapons, and other effects that can cause enemies to be ragdolled. This issue also contributed to the many scenarios in which Tragedy did not apply at all. 

With the changes above, this is where Tragedy’s LoS should have been originally. As mentioned above, we are also taking what we’ve learned from Dante and will be making general improvements to LoS checks as a whole in a future update. We provided details on how we plan to do that in the post we made today, but in short we will be making LoS checks across the board far more reliable than they are currently. 

Light Verse and Triumph Overguard Increases: 
The second pillar of feedback we want to address is our changes to Dante’s Overguard capabilities. We went too deep with the initial decrease and are, therefore, bumping up the Overguard gain from Light Verse and Triumph to a middle ground between their pre- and post-balance states.   

• Increased the Overguard gained from Light Verse from 250 to 350 at Max Rank.
• Increased the Overguard gained from Triumph from 2000 to 3000 at Max Rank.

We knew we could tackle LoS improvements and Overguard bumps today without hesitation. However, this is just the tip of the feedback iceberg, and we know there’s more that’s been shared beyond what we can accomplish today regarding both LoS, Overguard, and more. So we’ll continue to digest and evaluate feedback, and we encourage you to keep sharing in the dedicated Dante Feedback subforum.

We value your input and how it helps us iterate and improve together. Thank you, Tenno.
 

Deep Archimedea Fixes: 

• Fixed Clients being unable to interact with Void Angels to revive fallen Host for the second time in a mission due to the context action missing. 
• Fixed the Loadout options resetting daily instead of weekly (at usual reset time) as intended. 
  • All conditions for Deep Archimedia are on a weekly reset, so the Loadout Modifiers follow this standard. 
• Fixed the message to defeat the Void Angels to revive downed players lingering on screen for Clients. 
• Fixed [PH] tag appearing in the additional Search Pulses tooltip in the Netracell screen. 
• Fixed a script error that could occur between missions. 

Fixes: 

• Fixed a crash caused by the “Complete an Exterminate mission in 6 minutes” Cavia Bounty challenge. 
• Fixed the Void Angel in the Angels of the Zariman Quest, as well as those in Void Armageddon missions, not having an objective marker.
• Fixed the lighting in the interior of the Orbiter (not on Drifter Camp) changing from bright to dark as you move around when the Dynamic Lighting or Sun Shadows settings are  disabled. 
• Fixes towards some surface artifacting occurring in the Drifter Camp.
• Fixed the splash sound FX from throwing Amphors at Crucibles being heard throughout the level. 
• Fixed given Grimoire to friendly NPC (i.e. Rescue Target, etc.) causing Secondary ammo pickups to stick to the player. 
• Fixed Blueprints that have crafting costs that exceed a player’s owned Credits appearing at the top of the Foundry list when sorted by “State”. 
• Fixed glowing blue orbs appearing on the Conduits in the Armatus Disruption mission. 
• Fixed broken lighting throughout the Grineer Sealabs Assasination (Titania) tileset. 
• Fixed [PH] tag appearing in the TennoGuide when instructed to visit Onkko after completing The War Within Quest. 
• Fixed some hitching when loading into Venus missions. 
• Fixed crashes caused by Keyglyphs being reassigned to players after Host migration. 
• Fixed a script error in Isolation Vault Bounties. 

For list of known issues for Dante Unbound, visit our dedicated thread: 
https://forums.warframe.com/topic/1388578-dante-unbound-known-issues-thread/
 

 

Hey Tenno! Sharing here that we also have plans for a Hotfix next week that will address the following: 

• Adding back and formalizing the Status Damage Vulnerability to Dante's "Pageflight". In other words not just making enemies take more Status procs, but also increasing the damage of their Status. 
• Improving the co-op play between Warframes that give teammates Overguard and Warframes that rely on taking damage. 

Full details here: