search

FraserLee / bevy_sprite3d

Use sprites in a 3d bevy scene.
MIT License
144 stars 22 forks source link

Unable to use versions before 2.8.0 #17

Open Kaendor opened 8 months ago

Kaendor commented 8 months ago

Hi,

While I wait for some crates to adopt bevy latest version (0.13), I have to keep my game running before updating.

However for some reasons when I want to use your crate with the version 2.7.0, it uses the 2.8.0 version and create a bunch of problems with incompatibilities.

Maybe it's because there is no tag branch and only main...

Have a great day, thanks!

FraserLee commented 8 months ago

Hi, thanks for writing! That sounds like a really weird issue, I'd love to help solve it.

I've checked on crates.io, and it doesn't look like anything had overwritten 2.7.0 (for bevy 12) when 2.8.0 (for bevy 13) was released. The obvious first thing I'd suggest would be to clear out your packages cache to force cargo to completely redownload everything, then rebuild from scratch just in case something's messed up inside the system. If specifying bevy_sprite3d = "2.7.0" isn't enough, you could also use an exact commit hash with rev (though I can't imagine why the normal package version resolution wouldn't work).

Beyond, that I'm really not sure where things could even be going wrong. If your editor has the capabilities, maybe try to jump to code in the crate. You'll probably get a path looking something like

~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_sprite3d-2.7.0

if possible, could you check the version in the Cargo.toml inside that directory - just to be certain of the issue?

If you have any other info about your project, too, that could help; things like if you're including bevy_sprite3d directly in your Cargo.toml, or if it's a dependency of a dependency.

Kaendor commented 8 months ago

My first idea was to cargo clean , and indeed use and exact commit rev. Except before 0.13, bevy main branch was followed and when I use a rev it's needing bevy-14-dev as a result.

I use your crate as a direct dependency of my project.

I check with cargo tree and bevy-13 is pulled by bevy_sprite3d 2.8.0.

FraserLee commented 8 months ago

I'm a little bit confused by this line

I check with cargo tree and bevy-13 is pulled by bevy_sprite3d 2.8.0

Just to make things completely clear, you're trying to use bevy = "0.12" with bevy_sprite3d = "2.7.0", right? 2.7.0 is the version for bevy 12, and 2.8.0 is for bevy 13. There's really no reason that setup should have any entry for bevy_sprite3d 2.8.0 when you run cargo tree.