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
"default" Asset library path is incorrect, crashes on start #1331
Comments
Another issue, which might be related to this: unembedded assets are not loaded and result in a crash. I'm calling The id "textures/perlin.png" is eventually passed to Embedded assets seem to be loaded fine. |
It seems like the second problem happens because the basePath in AssetManifest is set to |
I also, seemingly suddenly, hit this issue. Using the proposed fix: if (path == "/manifest/default.json") {
path = "manifest/default.json";
} in This was an app that was previously working, i did do an Cheers, |
I had the same issue on a Windows system that was updated to hxcpp 4.0.19. The app would compile and run fine on Linux and neko (Linux and Windows), but on C++ it would show a message box complaining about missing My fix was to go back to hxpcpp 4.0.8 (that's the version I had running before, there might be later versions that also fix the issue) edit: I should mention I used Haxe 3.4.7 |
I can confirm @AlexHaxe's solution. Reverting back to |
I just found that this only happens when latest hxcpp is used together with Haxe 4.0.0-rc.2 or earlier. Hxcpp 4.0.19 seems to work fine with rc.3. |
This has been fixed in hxcpp: |
Hello,
Getting the following error:
[lime.utils.Preloader] ERROR: There is no asset library with an ID of "default"
when trying to start a Lime application (porting an existing game engine to a newer Lime).Native target, Windows, develop branch.
Traced down the problem to
Assets.loadLibrary
, which setspath
to "/manifest/default.json". Adding a line that changespath
to "manifest/default.json" (without the leading slash) before callingAssetManifest.loadFromFile
fixes the issue.I'm not sure what is the actual cause of this bug, so I can't provide a meaningful pull request at this point.
The text was updated successfully, but these errors were encountered: