Sign in to follow this  
wantnon_cn

OpenGL ios opengles 2.0 lowp cause problem, right? and why?

Recommended Posts

wantnon_cn    115
i am working on a iOS 3d game, because i don't have a real device in hand, so i have being test it in iOS simulator, and it always run well.
today i got a itouch4 with 5.0.1 system and test my game on it.
i found a strange problem:
in shader, i set the texCoord to lowp, and the texture become mess on device (but nothing wrong in simulator), and when i modified it to mediump it fixed.
there are some other wrong effect, and they are also finally solved by change lowp to mediump or highp.
that is a little strange because even though we known a little precision loss many cause some flaws, but i never expected the flaw may so serious as to get totally wrong effect.
and this is not the most strange thing, i also found that after i changed some of the lowp to mediump or highp, the game runs much more fluent on the device than before.
so i start to suspect that may be lowp have some support issue on real device. does the system (here is iOS 5.0.1) not support lowp well?
anyone else have the similar annoying experience with lowp?
i also want to known if i should change all the lowp to mediump or highp (or may be better all change to highp)? Edited by wantnon_cn

Share this post


Link to post
Share on other sites
C0lumbo    4411
My rule of thumb is:

lowp for colours.
mediump for normals and UVs.
highp for positions.

You can lookup the ranges and precisions in the spec, you shouldn't be surprised that lowp is no good for UVs since the range is only -2 to 2, and the precision is too low to represent a large (256+) sized texture to texel accuracy (IIRC).

It's difficult to test your chosen precision produces correct results, because the compiler is always free to give you a higher precision than the one you request, so you just have to test on the various different types of hardware.

In general, I wouldn't expect that increasing precision would improve performance, but there's always edge cases. For instance, lowp UVs have to be converted upwards when you pass them into sampler functions and conversions carry a small penalty - this may explain it since iOS is very sensitive to pixel shader performance. Also, I seem to remember an issue of severe performance problems if your vertex shader output precisions mismatch with their corresponding pixel shader input precisions. Edited by C0lumbo

Share this post


Link to post
Share on other sites
wantnon_cn    115
[quote name='C0lumbo' timestamp='1355346323' post='5009965']
I seem to remember an issue of severe performance problems if your vertex shader output precisions mismatch with their corresponding pixel shader input precisions.
[/quote]
so, if in vertex shader i do not specify a precision for a vertex shader output varying variable, and in the fragment shader i specify it with lowp or highp, will this cause a mismatch problem (have a risk of low performance) ? Edited by wantnon_cn

Share this post


Link to post
Share on other sites
C0lumbo    4411
[quote name='wantnon_cn' timestamp='1355443229' post='5010400']
[quote name='C0lumbo' timestamp='1355346323' post='5009965']
I seem to remember an issue of severe performance problems if your vertex shader output precisions mismatch with their corresponding pixel shader input precisions.
[/quote]
so, if in vertex shader i do not specify a precision for a vertex shader output varying variable, and in the fragment shader i specify it with lowp or highp, will this cause a mismatch problem (have a risk of low performance) ?
[/quote]

Possibly - I'd recommend you be as explicit as possible with precision rather than using the default precision. That said, I'm afraid I don't know the full details - it was an issue that suddenly hit a project after an OS revision a couple of years ago, and we modified our shaders accordingly, but there's a good chance that the problem has been fixed by Apple. Still, it seems like a good idea to avoid a precision change between vertex shader output and fragment shader input anyway.

Share this post


Link to post
Share on other sites
wantnon_cn    115
[quote name='C0lumbo' timestamp='1355472317' post='5010517']
Possibly - I'd recommend you be as explicit as possible with precision rather than using the default precision.
[/quote]
ok, i will take your advice and specify the precision explicitly to insure the matching. Edited by wantnon_cn

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now