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

Ctrl+S does not save resources in *[unsaved] scenes #45611

Closed
lyuma opened this issue Jan 31, 2021 · 3 comments
Closed

Ctrl+S does not save resources in *[unsaved] scenes #45611

lyuma opened this issue Jan 31, 2021 · 3 comments

Comments

@lyuma
Copy link
Contributor

lyuma commented Jan 31, 2021

Godot version:
4.0.dev c9413b513fd2fb95e9b71d886e01a04e379bb969

OS/device including version:
Windows 10.0.19041.746
Nvidia RTX 2080 Ti driver 452.06

Issue description:
Ctrl+S saves resources but only if the current scene can be saved, so either [empty] or a valid scene. (not [unsaved], and not opened .glb files or such things)

Ctrl+Alt+S (Save All Scenes) always saves resources but does not notify the user of this fact.

Similar to issue 9069, but this problem deals with all resources (such as Environment), not just scripts.

Steps to reproduce:

  1. Create a new project or open existing
  2. Double click default_env.tres
  3. Expand Sky. Then, in the Sky fleld, click Sky to expand the sky object.
  4. In the Sky Material box, create a new PhysicalSky
  5. Press Ctrl-S
  6. Quit to Project List and reopen.
  7. The default_sky.tres was not saved.

Minimal reproduction project:
Happens in a new project

@Calinou
Copy link
Member

Calinou commented Jan 31, 2021

Related to #45601.

@KoBeWi
Copy link
Member

KoBeWi commented May 6, 2022

Can't reproduce in alpha7.
When scene is [empty], the resource is saved correctly.
When scene is [unsaved], you are prompted to save the scene. The resource is saved if you do so and not saved when you cancel.

So I guess the issue is resolved?

@YuriSizov
Copy link
Contributor

Closing due to no response. Let me know if it's still reproduceable so I can reopen it.

@YuriSizov YuriSizov closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants