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
Basically, in the curent state-of-affairs, you have to use a stupid work-around in order to have upscaled spritesheets working properly in the browser:
To be more specific:
version 1 is the source-code one writes without too much thinking, it is the "natural way" to solve the problem. But this creates a fatal error (pyVM crash) with the current version, that is: v24.4a2 of the Kata.Games system
version 2 works fine. What changed is the fact that instead upscaling then cutting in the spritesheet, we do it the other way around. As you can see this critical bug is related to details about how upscaling works within pyVM. The explanation is that how pyVM handles surface manipulation (in particular: calls to surface.sub_subsurface(...) ) is still a bit clunky.
Basically, in the curent state-of-affairs, you have to use a stupid work-around in order to have upscaled spritesheets working properly in the browser:
To be more specific:
v24.4a2
of the Kata.Games systemsurface.sub_subsurface(...)
) is still a bit clunky.Version 1
Version 2
The text was updated successfully, but these errors were encountered: