-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Stack display updating every time an object is added. #265
Comments
Hmm... when loading a deck of cards, only the top and bottom cards should be loaded in. I'll have to do some testing on this on my end. Are you able to confirm which version of the game had faster loading times for decks? |
I was using Beta 3 before. |
Just checked this on my system, there is definitely a noticeable difference in the loading times - thanks for the heads up! |
I've found the cause of the issue: dcb084d introduced a workaround for a race condition in
EDIT: It's not the collision shape that's the issue, that's only loaded once when the stack is first created. Instead, it's the stack textures updating every time a piece is added. This is more deep-rooted than I initially thought, so I'm pushing back the milestone to v0.2.0, and I'll make sure when rewriting the code to separate the actions of adding a piece to the stack, and updating the stack display. |
When loading a deck in the assets menu, the deck takes much more time than in earlier versions to load. It feels like all cards in a deck is being loaded, instead of the top one only.
The text was updated successfully, but these errors were encountered: