Timothy Bess
Timothy Bess
@StarArawn Yeah I tried adding padding in that field and it seems to completely mess up the sampling at that point. This is what happens when I add `Vec2::new(1.0, 1.0)`...
Thanks! I'll try to look into it too, but I'm a noob with graphics programming and bevy internals for that matter. Very cool what you've done here though, way better...
FWIW I'm trying to integrate ldtk and this is sort of an issue since each layer can have its own tileset. Honestly most asset collections I've seen out there aren't...
Thanks! Are they listed anywhere? There's no way I would've found this. Might be cool to put it in the readme or something?
Is there any reason why this can't be merged? His fork works perfectly for me.
Yeah I'm using both of these functions and still experiencing the issue.
Sorry about that, I'll reopen if we run into it again. In the middle of a big production release over the last month or so.
I'm getting a similar error while attempting to compile with musl target: default.nix ```nix let moz_overlay = import (builtins.fetchTarball https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz); nixpkgs = import { overlays = [ moz_overlay ]; };...
The Haskell APIs are very nice and the server side rendering/etc. all work perfectly out of the box. It's really very cool, glad to see people taking a different approach...
> Do environment variables not work here? `PIP_NO_BINARY=:vext:` So it's okay for `pipenv install` to blow up and not work unless they know to set `PIP_NO_BINARY` every time they install...