This is a bug with screen traces, Iâve also encountered this and it seems to just miraculously fix itself on occasion. If you can figure out how to reproduce it I would encourage you to submit a bug report for it.
I see, yeah I actually fixed it somewhat by playing with âr.Lumen.Reflections.HierarchicalScreenTraces.MaxIterationsâ and âr.Lumen.Reflections.HierarchicalScreenTraces.UncertainTraceRelativeDepthThresholdâ in the console command. It brought back the reflections but added itâs own issues a bit.
Thatâs what you get working in a beta version I guess! Thanks for your reply.