You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2023. It is now read-only.
Describe the bug
You cannot load image files (e.g. the SpriteSheets in the testing package) as SaltyVolatileImages, however, all the other images (lights, and the final render) are shwon as usual.
To Reproduce
Steps to reproduce the behavior:
Set SaltySystem#preferredImageType to ImageType.VOLATILE
Run testing.Tester
Expected behavior
The exact same thing as with ImageType.BUFFERED
Screenshots
Desktop:
OS: MacOS
Additional context
Running 0.14.16-local
The text was updated successfully, but these errors were encountered:
As because of this bug, SaltySystem.prefferedImageType has become irrelevant for development, I am no longer sure where it is even respected and where the library just produces 'SaltyBufferedImages' per default.
Using Salty Engine 0.15-SNAPSHOT, a prototype for my game renders very laggy with SaltySystem.prefferedImageType = SaltySystem.ImageType.VOLATILE and only shows custom rendered UI and a single sprite (which is the only one to have pixels with transparency != 0 or 1 - coincidence?)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
You cannot load image files (e.g. the SpriteSheets in the testing package) as SaltyVolatileImages, however, all the other images (lights, and the final render) are shwon as usual.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The exact same thing as with ImageType.BUFFERED
Screenshots

Desktop:
Additional context
Running
0.14.16-local
The text was updated successfully, but these errors were encountered: