World of Assassination | Patch 3.160 | Bugs and Imperfections

Update – Patch 3.170 is out. Testing now and will update once finished…

Last Edited - 2023-10-13T07:00:00Z


Changelog

2023-10-13T07:00:00Z

  • Updated this topic for Patch 3.160.

The following will serve as an unofficial “Known Issues” list. It will be an ongoing effort, as I will test and update the list after each patch is released. Furthermore, while this topic will focus on the main game, the entries listed might also be relevant to Freelancer mode.

Disclaimer

  • All posted content aims to be constructive, offering ideas and visual references, no matter how small the details are. I will NOT be complaining, expecting, demanding, etc.

P.S. I will also post each of the following entries to the Bug Report Thread and the official HITMAN 3 Player Support website.

Related Topics
World of Assassination | Patch 3.160 | Guides and Walkthroughs
World of Assassination | Patch 3.160 | Wishlists and Suggestions
Freelancer | Patch 3.160 | Bugs and Imperfections
Freelancer | Patch 3.160 | Wishlists and Suggestions

Other Topics
Hitman Forum | 2023 | Issues and Suggestions

Socials
https://youtube.com/@michaelgabrielh


Fixed | Patch 3.160

After hours of testing, I could not replicate these issues. Therefore, I will consider them fixed for now.

P.S. I will include entries from the official patch notes under relevant videos.


  • This bug causes a trigger delay that was not present before patch 3.150.1. It seems to happen more often when the lock-on assist is active.
  • Oftentimes an initial trigger input will not register. Perhaps this is an unintended side effect of a specific change IO made in the patch regarding shots when entering crates.

    Crate Shot
    We’ve added a slight delay to when 47 can fire a weapon after closing a crate. This is to prevent accidental deaths that can occur if a player opens a crate with a weapon equipped and then ‘double clicks’ to pick up an item. This would result in them retrieving the chosen item and potentially firing their weapon into the crate and possibly setting off an explosive (if the crate contained an explosive item) and killing themselves. And we don’t want that.


  • Noticed an issue when opening some doors, causing 47’s character model to warp out of shape.


  • Noticed an issue with shadows and lighting on 47’s head when wearing the Public Enemy Suit.




  • This is more of an observation than a bug, but I thought I would share. It seems we didn’t receive a new challenge and relative unlock for August despite the roadmap suggesting otherwise.
  • A shame, given that there are still a handful of unlocks we don’t have available (e.g. Black Winter Suit, Stadia exclusives IO promised would be free to all a while back, etc.).

    Stadia Exclusive Items

    When we launched HITMAN on Stadia, we included platform-exclusive items that were unlocked by playing each game from the World of Assassination trilogy; The Sunset Rubber Duck, Orange Pinstripe Briefcase, and White Sunset Suit.

    Due to how these items were distributed to Stadia players, they will not be part of the Stadia Progression Carryover. However, we are committed to making all of these items available to all HITMAN 3 players on all platforms in a future patch.



  • Noticed some floating vehicles in Mumbai.


  • Noticed an NPC clipping through the floor in Ambrose Island.


  • Noticed an alert banner across the middle of the mini-map.


  • Noticed some gaps with NPC animations and their respective items, like this soldier in Marrakesh.


  • Noticed NPCs clipping through the environment during certain animations.


  • Noticed odd shadows on the face of one of the “Surgeon” elusive target character models.


  • Noticed NPC model clipping issues like duplicate ankles and “fused” characters on multiple maps like Bangkok and Isle of Sgail.


  • Noticed see-through gaps at the ankles of an NPC in Sapienza.


  • Noticed sunglass lenses are not reflected on several reflective surfaces in Dubai.


  • Noticed discrepancies in the textures of vehicle interiors across several maps.


  • This bug occurred on the Whittleton Creek map, causing 47 to stand up inside an exit vehicle when completing a contract.


  • This bug occurred on the Haven Island map, causing birds to dive into the ground and bounce back up.


  • This bug occurred on multiple maps, causing visual issues on helicopter propellers when exiting missions.


  • This bug causes weapons to clip through floors on multiple maps.

    Below are more examples, but even more could exist.

    Screenshots


  • This bug occurs on the Chongqing map, causing certain objects to float.


  • This bug occurs on the Hokkaido map, causing a poisoned NPC to react with ‘unpoisoned’ behavior.


  • This bug occurs on the Haven Island map, causing clipping of 47’s character model within the picture-in-picture window.


  • This bug occurs on the New York map, causing a door to lock itself each time 47 unlocks and passes through it.


  • This bug occurs on multiple maps, causing pop-in issues for certain objects.


  • This bug occurs on multiple maps, causing 47 to disappear when vaulting certain areas.

    Patch 3.170

    Invisible assassin
    Agent 47 was able to turn completely invisible whilst vaulting in certain areas of the Freedom Fighters mission. His powers have now been restrained and this should no longer occur.


  • This bug occurs on the Mumbai map, causing a disguise bag to float after subduing a guard NPC near a ledge.


  • This bug occurred after entering Hitman Freelancer mode and returning to the main menu, causing the tiles above the ‘Load Game’ tile to disappear.


  • This bug occurs on multiple maps, causing different mini-map issues.


  • This bug occurred on the New York map, causing an NPC unaware of 47 to notice a distraction shot as a crime.


  • This bug occurred on the Berlin map, causing 47 to bend down when retrieving a stash pickup that is at chest height, depending on the camera angle.


  • This bug occurred on the Berlin map, causing a guard NPC to greet 47 as Salvatore Bravuomo while disguised as Rolf Hirschmüller.


  • This bug occurred during multiple contracts, causing the mission score to show an online level of zero.

    Below are more examples, but even more could exist.

    Screenshots


  • This bug occurred on the Berlin map, causing a poisoned NPC to relieve themselves in an occupied bathroom.


  • This bug occurred on the Dartmoor map, causing certain ‘clutter’ objects to fail to spawn during specific missions.


  • This bug occurred on the New York map, causing NPCs to have what seemed an impossible awareness of a crime committed at a distance.


  • This bug occurred on the New York map, causing a legal item to alert NPCs and be considered a crime after being thrown multiple times.


  • This bug causes ‘see-through’ gaps on the ankle, wrist, and neck areas of certain suits and disguises.


  • This bug occurred on the Dartmoor map, causing a stash location to be unavailable in The Dartmoor Garden Show and available in related missions.


  • This bug occurred on the Dubai map, causing NPCs to either become hostile or ignore 47 after committing a crime.


  • This bug occurred on the Berlin map, causing a visual glitch on NPCs and 47’s character model when passing through a specific door.


  • This bug occurred on the New York map, causing a seated NPC to stand up and clip through a chair when alerted.


  • This bug occurred on the New York map, causing an NPC who witnessed a crime to fail to become a witness.


  • This bug occurred during The Collector - Year 3, causing 47’s character model to clip through the roof of a vehicle.


  • This bug occurred when planning for The Collector - Year 3, causing an issue with the lenses on the target’s glasses.


  • This bug occurred on the New York map, causing an issue with the reflection of a floor sign.


  • This bug occurred during The Showstopper on the Paris map, causing pop-in issues for certain NPCs.


  • This bug causes certain disguises with holsters to be without firearms.


  • This bug occurred when holding a one-handed weapon and briefcase, then swapping to a two-handed firearm from our back.


  • This bug caused the Concept 5 pistol to use silenced sound effects despite not being a silenced weapon.


  • This bug occurred during Ludonarrative Dissonance and The Source on the Bangkok map, causing NPCs to clip through one another.


  • This bug occurred in the main menu on multiple tabs, causing an infinite loading wheel issue on certain tiles.


  • This bug occurred on multiple maps, causing clipping issues on certain NPC wardrobes.

    Below are more examples, but even more could exist.

    Screenshots


  • This bug caused the title for The Gluttony Gobble to change once selected.


  • This bug occurred on the Santa Fortuna map, causing the tattoo sleeves to not appear when wearing the P-Power disguise.


  • Certain suits and disguises with capes have clipping issues and irregular physics behaviors.


  • This bug occurred during level three of The Genera, causing the boat start location to be locked out.


  • This bug caused the Brine-Damaged SMG to be impossible to select, as a concealed weapon for load-outs, despite being a one-handed weapon.


  • This bug occurred during The Delgado Larceny, causing issues with the ‘prompt’ for picking up the El Matador from its safe.


  • This bug occurred during level three of The Aelwin Augment, causing the mission rating to show four stars despite getting Silent Assassin.


  • This bug caused neck seams on 47’s character model when using certain suits.


  • This bug caused clipping and transparent textures on certain suits and disguises.

    Below are more examples, but even more could exist.

    Screenshots


  • On the Xbox online store, the “Makeshift Pack” has a screenshot of an explosive device. However, the description doesn’t list such an item nor is one unlocked in-game.


8 Likes

Any Featured Contract with a misspelled title (purposely or on accident) is a result of the person who submitted it, misspelling it. ioi doesn’t spell check the submissions.

8 Likes

In all the escalations and elusive targets of Chongqing the player could destroy the ICA data core with Olivia coming out from nowhere. This might not be a bug but it’s surely a negligence.

4 Likes

The signature suit with gloves also doesnt rain and the tattooist disguise also doesnt show its sleeves. I also dont want to become a clone of that guy but 47 still uses a weird early version of his head on season 1 disguises and the raven suit, with him still using the hitman 2 head on craig black. Another thing is that certain traits dont show up on descriptions, the ICA shotguns and brine damaged smg dont show up as suppressed even tho i think even the smg is. The kalmer bug and various other target ko bugs arent fixed, but idk if its possible to fix that without breaking other stuff. The midnight black suit bug in mendoza still isnt fixed, do they not know about it? The websites dont update nearly as often. Another bug that was never fixed is that you still cant take a shotgun with you as a concealed item or in a hidden stash. You should be able to do this, IO tried implementing it but it created a bug where it wasnt concealed and thus 47 would take it out immediately upon entering the level, so it was reverted back but i’d like to see them try to implement it properly. Another thing which is kind of a bug kind of not is that the Hitman 1&2 levels still use his old face models in starting locations, itd be nice to update these to make then more consistent as well as updating the text of the starting locations to no longer say “undercover as” and instead have the uniform titles just of the area name of the later games
Edit: is the buccaneer illegal in the church still? If not heres another one: you cant check in with the polar suit

1 Like

Last time they tried, it broke the legal KO of the Kalmer (which made it useless).

3 Likes

I think that only applied to targets and was probably done to prevent people from using the tranq-then-shoot exploit.

2 Likes

That Tranq/Gun glitch still exists! That’s what I was talking about. ioi tried to fix that, but couldn’t.

They DID fix the fire extinguisher explosion/accident kill (they tried to fix both at roughly the same time). But like I said, they couldn’t figure out how to make their system distinguish between a regular Tranq KO (legal + retains SA when a body is found) and the Tranq/Gun Glitch/Bug/Exploit (illegal + should void SA).

2 Likes

IO have never tried to fix it - in fact during the HITMAN 2 era, they outright stated on one of the livestreams on Twitch that it would never be fixed. They also said that they know how to fix it but the fix would break too many other things in the game, creating additional work to then fix those issues, that it was deemed to be “not worth it”.

This was right after they had finally fixed the SA “rules” in H2 that were broken for eight months and took a lot of time to get working again, so I’ve always assumed that this system was one of the things that would be broken. They wouldn’t want to break something that had just been repaired after eight months.

1 Like

First mentioned in the “Known Issues” section of the patch notes (specifically pointing out the Tranquilizer aspect) here:

  • The SA rating can still be earned when the body of a target who has been tranquilized and then killed immediately afterwards has been found.

Followed by this:

The SA rating is not failed when a dead body is found, if a tranquilizer was used before the lethal kill
Status: This is an issue with many components and we are still investigating a fix that doesn’t have other impact on the systems that are affected

Which eventually lead to this for the final Hitman 2 patch:

  • The SA rating is not failed when a dead body is found, if a tranquilizer was used before the lethal kill
    Status: This is an issue with many components and to avoid creating any further issues, we have decided to place this issue in the HITMAN 2 backlog.

But according to you, they never tried to fix it!? Ok. :joy:

2 Likes

There’s a difference between knowing about an issue and doing some investigation compared to actually actively trying to fix it.

3 Likes

You seem to view coding as like plumbing, where a physical act has to be done in order for fixing to be attempted. Whereas when it comes to code investigating the code and the various parameters of it and seeing how this system would affect this system and so on is trying to figure out a way to fix it. Do they need to edit a line actively in order to have done any work?

3 Likes

Update

  • The original topic has been updated and refreshed for Patch 3.160.
1 Like