When I export from spine 2D to binary, when loading the files, some of the project animations have noise. For a web based slot app.What are the best export settings ?
How can I solve the problem ? Is it an issue in the export ?
When I export from spine 2D to binary, when loading the files, some of the project animations have noise. For a web based slot app.What are the best export settings ?
How can I solve the problem ? Is it an issue in the export ?
To address the issue of noise in animations when exporting from Spine to binary for a web-based slot app, it's important to ensure that your export settings are optimized for your specific use case. Here are some steps and considerations:
Export Settings: When exporting, make sure you are using the correct settings for your project. If you are exporting to binary, ensure that you are using the latest version of Spine and the appropriate runtime that supports binary export, such as spine-libgdx.
Resolution and Scale: Check the resolution and scale settings during export. If the animations appear pixelated or noisy, it might be due to low resolution. Consider exporting at a higher resolution and using the appropriate scale settings to maintain quality.
Texture Atlas: If you are using a texture atlas, ensure that the settings for max width/height and min width/height are configured correctly. This can help in maintaining the quality of the textures used in your animations.
Smoothing and Filtering: Adjust the smoothing settings to reduce artifacts. For pixel art, you might want to set smoothing to 0 for a nearest-neighbor filtering effect, but be aware that this can introduce aliasing artifacts.
Runtime Configuration: Ensure that the runtime configuration for your web app is set up to handle the textures and animations correctly. This includes setting the min filter, mag filter, and mipmap generation appropriately.
By carefully adjusting these settings, you should be able to reduce noise and improve the quality of your animations when exporting from Spine to binary.
Please show us what you see. Otherwise we need to guess at what's happening. You also need to tell us which runtime you are using.
The runtime version is : "@esotericsoftware/spine-phaser": "4.2.74",
When i load the file appears this square which is following the animation
Thanks for providing information about the runtime.
As shown on the npm page, @esotericsoftware/spine-phaser
has been deprecated and will no longer be updated.
I recommend upgrading to the latest version of @esotericsoftware/spine-phaser-v3
, which is currently 4.2.80
at the time of writing. This version includes an important fix that may impact versions prior to 4.2.75
.
Regarding the runtime issue, the screenshot you provided isn't sufficient. While I can see a faint green square, I can't determine the expected result.
If you're using blending modes, make sure to export PMA (Pre-Multiplied Alpha) assets and use them correctly in Phaser.
Please provide a clearer representation of the issue. Ideally, we would like to see a comparison of both the expected and actual results, or a video that clearly demonstrates the problem.
It would also be helpful if you could send us a minimal reproduction example of the issue at contact@esotericsoftware.com.
We’ve received your assets.
As I mentioned yesterday, if you're using blending modes, you should enable Pre-Multiplied Alpha when exporting your assets.