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

Visual shader inspector panel always collapse on value change #81481

Closed
bitinn opened this issue Sep 9, 2023 · 4 comments · Fixed by #95149
Closed

Visual shader inspector panel always collapse on value change #81481

bitinn opened this issue Sep 9, 2023 · 4 comments · Fixed by #95149

Comments

@bitinn
Copy link

bitinn commented Sep 9, 2023

Godot version

v4.1.1.stable.official [bd6af8e]

System information

Godot v4.1.1.stable - macOS 13.5.0 - Vulkan (Forward+) - integrated Apple M2 Max - Apple M2 Max (12 Threads)

Issue description

When editing visual shader's flags and modes under inspector, its panel always collapse after any single value change, making the process of testing values very cumbersome. See attached video.

https://streamable.com/v6w47s

I tried other nested panel such as world environment, they do not suffer from this issue.

https://streamable.com/056dg2

Steps to reproduce

In any new project, create a shader material then assign a new visual shader, modify its flags or modes as shown.

Minimal reproduction project

N/A, should be easy to reproduce in any project. I suspect the issue is due to visual shader recompiling after mode/flag change?

@bitsawer
Copy link
Member

bitsawer commented Sep 9, 2023

Confirmed, this happens at current master too at fc99492. Also StandardMaterial3D and ShaderMaterial seems to work normally, so looks like a VisualShader specific regression.

@jsjtxietian
Copy link
Contributor

jsjtxietian commented Oct 17, 2023

I did some quick check and find maybe it's because set these flags or modes will trigger a _queue_update which will call _update_shader, and it will emit change to ShaderMaterial::_shader_changed().

Relared to #74745

@viksl
Copy link
Contributor

viksl commented Feb 20, 2024

@jsjtxietian
Well changing the flags does change the shader so it should trigger shader change or not?
Btw changing Node3D properties such as rotation edit mode also causes the materials to fold but it does not fold Mesh resource of MeshInstance3D but it does collapse the Material (this time StandardMaterial3D). So it's not just VisualShader related.

@Chaosus
Copy link
Member

Chaosus commented Aug 4, 2024

Its a regression from #73381 cc @KoBeWi

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

Successfully merging a pull request may close this issue.

7 participants