@FollonSaxBass
This was supposedly fixed in 6.0 or 6.1 (introduced in 5.0)…no one has confirmed it’s actually fixed (yet). Are you seeing it on 6.1 or 6.2?