I started a thread about surfaces failing on a modded transformer, I now know the
surfaces failing on stock transformers.
The App compiled against 5.1xxx didn't have reports of this problem, it seems to be a 5.2
problem.
Anyone come across this ?
Cheers
Have you tried the IwGx Surface Example? Does this work ok or does it exhibit the same problems?
Can you provide any more information or a repro case?
Hi,
I don't have the device myself, I put an update to my app out using 5.2beta then again with 5.2 release
with nothing changed apart from a minor keystate change.
Feedback I got was App compiled with 5.2 release has these surface fail errors oon the transformer , 5.2beta worked fine as a quick test I took out the EGL_RED_SIZE =8 EGL_GREEN_SIZE =8 EGL_BLUE_SIZE =8 AndroidSurfaceHolder= 1 # RGBA_8888 but app still failed creating surfaces.
As a repro you have the latest zest file for the App, as the App works fine on my defy and vega maybe that
can help you.
Cheers
I've deployed your zest file and have seen the errors, but I'm not seeing them with any of our examples. Can you provide us with some code or a project which reproduces this issue?
Hi,
My responses are limited as I don't have the device I'm afraid.
Surface creation code for example.
if( !s_Surface_1->CreateSurface(NULL, LensViewSurfaceSize, LensViewSurfaceSize,CIwGxSurface::EXACT_MATCH_F|CIwGxSurface::PERSISTENT_F|CIwGxSurface::PRESERVE_FRAME_BUFFER_F)) IwError(("Surface 1 creation failed"));
my icf
EGL_RED_SIZE =8
EGL_GREEN_SIZE =8
EGL_BLUE_SIZE =8
AndroidSurfaceHolder= 1 # RGBA_8888
Apart from load in the assets this code is next so not alot of scope for the app to go wrong ;).
Things that will fail the surface creation is PERSISTENT_F and PRESERVE_FRAME_BUFFER but app was reported working in the 5.2beta.
Cheers
Steve
Hi,
Any more info on this one? I'm only getting these reports on this
device (I've had a few more)? but only on this device it seems.
Cheers
Am seeing this exact same issue. Then I found the setting in s3e.icf:
# Asus eee Transformer TF101
# has problems with FBO surfaces
{ID=ANDROID "Transformer TF101"}
[GX]
DisableFBOSurface=1
so in my app.icf I set:
{ID=ANDROID "Transformer TF101"}
[GX]
DisableFBOSurface=0
And everything now works! SDK 5.2.1..
What I did to test was to DisableFBOSurface for my test Xoom and I could repro the issue.
We are investigating.
It seems that it causes assert in debug version but it works
While the DisableFBOSurface=0 for TF101 allows the App to run on this
device, I'm getting rendering errors every time it's run were random
vertices are shooting off into the distance in my shader.
I've seen this effect before with boned characters (an old post) but
not using bones now.
I'm sure they are linked, works fine on the 1.6 SDK, but people are
upgrading to ICS - and 1.6 has problems running with ICS even though it should work.
Hello,
i have the same problem, our application has been launch on android and crash on Asus Transformer TF101.
I don't have the device so i can't test why the app crash.
But at the start of the app i also create Surface.
I use surface to make transition between the page of my book. It's quite important for me.
Rob have you more information of why the 'DisableFBOSurface=1' is set for this platform ?
I don't want to activate de FBOSurface and have a random crash generate by a memory leak.
S Pothieux
Technical Director
www.slimcricket.com