-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
Error: Couldn't load project data at path ".". Is the .pck file missing? #89825
Comments
I dug into this a little today and noticed that after 5a6adb4 my exported pck from the editor no longer contains |
5e6adb4#diff-a64507e1723f451757967d0bcb08c8e8999bc77b5d4863e9c71133432140b17fR1798 changing this to |
Sounds like the way you are exporting (or an error in the code) is creating a non-main PCK rather than a runnable one. My understanding is that in the export dialog "Export Project" makes a full PCK (with the project file and icons and such) and "Export PCK/Zip" is intended to make content-only PCKs (suitable for DLC). Source (assuming I'm interpreting correctly) https://docs.godotengine.org/en/stable/tutorials/export/exporting_projects.html Are you doing Export Project? |
That's a misinterpretation, "Export PCK/Zip" should (at least by default) export the exact same PCK file that "Export Project" would.
With such a PCK, you can run Godot with |
I'll admit to having missed this use-case as well, but I see now that it's also quite clearly spelled out under "Export approaches" on the "Exporting for dedicated servers" page:
This is somewhat of a quick kneejerk fix, and largely untested, but it seemed like a straight-forward and reasonable compromise: #89928 Let me know what you think in the PR. |
I got this issue while doing normal Exports (no separate pck export, and it should produce same pck as commented above anyway), but only when using certain names for folders and binary, such as: I checked the file commits for the fix but I don't see an obvious cause of how path usage affects the result. Should I just trust that this fix will also fix these particular export path naming? In fact, I got a copy of Godot 4.3 dev 6 and just tried it, I cannot repro - but at the same time Godot 4.3 now generates fully hyphenated project path names by default for extra safety, so it's hard to tell. I cannot switch version right now (middle of jam, need something stable), so I'll just avoid long export path names. |
I got this bug when compiling using |
Tested versions
System information
Godot v4.3.dev (fe01776) - Void #1 SMP PREEMPT_DYNAMIC Fri Mar 8 01:01:43 UTC 2024 - Vulkan (Forward+) - dedicated AMD Radeon RX 7900 XTX (RADV NAVI31) () - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)
Issue description
Getting
Error: Couldn't load project data at path ".". Is the .pck file missing?
when running a build of the engine in same directory as the same named pck. Same error when using --main-pack.git revert 5e6adb4a2dd947432e59ca00b6d046a68c534e10
fixes the issueSteps to reproduce
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: