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

Can't run scene with .res or .tres extension #35709

Closed
RockyMadio opened this issue Jan 29, 2020 · 8 comments · Fixed by #38515
Closed

Can't run scene with .res or .tres extension #35709

RockyMadio opened this issue Jan 29, 2020 · 8 comments · Fixed by #38515

Comments

@RockyMadio
Copy link

RockyMadio commented Jan 29, 2020

Godot version:
3.2 ( from 3.1)

OS/device including version:
Windows 10

Issue description:
Play scene - buttons do not work as intended (F5 and F6, and Ctrl+Shift+F5)
Our project runs flawlessly in 3.1. However by clicking any of those, the latest 3.2 will always play the default scene (in the config) .

Removed the path in default scene setting, F6 and Ctrl+Shift+F5 will launch the default Godot project manager (list of launchable projects). F5 will ask for scene.

Changing the default scene with another scene will temporarily fix the issue. But it will repeat again as you want to F6 one another scene.
Steps to reproduce:
I am not sure how to reproduce this. A new project will not show this issue. But our project has already reached a big scale. There must be some conflicts in one of the conflig files. Please help :(

You would reproduce the bug like this : Create 2 scenes, A and B, make A default scene, close A, and F6 with B. if the game runs with A, it is the bug.

@KoBeWi
Copy link
Member

KoBeWi commented Jan 29, 2020

What happens if you replace project.godot with an empty one?
It cold be some autoload node changing the scene.

@RockyMadio
Copy link
Author

I tried, and it still shows the same issue. The empty project just lets me reset the default scene. As I repeated all steps mentioned above, It still does not change.

@RockyMadio
Copy link
Author

RockyMadio commented Mar 5, 2020

This issue occures when you have level scenes as .res, changing them to .tscn will solve the problem. Most of my assets/instances are saved as .res, they still run properly.

@akien-mga
Copy link
Member

Why close it? It seems you found a workaround/explanation but the bug is still present, no?

@RockyMadio RockyMadio reopened this Mar 7, 2020
@RockyMadio
Copy link
Author

Why close it? It seems you found a workaround/explanation but the bug is still present, no?

i thought it was a mistake on my end -.- So do you think it is a bug?

@KoBeWi
Copy link
Member

KoBeWi commented Mar 7, 2020

Ok, I managed to confirm the issue. The problem is that you can't run scenes with .res extension (unless it's a main scene).

.res do appear as one of the extensions when saving scene
image
so either the bug should be fixed or the extension removed from the list.

@KoBeWi KoBeWi changed the title Conflict with default scene. Can't run scene with .res extension Mar 7, 2020
@akien-mga
Copy link
Member

While .res and .scn are exactly the same thing, I think it's likely fine to remove .res from the allowed extensions to reduce confusion. .tres is already missing even though it's also equivalent to .tscn.

On the other hand the engine itself should still be able to run scenes using .tres or .res if users do happen to force using these extensions for some reason. But if it works already with the main scene, I guess it's just the Play Scene code which adds this restriction.

@Calinou
Copy link
Member

Calinou commented Apr 29, 2020

This is likely a regression from #33149. I guess we should allow using .res and .tres to run scenes as well.

Calinou added a commit to Calinou/godot that referenced this issue May 6, 2020
@Calinou Calinou changed the title Can't run scene with .res extension Can't run scene with .res or .tres extension May 18, 2020
@akien-mga akien-mga added this to the 4.0 milestone May 20, 2020
akien-mga pushed a commit to akien-mga/godot that referenced this issue May 20, 2020
huhund pushed a commit to huhund/godot that referenced this issue Nov 10, 2020
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.

5 participants