Open guilhermefelipecgs opened 4 years ago
CC @clayjohn
Yea that looks like the same issue. I will press reduz about it more, as I still don't understand what is broken and why my PR fixes it.
Just a note, BakedLighmap is also affected:
@guilhermefelipecgs Can you still reproduce this in the latest master
branch with VoxelGI, and with the new GPU lightmapper (LightmapGI)? You can download a nightly build here.
Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.
The bug is still there (VoxelGI), even worse when entering in orthogonal view now.
https://user-images.githubusercontent.com/1387165/152700307-4baa2bc6-7a03-4b79-83e0-32e231c3e700.mp4
Minimal reproduction project updated to v4.0.alpha1.official giprobe_test.zip
On the other hand, looks like the LightmapGI has been fixed.
https://user-images.githubusercontent.com/1387165/152700147-4242ecd5-2cf4-49d5-b38f-1dd26ba8aca9.mp4
Godot version: master (495b28765d03aa9459bc312ebba190ec208979e7)
OS/device including version: Arch 5.6.4-arch1-1
Issue description: GIProbe are generating different results depending on the position of the object inside giprobe's cage: Rotating the object also affects the calc (happens in 3.2.1 as well, maybe is related to #35200): cube was rotated and rebaked
Steps to reproduce: I exported a cube with inverted normals from blender. I setup 3 spot lights for each cube. Then I bake giprobe with interior on and light intensity to 8.
Minimal reproduction project: giprobe_test.zip