MikalDev

I got a request from a Construct 3 user of my C3 Spine plug-in to use data URIs instead of URL paths (required for playable ads). We are still using Spine 3.8 spine-ts runtime (we will go to 4.0 in the future when we have time to upgrade.)

Using the spine-ts 3.8 runtime, what is the best way to load data URIs instead of fetching/loading the files? Generally, I think the image might just work with some tweaking to match 'file name', how about json and atlas files?

I have seen the webplayer supports data URIs, so I will also take a look at that implementation.

Thanks for the advice.

---

Ah, I see the support is in the AssetManager, but it does not look to be available in the SharedAssetManager which we are currently using. Hmm.
MikalDev
  • Mesajlar: 70

Nate

I believe SharedAssetManager is gone in 4.0 because now AssetManager does everything SharedAssetManager used to do.
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11855

MikalDev

Yes, I understand that (I have read the 4.0 WebGL upgrade notes.) I am thinking I would need to bite the bullet and upgrade to Spine 4.0 WebGL runtime to get the support for data URIs.
MikalDev
  • Mesajlar: 70


Dön Runtimes