Skip to main content
B
boat5
Inspiring
October 4, 2011
Question

Air3.0 andriod GPU poor performance after deactivate/reactivate

  • October 4, 2011
  • 1 reply
  • 767 views

Air3.0.0.408 (released oct 4th 2011).

-Open android app in GPU mode:

great and stable performance / auto smoothing on bitmaps as usual

-Minimize to homescreen and re-open app:

very poor performance, horrible framerate, originally auto smoothed bitmaps are now jagged.

My game works great on air 2.5, 2.6, 2.7

This is happening in Air 3 only

I just downloaded "Flash GPU performance tester" from android market. (dont know much about the app)

-Open android it

40 fps solid

-Minimize to homescreen and re-open app:

20 fps and staggering.

Something was changed with GPU rendering in the newest release of Air3.

Only after minimize app and regaining focus does this occur.

Someone please advised what has changed so i can try and adjust my rendering. My game whiched worked perfect before still works great, but cannot recover properly after minimize and re-open anymore.

I had reported in Air3 beta that minimize/reactivate was crashing in GPU mode, this is now corrected in the Air release, but this other issue occurs

droidx gingerbread(2.3 android os)

This topic has been closed for replies.

1 reply

H
hoono
Participating Frequently
October 15, 2011

Hi, I was having the exact problem and I think this must be a bug in AIR

I sort of overcame the problem by setting the stage quality to LOW, which seemed to keep the frame rate above 30fps.

What I have noticed was that AIR seems to be setting the rendermode to CPU or Direct. You can test this by trying the following:

1. add a small bitmap element on stage.

2. give the bitmap scaleX and scaleY to 2 or 3.

3. set the stage quality to LOW

4. try viewing with rendermode set as CPU and GPU

What you will notice is that under GPU mode, the bitmap is smoothed, and CPU mode seems to NOT smooth the bitmap.

Under GPU mode, while the application is running, goto Android home screen and invoke the application again. You will notice the smoothing is gone.

I think i should report this as a bug..

some of my bitmap assets on stage are 200% big, and by viewing my application via GPU mode, the bitmap is smoothed by default. but under CPU mode, the bitmaps are not smooted at all.

B
boat5Author
Inspiring
October 15, 2011

Great observation! It does seem like its going into CPU mode.

The smoothing is one reason.. but also, when blitting with copyPixels() its naturally slower in GPU mode as it keeps re-writing the main canvas bitmap to gpu, however when selecting Blitting with the "Flash GPU tester", i see a higher framerate after the app has minimized/resumed... another indication its reverted to CPU mode.

I had logged a bug here 10 days ago:

https://bugbase.adobe.com/index.cfm?event=bug&id=2993046

Its now listed as "to fix" ... i take that as an acknowledgment of the issue (although no one else replied).

According to friends i had testing, apparently some device models don't have the problem. I know droidX and droid2 deffinitly do.

This is the logcat error i get when the issue begins and seems to drop gpu support afterwards:

13286 13286 E libEGL  : call to OpenGL ES API with no current

context (logged once per thread)


Firefly Community Gallery
Adobe Firefly

Remix with Firefly Community Gallery

Thousands of free creations to fall in love with and remix in Firefly.

Explore now
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices