Ray Tracing is beyond broken in 4.23

[John_Alcatraz]

@Juan_Canada

• When ray tracing effects are disabled (r.RayTracing.ForceAllRayTracingEffects is set to 0), there is still some ray tracing work done. In fact it has been like that from the beginning but now that in 4.23 we support heavier geometry types such landscapes or HISM this is more evident. This will be improved in the near future, hopefully in the first 4.23 hotfix

Independent from the question if disabling raytracing will make the cost go away, having GenerateVisibleRayTracingMeshCommands take 18 ms of time for a bunch of grass does not sound too ideal, as that means it’s quite impossible to use it with foliage, right? Is this just an early implementation that can be optimized, or is there some deeper problem with foliage that makes it very slow to process for RT?