Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconection betwen Gizmo and inspector values on BakedLightmap #45317

Closed
Janders1800 opened this issue Jan 19, 2021 · 7 comments
Closed

Disconection betwen Gizmo and inspector values on BakedLightmap #45317

Janders1800 opened this issue Jan 19, 2021 · 7 comments

Comments

@Janders1800
Copy link

Godot version:

3.2.4-beta6

OS/device including version:

Zorin OS 15

Issue description:

If you change Extents in the Gizmo it does not reflects on the inspector.
GizmoBug
@JFonS related: #44628

Steps to reproduce:
Add a BackedLightmap node and change its extents with the gizmo.

Minimal reproduction project:

No need.

@Calinou
Copy link
Member

Calinou commented Jan 19, 2021

A change_notify("extents") call was likely missed in the gizmo code.

@Calinou Calinou added this to the 3.2 milestone Jan 25, 2021
@akien-mga akien-mga changed the title Disconection betwen Gizmo and inspector values on BackedLightmap Disconection betwen Gizmo and inspector values on BakedLightmap Jan 25, 2021
@Bhu1-V
Copy link
Contributor

Bhu1-V commented Jan 27, 2021

I actually tried to fix this, but I didn't see neither the gizmos nor those values available in the inspector. using this version ad0f1c6

@Calinou
Copy link
Member

Calinou commented Jan 27, 2021

I actually tried to fix this, but I didn't see neither the gizmos nor those values available in the inspector. using this version ad0f1c6

The master branch has a different GPU-based lightmapper which doesn't have a notion of extents. You need to test this with the 3.2 branch on a different project.

@TamplierS1
Copy link

Hi, I fixed this by adding _change_notify("extents") to _update_gizmo() method in Spatial class. Do I create a pull request to 3.2 branch or master branch?

@Calinou
Copy link
Member

Calinou commented Jan 27, 2021

Hi, I fixed this by adding _change_notify("extents") to _update_gizmo() method in Spatial class. Do I create a pull request to 3.2 branch or master branch?

To me, it seems too "general" to add this to the Spatial class. Solutions must be local, so the fix should be applied to the BakedLightmap class.

Also, since BakedLightmap extents only exist in Godot 3.2.x, the pull request should be opened against the 3.2 branch.

@TamplierS1
Copy link

Okay, I moved _change_notify("extents") to set_extents() in BakedLightmap and opened a PR on 3.2 #45510

@akien-mga
Copy link
Member

Fixed by #45510.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants