AIR 17 : Stage3D Fails to render in Android

[Enigmato]

Because Adobe Bugbase is completely messed up (white screen, infinite refresh loop, etc) so I have to write my bug report here.

Hope bugbase get fixed soon. It is rarely accessible with chrome browser.

Problem Description:

On some android devices, Context3D.createVertexBuffer() throws following error :

ArgumentError: Error #3672: Buffer creation failed. Internal error.

Starling frame work can't render anything due to this error, resulting in black screen.

Code seems to be running (as sound is played normally, and scout reports normal code execution),

but rendering loop fails with error (happens as soon as starling's addChild() is called).

Debug attempt is limited due to lack of information in the error message.

Steps to Reproduce:

Tried on Sharp SH-06D (Android OS v4.0.4, Using AIR SDK 17 build 124 / 138)

Please see sample project. As Context3D fails, application cannot render anything on stage3d.

SH-06D has Texas Instrument OMAP4460 1.2Ghz dualcore / PowerVR SGX540.

Actual Result:

Context3D throws error, stage3d completely black. code is running but app unusable.

Expected Result:

Starling's QuadBatch should be rendered correctly.

Any Workarounds:

Does not happen in APK files built with AIR 16 build 292.

Other android devices does not exhibit this behaviour.

Tested and reproduced :

Sample project APK's built with AIR 17 build 124, 138, as well as all AIR 17 beta builds

Android Device : Sharp SH-06D (android v4.0.4, OMAP4460 / PowerVR SGX540 GPU)

Sample Project :

Dropbox - BugTest.zip

Anybody experiencing same problem (black screen on some android devices, stage3d)?

[Paul M Schwarz]

Yes, getting this same problem on Android (Samsung Galaxy 4 7").

Doesn't occur w/ AIR 14.

[tdwivedi]

Hi Enigmato,

Thanks to bring this to our notice. We could successfully reproduce the bug at our end. Our team will be looking into this.

-Tushar

Adobe AIR Team

[mrsimonrodriguez]

We're having this issue with Air 17 + Starling on a Samsung Galaxy Tab 3 (SM-T210).

Does not occur on Air 15.

Exception fault: ArgumentError: Error #3672: Buffer creation failed. Internal error.

  at flash.display3D::Context3D/createVertexBuffer()

  at starling.display::QuadBatch/createBuffers()[/xxx/Starling-Framew ork/starling/src/starling/display/QuadBatch.as:173]

[trycatch]

I encountered the same issue. When enableErrorChecking for Context3D is turned on, I got:

Error #3700: A texture sampler binds an incomplete texture. Make sure to upload(). All miplevels are required when mipmapping is enabled.

Everything works on Air 16 SDK. Phone is Galaxy Nexus running Android 4.2.1. The build does not fail on our other Android test devices and all iOS builds on all devices seem fine. Mipmaps are not used.

[tdwivedi · Accepted solution]

Hi Guys,

This bug has been fixed internally. It will be released in next AIRSDK release.

-Tushar,

Adobe AIR Team

[rvendler]

Which version is the fix in? We have tested on the 18.0.0.109 beta (released April 28), and still see the behavior described in post #4 above ("When enableErrorChecking for Context3D is turned on, I got: Error #3700: A texture sampler binds an incomplete texture. Make sure to upload(). All miplevels are required when mipmapping is enabled.")

[tdwivedi]

The above confirmation for fix was regarding the Enigmato's report of the issue "Error#3672: Buffer creation failed. Internal error." issue. Your mentions "Error#3700: A texture sampler binds an incomplete texture. Make sure to upload().”

We will surely look into this one as well. Can you tell us in what scenario you are getting above problem ? Such error is also seen in cases where mipmapping is enabled with Rectangular textures, because rectangle textures aren't supported. If that isn't the case, please also provide us the resources (specially ATF file ) and a sample project in which you are able to reproduce this issue.

-Tushar,

Adobe AIR Team

[grosssmutttr]

I'm still getting this issue with the latest beta AIR 18.

On a Nexus 4 running Android 5.1 it works but on a Samsung Galaxy S2 with Android 4.1.2 I'm getting the following:

ArgumentError: Error #3672: Buffer creation failed. Internal error.

  at flash.display3D::Context3D/createVertexBuffer()

  at starling.display::QuadBatch/createBuffers()[/Users/redge/Dropbox/Development/starling/starling/src/starling/display/QuadBatch.as:170]

  at starling.display::QuadBatch/syncBuffers()[/Users/redge/Dropbox/Development/starling/starling/src/starling/display/QuadBatch.as:199]

  at starling.display::QuadBatch/renderCustom()[/Users/redge/Dropbox/Development/starling/starling/src/starling/display/QuadBatch.as:217]

  at starling.core::RenderSupport/finishQuadBatch()[/Users/redge/Dropbox/Development/starling/starling/src/starling/core/RenderSupport.as:372]

  at starling.core::Starling/render()[/Users/redge/Dropbox/Development/starling/starling/src/starling/core/Starling.as:503]

  at starling.core::Starling/nextFrame()[/Users/redge/Dropbox/Development/starling/starling/src/starling/core/Starling.as:457]

  at starling.core::Starling/onEnterFrame()[/Users/redge/Dropbox/Development/starling/starling/src/starling/core/Starling.as:660]

The release notes of the beta18 mentioned:

"Error #3672: Buffer creation failed" while calling createVertexBuffer() to a Texture on Samsung Galaxy Tab 4 (3960859)

So please check whether this is fixed on other devices like the Samsung Galaxy S2 🙂

I also saw someone complaining this issue on a Samsung Galaxy Tab 3 and he stated that he also tried the latest beta:

Uncaught ArgumentError: Error #3672 at starling.display::QuadBatch/createBuffers() · Issue #676 · Ga...

I can't update my apps since AIR 17...

[ashleys65929054]

Hello tdwivedi,

Could you please link the bugbase entry for this issue so we can track this issue.

Thanks,

Ashley

[tdwivedi]

Hi Ashleys65929054,

We have an internal bug#3960859 for "Error#3672: Buffer creation failed. Internal error." . It was earlier reported for Samsung Galaxy Tab 4, and was fixed for it, as mentioned in release notes.

We encourage you to log a bug on bugbase for the same with details of your test environment. Please inform us after logging the bug, so that we will link it to the existing internal bug for better tracking of the issue.

About "Error#3700: A texture sampler binds an incomplete texture. Make sure to upload().”, we are still waiting for the response to the above query. We will need the above mentioned info to proceed on it.

-Tushar,

Adobe AIR Team

[Pavel Syrnev]

Hi all
the same issue for Asus Transformer Pad TF701T K00C

AIR 18.0.0.180 - the same issue

AIR 18.0.0.199 - the same issue

ArgumentError: Error #3672: Buffer creation failed. Internal error.

[tdwivedi]

Hi @Pavel Syrnev,

Were you able to reproduce the above issue (Error#3672) on any other devices as well ?

Hi rvendler‌,

Regarding "Error #3700: A texture sampler binds an incomplete texture. Make sure to upload(). All miplevels are required when mipmapping is enabled.", are you able to provide us the info inquired earlier? ie

Can you tell us in what scenario you are getting above problem ? Such error is also seen in cases where mipmapping is enabled with Rectangular textures, because rectangle textures aren't supported. If that isn't the case, please also provide us the resources (specially ATF file ) and a sample project in which you are able to reproduce this issue.

-Tushar,

Adobe AIR Team

[rvendler]

Hi Tushar,

I provided more context here: Bug#3986142 - On some Android devices, some textures fail to upload without any indication of error.

Hope this helps!

[Pavel Syrnev]

Hi tdwivedi,

Error#3672 is reproduced on Asus Transformer Pad TF701T K00C.
App works fine on devices like  Galaxy Tab 3 Lite 7.0, Galaxy TabPRO 8.4, Nexus 4, Nexus 7 (2013) .

- Pavel

Hope this helps!