When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
PC - HUGE Graphic bug for basement
Steam - PC/Laptop
CURRENT BUG: https://youtu.be/H9rlgcpQuHo
Excuse the quality please, I play on a laptop and it doesn't play nice with OBS. The game has steady frames normally and runs just fine so before anyone suggests my specs don't match I promise they're within range and it only hiccups during bugs like this one. The game runs just fine besides this, it's really random about when it decides to do it. I think for the recording it's specially this map variant (LD63) since I'd tried this a match before (customs with bots) and didn't get it on the Pale Rose. I think it's particular to certain RNG of where the basement spawns in the main buildings/shack. I have had similar on the Autohaven maps, Macmillan maps, and I believe the Chapel map. If I manage to come across it in different locations and map variants I'll add video of those as well.
Fun fact:
I can still hook and open lockers just fine as killer (shown in recording) and I can open the chest or hide as survivor. There's no collision issues etc, just the weird glowing/neon effect. This has crashed my game multiple times since it's very intense on my laptop. I run the game using launch option -dx12 on Steam to help with a completely DIFFERENT graphics bug (https://youtu.be/YpegF_lfL9k) so maybe the two are tied together? I'm not sure though, it's just really obnoxious to deal with. Please fix this I just wanna play without worrying about the penalty or losing a fun match to a crash :o(
Adding a screenshot of another map variant of the same issue. You can see the glowing in the background of the screenshot, this was under the main building where basement was.
Added another map variant (Saloon_141 I believe) as well as a screenshot from inside the basement of that map. It's also shown here in this video: https://youtu.be/hIe97_Y3a30 as well as two other bugs I've seen in the past week.
