Its a super annoying and frustrating issue and its tough to see the bigger picture, if it feels like its a very common issue and yet there seems to be no answer as to why its happening.
We might all just share the same type of windows setting we´re not aware off…
Bit off topic, but I recently found the cvar that culls raytraced shadows at a distance, something that I´ve been struggling two figure out since I started using Unreal two years ago and could not find ANY info or tip anywhere that helped.
Seemed like its an absolutely unavoidable problem with Unreal being a game engine, so I had already given up and then there it was:
r.RayTracing.Culling 0
Boom. Problem gone.
Same with godrays.
Couldn´t figure out why I couldn´t get godrays anymore.
r.VolumetricFog.InjectRaytracedLights 1
Boom. Problem gone.
Its possible that we all followed ONE tutorial that gave ONE tip in the project settings that now makes it crash.
Or some other thing we share, like a certain windows build.
Lets hope its an Epic problem or a DirectX problem and we get that fix automatically at some point.
Limiting frame rate is still a …limiting “fix”, as it doesn´t just limit your frane rate to a comfortable 25fps, it also makes things slower than 25 fps occasionally on heavy scenes, that would still have fps in editor that would be workable, if it weren´t limited…