render not correct on Asus TF101!

[GoogleCodeExporter]

On Asus TF 101,I found this issue:
Game Scene Always on Splash Logo and not switch to game scene.
Game logic and input is correct.
User can't view it correctly.

Original issue reported on code.google.com by mileslee...@hotmail.com on 29 Nov 2011 at 7:23

[GoogleCodeExporter]

11-29 15:36:18.114: W/EmoFramework(16419): Offscreen framebuffer is not 
supported on this device.

Maybe the bug is cause by this reason

Original comment by mileslee...@hotmail.com on 29 Nov 2011 at 7:30

[GoogleCodeExporter]

Could you please attach a file that you use to reproduce this issue for more 
information? You can not use the scene transition when the device failed to get 
offscreen framebuffer (the function like stage.load(Main(), 
currentSceneModifier, nextSceneModifier) will fail ), but on the other hand the 
function like stage.load(Main()) will work, I guess. I would like to see the 
exact script file you use. 

Original comment by infosia...@gmail.com on 29 Nov 2011 at 10:56

• Changed state: Accepted

[GoogleCodeExporter]

Oh I've seen your email report. kawazbuster-squirrel also fails..now I think 
your expectation is right. The scene transition fails when the device failed to 
get offscreen buffer. I don't know why Asus TF101 failed to get offscreen 
buffer but it seems some device fails to get them..anyway I'll fix this issue 
and I appreciate your report!

Original comment by infosia...@gmail.com on 29 Nov 2011 at 1:56

[GoogleCodeExporter]

I test it use "kawazbuster-squirrel-1.0.4".
You can tell me how to get more info about this issue.

Yes.Follow your instruction, it will work.
//stage.load(MainScene(), null, emo.AlphaModifier(0, 1, 1000, 
emo.easing.CubicOut));
// will not work!

stage.load(MainScene());
// OK! work without transition effects.

Note that TF101 is a very popular device.
1.
Is there some API to know this device feature(NO offscreen buffer) and deal 
with it in script ?

2.Have you a IM account and let me know?

Original comment by mileslee...@hotmail.com on 29 Nov 2011 at 1:56

[GoogleCodeExporter]

Thank you for your report. Currently there's no API to know whether the device 
can handle offscreen buffer. I'm fix how stage loading works, like following 
way.

1. if the device can not handle offscreen, stage.load(TheScene(), modifierA, 
modifierB...) acts like stage.load(TheScene()) that won't use offscreen buffers.
2. stage.isOffscreenSupported() will be added to emo.Stage.

You don't have to detect whether the device handles offscreen at loading stages 
like below.

// you don't have to code like below:
if (stage.isOffscreenSupported) {
  stage.load(TheScene(),modifierA,modifierB,....)'
} else {
  stage.load(TheScene());
}

// instead, emo.Stage automatically detect whether the device has offscreen and 
the functions will cause no error. this code acts like stage.load(TheScene()) 
when the device has no offscreen framebuffer.
stage.load(TheScene(), modifierA, modifierB,..);

And, because I would like to keep the question and answers open to the 
world-wide, I would like to use google code issues and emo-discuss forum to 
discuss about emo-framework, not e-mail or IM... :)

Original comment by infosia...@gmail.com on 29 Nov 2011 at 2:46

[GoogleCodeExporter]

Now I have updated the kawazubuster-squirrel that skip using scene transition 
when getting offscreen buffer fails. Could you please try following update to 
see how it works? If these changes seem OK, I will release new maintenance 
version of emo-framework.

http://code.google.com/p/kawazbuster-squirrel/downloads/detail?name=kawazbuster-
squirrel-1.0.5.zip

Original comment by infosia...@gmail.com on 29 Nov 2011 at 10:58

• Changed state: Fixed

[GoogleCodeExporter]

nice work!
it is work fine.No transition on it.
i want to sleep and play modern warfare 3.

Original comment by mileslee...@hotmail.com on 30 Nov 2011 at 3:16

[GoogleCodeExporter]

I appreciate your report! Now I have released a maintenance version of 
emo-framework. Thanks and have a good night :)

Original comment by infosia...@gmail.com on 30 Nov 2011 at 4:26

• Changed state: Verified