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

Tileset Edit unavailable if shader present in a tile #36947

Closed
LeD95 opened this issue Mar 9, 2020 · 3 comments
Closed

Tileset Edit unavailable if shader present in a tile #36947

LeD95 opened this issue Mar 9, 2020 · 3 comments

Comments

@LeD95
Copy link

LeD95 commented Mar 9, 2020

Godot version: v3.2.stable.official (Standard 64-bit for Windows)

OS/device including version: Windows 7 Home Premium, 64 bit

Issue description: TileSet editing window, normally present at the bottom center of the editor becomes unavailable if any of the tiles in the tileset uses a material with a shader that was opened through inspector of a tile. For lack of better wording there will be screenshots included.

Steps to reproduce:

  1. Create a TileMap node [1] and add a new TileSet [2] to it, then click on it to enter tileset editor. (Screen_1.png)
    2, Create at least one tile for that tileset.
  2. In any of the tiles add a new material. Right now everything should be normal (Screen_2.png)
  3. Add a new shader to that material[1]. The Shader editor will now appear[2]. (Screen_3.png)
  4. If you were to click away to exit inspector for the tileset, for instance focus a different node on your scene, and then came back to the tileset, instead of the TileMap editor you will see the shader editor. It will not go away if you don't do one of two things.
    A) Restart the editor and reenter the TileSet editor.
    B) Find the tile where you edited the shader and click the blue name of the shader to close the shader editor. Then unfocus the tileset in inspector and go back into it so that TileMap appears. (Screen_4.png)

Minimal reproduction project:
Attached BugReport.zip
(though I doubt its usefulness because restarting fixes it)

Screen_1
Screen_2
Screen_3
Screen_4

@KoBeWi
Copy link
Member

KoBeWi commented Mar 9, 2020

Related to #32002 probably.

@LeD95
Copy link
Author

LeD95 commented Mar 11, 2020

Related to #32002 probably.

Sounds the same, aside from restarting godot not fixing it. Might be another issue underneath defining whether it persists or not.

@Calinou
Copy link
Member

Calinou commented Apr 9, 2020

Duplicate of #32002.

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