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

Project Manager only preserves projects in the projects directory setting #90824

Closed
Spartan322 opened this issue Apr 18, 2024 · 2 comments · Fixed by #90845
Closed

Project Manager only preserves projects in the projects directory setting #90824

Spartan322 opened this issue Apr 18, 2024 · 2 comments · Fixed by #90845

Comments

@Spartan322
Copy link
Contributor

Spartan322 commented Apr 18, 2024

Tested versions

  • Reproducible in: v4.2.2.stable.official [15073af]
  • Tested but cannot be reproduced in: v4.2.1.stable.official [b09f793]

System information

Godot v4.2.2.stable - Arch Linux #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) () - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)

Issue description

I expect that if I import a project or scan project directories, the project manager would remember those projects, not just the ones in the filesystem/directories/autoscan_project_path editor setting.

But starting with 4.2.2 the project manager never recalls projects not listed in that path.

Steps to reproduce

  • Start Godot
  • Import a project not in the editor path
  • Close and restart Godot
  • See project is not in list

Minimal reproduction project (MRP)

N/A

@akien-mga
Copy link
Member

akien-mga commented Apr 18, 2024

I don't seem to reproduce the issue on Fedora 39.

I wonder if you were not running Godot 4.2.1 in self-contained mode, which makes it use a different editor settings file than others? There would be a ._sc_ file next to it if so.

Edit: Actually I can reproduce the issue after setting the filesystem/directories/autoscan_project_path setting. Thankfully I don't think it's a very commonly used setting (hard to discover), so it's not too critical. Will look for a fix for 4.2.3.

@akien-mga
Copy link
Member

akien-mga commented Apr 18, 2024

This appears to be a regression from #86271. I think it made a wrong assumption about what to do when using filesystem/directories/autoscan_project_path, seems like an easy fix.

It affects 4.3 too, reproducible from 4.3-dev1 and 4.2.2-rc1.

The workaround for affected users is to unset filesystem/directories/autoscan_project_path for now, and just scan that path manually when adding new projects to it.

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.

2 participants