Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
Distinguished Ambassadors
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello forum
Operating Systems forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Internet of Things (IoT) blog
Operating Systems blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Graphics, Gaming, and VR forum
OpenGL ES 2.0 problems
Jump...
Cancel
Locked
Locked
Replies
5 replies
Subscribers
136 subscribers
Views
4678 views
Users
0 members are here
OpenGL ES
Options
Share
More actions
Cancel
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
OpenGL ES 2.0 problems
Kwan Chi Lee
over 11 years ago
Pete
over 11 years ago
Note: This was originally posted on 2nd November 2012 at
http://forums.arm.com
Hi Chi,
thanks for the report.
I must say, my first thought seeing the screenshots was perhaps some issue with the texture coordinates and/or clamping mode (as though GL_TEXTURE_WRAP_S and GL_TEXTURE_WRAP_T had been set to GL_CLAMP_TO_EDGE). It would also be interesting to see the fragment shader code to see if any arithmetic is being done on the texture coords.
Does the problem show up with the version of the PicArts app on Google Play? Are there any particular steps required to reproduce the issue?
Cheers, Pete
Cancel
Up
0
Down
Cancel
Kwan Chi Lee
over 11 years ago
Note: This was originally posted on 17th November 2012 at
http://forums.arm.com
Hi Pete,
Sorry for the late reply, and thank you for your quick respond.
Here are the information that may help, please look at it.
There is no special procedure to produce this problem,
I just open it up. It seems that all Mali-400MP device have this problem.
And another user using Galaxy S2 has the same problem too,
hope we can fix it together asap. Great thanks.
Texture Wrapping Function
All texture are set by this helper function.
setWraps(GLES20.GL_CLAMP_TO_EDGE, GLES20.GL_CLAMP_TO_EDGE);
public void setWraps(int wrapS, int wrapT) {
this.wrapS = wrapS;
this.wrapT = wrapT;
GLES20.glTexParameterf(GLES20.GL_TEXTURE_2D, GLES20.GL_TEXTURE_WRAP_S, wrapS);
GLES20.glTexParameterf(GLES20.GL_TEXTURE_2D, GLES20.GL_TEXTURE_WRAP_T, wrapT);
}
Fragment Shader
#version 100
precision highp float;
uniform sampler2D s_texture;
varying vec2 vTexCoord;
void main(){
gl_FragColor = texture2D(s_texture, vTexCoord);
}
Vertex Shader
#version 100
attribute vec4 aPosition;
attribute vec2 aTexCoord;
varying vec2 vTexCoord;
void main(){
gl_Position = aPosition;
vTexCoord = aTexCoord;
}
Photo Mesh
normal = new float[]{
-1.0f, -1.0f, 0.0f, 1.0f,
1.0f, -1.0f, 1.0f, 1.0f,
1.0f, 1.0f, 1.0f, 0.0f,
-1.0f, 1.0f, 0.0f, 0.0f};
4 vertices (x, y, s, t).
Cheers,
Chi
Cancel
Up
0
Down
Cancel
Pete
over 11 years ago
Note: This was originally posted on 4th December 2012 at
http://forums.arm.com
Hi Chi,
I'm struggling to reproduce the issue here. I have a Samsung Galaxy S2 running Android 4.0.4.
I have installed PicArts 3.1.2. I start it, and select "From Gallery" and choose a photo:
I am able to pick several filters, e.g. Hue/Saturation:
Blur:
Sketch:
They all seem to look OK?
Can you perhaps explain the steps necessary to reproduce the problem, or tell us more specifics about the device and versions involved?
I have looked at the application and shader code, and none of that looks like it would cause a problem.
Thanks, Pete
Cancel
Up
0
Down
Cancel
Kwan Chi Lee
over 11 years ago
Note: This was originally posted on 11th December 2012 at
http://forums.arm.com
Hello Pete,
Because of this issue, we updated the app on the store immediately to the older version.
That's why the problem didn't arise when you try the 3.1.2 out.
However, I cannot give you all the source code. I am trying to write a little app to show you what is wrong.
Thanks,
Chi
Cancel
Up
0
Down
Cancel
Pete
over 11 years ago
Note: This was originally posted on 12th December 2012 at
http://forums.arm.com
Hi Chi,
of course, I understand you cannot give out the source. Would it be possible to host a binary APK somewhere of the later version that does show the problem? That may be quicker than you writing a test case, and should be enough to debug the problem.
Thanks, Pete
Cancel
Up
0
Down
Cancel