Requesting Context3D is slow

Question

I am noticing that on some devices, requesting a context3D ( via stage3D.requestContext3D( "auto", Context3DProfile.BASELINE ) ) can be particularly slow ( like: 15 secs on the Nook Color ! ). This is just for requesting the context. Uploading textures to the GPU, afterwards, is nearly instantaneous by comparison.

What I would like to do is give the user a hint that the app has not crashed and is still initing ( 15 secs is a long time to wait when nothing is happening! ). Unfortunately, I have determined that while the context is being requested, no screen refreshes occur ( no enter_frame events ), so I can't even do a little loading gage animation.

Instead of using an enter frame handler to animate my loading gage, I also tried using a timer with timerEvent.updateAfterEvent(), but that didn't force any refreshes either while the context was being requested.

Any ideas?

User Unknow · Accepted Answer

I think it's have poor GPU. Firstly try to switch from Context3DProfile.BASELINE to CONSTRAINED. I don't know why you need to use BASELINE for mobiledevices that is have slow GPU. BASELINE used in most cases on desktop games.

Also what is your Air SDK version?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded