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

CustomNode in VisualShader gets replaced with Null box #38960

Open
eiszfuchs opened this issue May 22, 2020 · 3 comments
Open

CustomNode in VisualShader gets replaced with Null box #38960

eiszfuchs opened this issue May 22, 2020 · 3 comments

Comments

@eiszfuchs
Copy link

Godot version:
3.2.0-stable (until latest beta)

Issue description:
One of the custom visual shader nodes gets replaced with Null node, rendering the shader useless.
When I saved, the shader looked like this:
20200522-151416-be3d11c8
Next time I open the project, it looks like this:
20200522-151348-a1248eb6
Initially, I was trying to reproduce an issue I had with VisualShaders in the game I'm working on, where the shader (the one that's included in the reproduction project) would show properly in the game when started from the editor, but in the exported game, the shader would render completely black and the console showed an error some function (pnoise4d in this case) would not exist, and it indeed was missing from the shader code. The generated code in the visual shader editor however would generate the shader code just fine.

So I created a copy of my project, removed everything that was not related, and my shader would export just fine now, but now I'm having issues with the shader save and load properly. I don't know if I'm chasing ghosts here, so maybe you can shed some light.

Steps to reproduce:

  1. Open the project provided
  2. Observe the screen being black in editor and a Null box in the shader.

It should render like this:
20200522-151435-a07c5239

(Please help, I'm going insane over this.)

Minimal reproduction project:
https://github.com/eiszfuchs/godot-vs-issue

@arkology
Copy link
Contributor

arkology commented May 22, 2020

@Chaosus
Copy link
Member

Chaosus commented Oct 7, 2020

Strange bug, I'm unable to reproduce it anymore to catch the sequence of action leads to it...

@eiszfuchs
Copy link
Author

I haven't checked out the latest versions, since some collision-related bugs blocked me from working on my game any further until I made up my mind how to deal with them. The bug might have been fixed in the meantime (there were quite a few updates since 3.2.0).

I'll try to reproduce again as well to confirm.

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

3 participants