I found an issue with using automatically generated ranges for custom probes. This short video clip describes how to reproduce the issue: https://www.youtube.com/watch?v=cPvC4bY5A7Y Hope you will be able to reproduce the issue on your side and find a fix. The workaround is to specify ranges manually...