

Hello!
First of all, thank you for looking into the stealth issues the game has been having!
It seems that, although the instant detection issue (where the detection meter fills up instantly) has been mostly addressed with the 1.4.2 TU, there is still another one that I have been facing a lot.
This bug causes instant detection, but does not show any detection meter: it instead triggers combat instantly, not giving me any time window to react. I believe that this bug is triggered whenever the enemy is facing a "dangerous" situation (seeing a dead body, hearing an arrow shot next to them, etc).
This bug is fairly easy to reproduce, and I have recorded a few of these instances (shown below)
This sequence is a first example of this instant detection bug: the detection meter does not show up and thus does not allow for any reaction (no slow motion). Although in this case it could be argued that it is normal, as I am assassinating a foe right in front of his partner
This sequence, recorded in the Raven Mastery Challenge of the Calleva Outpost, shows that the enemy below has heard my sleeping arrow. He is consequently put in an alerted state. This state allows him to instantly detect me without any detection meter showing up. I had again barely any time to react to his detection
The bug also happens in mistrust areas. I believe that the instant detection has been triggered by the enemy seeing the body of one of the soldiers I just assassinated (the detection meter showing up after the slow motion is of the other soldier accompanying the one instantly detecting me)
This sequence is very interesting, and has been recorded in the Raven Mastery Challenge in Scrobescire. The triggering of the bug is very consistent here (worked 4 out of the 5 times I tried it): all you have to do is whistle from the haystack (thus distracting the enemy near the haystack and the one above) and assassinate the enemy. And again, I was instantly detected and had no room for any reaction, although the detection meter never filled up
Could you please confirm that this is indeed a bug and not intended behaviour? If so, is it a bug that you will be or are already looking into?
Let me know if you need any more footage of this bug occuring
Thank you!
Hi @ubi-keo
Sorry to bring up an old topic
Do you have any news to share regarding this issue and if this is something you are still looking into?
Thank you!
Hi @ubi-perseids
Sure! I hope you don't mind the German
@ubi-oxavo Hello and thank you for your response!
It seems like after returning to their location again, they reappeared. Restarting the game seems to have done wonders!
However, their icon still doesn't appear on the map, as you can see in the video below
https://streamable.com/2yzh5i: (https://streamable.com/2yzh5i)
I also made a manual save (uploaded to the cloud) next to one of the Outrider's location, as you asked
Kind regards
Hi,
This topic is a follow-up to one of the issues I described here: https://discussions.ubisoft.com/topic/146830/dor-no-music-when-facing-roaming-bosses/8?lang=en-US
I was asked by Ubi-Froggard, from the support staff, to make a separate topic regarding this specific issue
The issue I am currently having involves Suttungr's Outriders no longer appearing on the map since TU 1.5.1. Their icon do not show up and they do not seem to spawn when I travel to the locations they are supposed to be
I have completed several "Dwarves in Distress" world events, I did not kill any of the Outriders before TU 1.5.1, and I do not have any piece from the Jotun Armor Set
I made a manual save last week near the location of one of the Outriders, for your convenience
Could you please look into this?
Thank you!
@ubi-borealis Hi and thank you again for your response!
I do refer to Suttungr's Outriders (playing in another language tends to make me change up the names a bit)!
Although I am aware that these bosses can only be beaten once, I have never killed any of them so far and thus never collected any Jotun gear. I believe that they should still be on the map, but no longer appear: should I make another topic in the forum about this issue?
As for groups of Jotuns outside of these boss instances, there is also no music triggering. I only hear music in group encounters when there was ambient music playing beforehand (in these instances, the music switches to its "combat" variation)
Thanks!
@ubi-nacho Hello!
Regarding the roaming Muspell bosses, it seems that Title Update 1.5.1 solved the issue
As for the Jotun leaders however, I am unable to verify if your maneuver solves the issue: they no longer appear on the map and do not seem to spawn when traveling to their location since the Title Update. It must likely be another bug
I created a manual save (and made sure that it is in the cloud) if you want to have a look
Thank you!
Hi @ubi-keo and thank you for your response!
I went through all the steps listed in the article you linked (GPU drivers up-to-date, Windows up-to-date, verifying the game files, etc) and I can confirm that it did not solve the issue in the aforementioned instances (Muspel roaming bosses, Jotun leaders, arena fights)
I always have had issues with the game's music: music rarely playing, lack of music variety (an issue I made a post about a few months ago). So I wonder if this is an issue tied to my saves affecting everything music related?
Hello,
I have an issue in which music does not start when I engage Jotun warriors in events like "Dwarves in distress" or "Kill Jotun leader".
https://streamable.com/gywfvn: (https://streamable.com/gywfvn)
I also have no music in Kara's Arena, but I am not sure if it is intented.
I have a similar issue when facing roaming Muspel bosses, but this time the music only starts to then end abruptly after a few seconds.
https://streamable.com/g9fflp: (https://streamable.com/g9fflp)
Could you please look into this?
Thank you!
Hello @ubi-milky and thank you for your response!
I was wondering if you had the opportunity to look into this issue since our last exchange?
Have you been able to reproduce the issue and can we hope for a fix in the future?
Thank you!
Hello!
First of all, thank you for looking into the stealth issues the game has been having!
It seems that, although the instant detection issue (where the detection meter fills up instantly) has been mostly addressed with the 1.4.2 TU, there is still another one that I have been facing a lot.
This bug causes instant detection, but does not show any detection meter: it instead triggers combat instantly, not giving me any time window to react. I believe that this bug is triggered whenever the enemy is facing a "dangerous" situation (seeing a dead body, hearing an arrow shot next to them, etc).
This bug is fairly easy to reproduce, and I have recorded a few of these instances (shown below)
This sequence is a first example of this instant detection bug: the detection meter does not show up and thus does not allow for any reaction (no slow motion). Although in this case it could be argued that it is normal, as I am assassinating a foe right in front of his partner
This sequence, recorded in the Raven Mastery Challenge of the Calleva Outpost, shows that the enemy below has heard my sleeping arrow. He is consequently put in an alerted state. This state allows him to instantly detect me without any detection meter showing up. I had again barely any time to react to his detection
The bug also happens in mistrust areas. I believe that the instant detection has been triggered by the enemy seeing the body of one of the soldiers I just assassinated (the detection meter showing up after the slow motion is of the other soldier accompanying the one instantly detecting me)
This sequence is very interesting, and has been recorded in the Raven Mastery Challenge in Scrobescire. The triggering of the bug is very consistent here (worked 4 out of the 5 times I tried it): all you have to do is whistle from the haystack (thus distracting the enemy near the haystack and the one above) and assassinate the enemy. And again, I was instantly detected and had no room for any reaction, although the detection meter never filled up
Could you please confirm that this is indeed a bug and not intended behaviour? If so, is it a bug that you will be or are already looking into?
Let me know if you need any more footage of this bug occuring
Thank you!