texture uploading with callback

[User_Unknow]

Hi,

Why uploadCompressedTextureFromByteArray allow report "complete" state and other don't allow to do this? Should I open feature request for this or I will be duplicate?

I mean we want use complete events also for BitmapData and ByteArray callback

[Jeff__Ward]

Anton - uploadCompressedTextureFromByteArray is the only one that's asynchronous.  The other two operations (uploadFromBitmapData and uploadFromByteArray) are synchronous, so they block and upload, and they're complete before the next line of code executes.

That said, it would be nice to allow asynchronous upload for the other types -- perhaps this is exactly what you are asking for?  I assume this is very non-trivial, because if it was easy it would have been built that way.  Asynchronous texture upload (especially if it doesn't block the UI) is definitely preferrable.

Best,

-Jeff

[User_Unknow]

Yes, I mean we need asynchronous uploading. Internally there is no differnce what to upload. ATF or BitmapData because it's decodes in CPU and than uploads to GPU. ATF can't be used for interfaces because it have big artifacts. Using asynchronous we can inform users about "loading" state without CPU hogging, because uploadng 4096x4096 on iOS (Adobe Air) it's long process and only asynchronous can help

[Dominik_Saur]

Hi Anton. Why you don't use  uploadCompressedTextureFromByteArray if you require async upload? ATF textures can be used without blockbased compression so you won't get ugly rendering artifacts. The upload and decoding speed is much better then creating textures from bitmapdata. If the filesize hurts you, you can still enable lossless JPG-XR compression. But this will increase decoding time again.

[User_Unknow]

Hi Dominik 😉  Yes, I know about uploadCompressedTextureFromByteArray. It's work fine for me. But just generate ATF atlas where I have the same game unit in different viewpoint (pseudo-3d) - OGL8888 as I see artifacts. So this why using BitmapData I don't see any artifacts... Also for reducing artifacts many developers apply small noise in photoshop to PNG before converting it to ATF. This remove small artifacts. With alpha near 0.1-0.3 without noise ATF make some blurring on thin image edges... So this why a lot of users still love BitmapData to GPU uploading...

[Dominik_Saur]

Hi Anton, i see your problem. A workaround for it can be uploading smaller textures tiles bitmapdata so you can track progress and have no blocking of the ui. After uploading draw them to a dynamic texture atlas (rendertexture)

[User_Unknow]

I have small DirectX background and I remember that you can't upload directly any atf, bitmapdata and etc data formats 😉 so this files anyway must by preprocessed. So why simply not add some small callback method for this and make it async ) May be there some deeper and hard things that I don't understand. But on the fast view looks like it's possible and not to hard.

[jeromiec83223024]

Hey Anton,

If you wouldn't mind, please file a bug on this (the artifacts in uploadCompressedTextureFromByteArray -- please include an example SWF) at http://bugbase.adobe.com, and send me the number.  I'll get it escalated to the Graphics team to see if we can provide some pain-relief in that area.  That seems like it would yield the best outcome.

Thanks!