Survivor slowdown bug vs Doctor (And other killers)

i think he just had nothing but misery; in the screen it shows a hex which therefore implies he had that perk on. nothing but misery but it has a condition that can only be satisfied by hitting any survivor 8 times which in turn makes a dull totem a hex totem and the killer gains the ability to give hindered status effect for 15 seconds every time he hits a survivor which only applies to the survivor that was hit.

It looks more like a collision issue here. Some places on different maps slow down both survivors and killers in random moments without obvious reason

I can't be sure because you don't have an overlay showing your FPS, but this looks identical to setting bUseFixedFrameRate=True in Engine.ini, which people do for an increased FPS limit beyond 120. This has the byproduct of lowering your game speed whenever you fall below whatever you set FixedFrameRate to in the Engine file (in-game FPS settings are ignored when doing this).

This happens because this "fps uncap" method is tying your game speed to your frame rate rather than actual time, meaning at a 180FPS cap, the game thinks each frame is 1/180th of a second, regardless of if you're actually getting 180 frames per second or not. Some real world examples; if your cap is 240FPS and you're only getting 120FPS in-game, most things in-game from your perspective will move at half speed, resulting in a speed difference between you and other players. This is also true for smaller FPS drops, say going from 180 to 120, or even 180 to 160, where you'll be slowed down by 30% and 12% respectively, both of which are very noticeable.

If you've followed any "optimization" or "uncap fps" guides, a lot of them tell people to do this without giving much explanation of the downsides, assuming everyone will set it to a number they'll never fall below, even though the vast majority of players don't have hardware that can actually run DBD without ever dropping below 120FPS against any killer in the game (doctor and dredge are actually the two killers that exemplify this the most, both being very expensive to render, causing an FPS drop that's not as perceptible in normal gameplay, but kills you when using fixed frame rates).

If this is actually the cause, to fix it, paste %localappdata%\DeadByDaylight\Saved\ into windows search, open up EGS for Epic Games Store, WindowsClient for Steam, or WinGDKClient for MSStore/Xbox PC, right click your Engine.ini file, uncheck read-only, and delete the [/Script/Engine.Engine] section, which isn't included normally and would only be present with a modified Engine.ini. If you're not comfortable editing it, you can delete the file and the game will recreate it for you the next time it's launched, but you'll lose any other modifications you've made, e.g. disabling mouse acceleration/smoothing/enabling raw input.

Little side note as I assume ThatRyanB will read this since he's already in this thread, if you could mention recent interest in an increased FPS limit to UX, that'd be very much appreciated. People have been asking for this for a long time, and community members, notably even Hens, have made tutorials on how to exceed the 120 FPS cap using this method. I recognize there are a lot of other things on the team's plate right now, however it would be amazing if we could get this in-game some time next year, even under Beta options as an Unlimit FPS checkbox at first, while the fringe issues are still being ironed out. Myself and a lot of others would take this over the majority of the 9.3.0 UX changes combined, despite how wonderful those are!