What’s wrong with .ml posts?
@lemmy.ml
What’s wrong with .ml posts?
2, I upset my partner and feel anxious about it
All of them?
This is a good answer. Too bad people are downvoting it for the reasons mentioned.
I exclusively drink sparkling water
Detective game where you have to find plausible explenations for paranormal events
Piss and Poo, at it again (sorry)
Yummy mossy mommy
There’s already beans in this so probably more beans :)
I use LocalSend, I wouldn’t call it “sketchy” although it is a “file uploader” app.
I miss her :(
Love the vibe + colors. Not 100% sure what’s going on but it looks painful
Chi Minh
in sha' allah
They still put drm in the games sold on their store though.
You should probably ask over here as well: https://github.com/FraserLee/bevy_sprite3d/issues I havent used this library before but I might take a look once Im out of the bath
ok so I'm out of the bath.
#[derive(SystemParam)]
pub struct Sprite3dParams<'w, 's> {
pub meshes : ResMut<'w, Assets<Mesh>>,
pub materials : ResMut<'w, Assets<StandardMaterial>>,
pub images : ResMut<'w, Assets<Image>>,
pub atlases : ResMut<'w, Assets<TextureAtlas>>,
pub sr : ResMut<'w, Sprite3dRes>,
#[system_param(ignore)]
marker: PhantomData<&'s usize>,
}
It seems like Sprite3dParams is already accessing Assets<TextureAtlas> which is why you get the the error.
So you need to either remove texture_atlases or sprite_params. in your system.
have you looked at this example? I won't be much help sorry :(
thanks for using Leebra!
go to feed...