I think it's missing the plane light probe display.
Yes, I didn't know that one had to be implemented too!
I would go with show_data_display_size
, to avoid breaking the Python API.
I think having 2 different Python properties that change the same flag is going to be quite confusing for Python users.
I am a bit unsure if we want this to be on the material. I think it depends much on the geometry.
The amount of displacement is always driven by the material itself (unless using an attribute…
IIRC, some preprocessors freak out when there's a directive and a comment in the same line.
I've only skimmed the actual scan implementation, but the results look fine, so I'd assume it's fine. XD
I haven't really noticed any visual issues.
Since 80a8368b88, there's no way to set the AO distance from the UI!