Lines not drawing correctly for S2

EgonOlsen · March 27, 2012, 11:06:22 PM

Is this always the first segment being drawn or a (fixed?) number of segments? Can you narrow that down somehow? And does setting Config.useVBO=false; (has to be executed right at the beginning; before creating any object) make any difference?

zammbi · March 27, 2012, 11:12:51 PM

Found a interesting test case. I made my stadium transparent. When looking from behind had no problems(below), but looking at front had the problem

[attachment deleted by admin]

zammbi · March 27, 2012, 11:13:27 PM

Looking at front(below). If you look closely between the 2 images, my transparent grid changes.

QuoteConfig.useVBO=false;

Solves the problem

QuoteIs this always the first segment being drawn or a (fixed?) number of segments?

Well I have 40 segments, looking at the curve it seems a few being drawn.

[attachment deleted by admin]

EgonOlsen · March 27, 2012, 11:18:35 PM

Quote from: zammbi on March 27, 2012, 11:13:27 PM
QuoteConfig.useVBO=false;
Solves the problem

The funny thing is: The lines don't use VBOs at all. Only the rest of the geometry does...i'm close to consider this to be a driver bug...

zammbi · March 27, 2012, 11:23:08 PM

Quotei'm close to consider this to be a driver bug...

Yeah probably is. S2 is a very popular device and not sure if this will effect everyone with the same graphics chip. So if there is no work around then I'll have to keep VBOs off.

EgonOlsen · March 27, 2012, 11:30:49 PM

It's a Mali GPU. I'm not sure which other devices are using these suckers...

EgonOlsen · March 27, 2012, 11:42:30 PM

Quote from: zammbi on March 27, 2012, 11:23:08 PM
...then I'll have to keep VBOs off.

It shouldn't be a performance issue in your case. I'll look into this again tomorrow, but i don't think that i'll discover the magic switch. After all, it's just a simple draw call that says: These are the coordinates and we have xxx of them...please do! I've no idea what prevents it from doing so...but i'll look into it. Maybe i'll find something...

zammbi · March 27, 2012, 11:46:28 PM

You could have a blacklist of GPUs and if it's a "Mali-400 MP" you could turn off VBOs by default? But then again since only lines that are causing the problems (that we know about), this application is probably the only one having the problems

QuoteIt shouldn't be a performance issue in your case.

Yeah my 3d stuff is quite light on the gpu.

Quotebut i'll look into it. Maybe i'll find something...

Thanks again

EgonOlsen · March 28, 2012, 10:28:33 PM

I've no idea what should cause this other than a driver bug. It's a simple call that says: This is the line data (which obviously is correct and not affected by transparency at all) and then executes a draw call for that data with the current length (which isn't affected by transparency either). I've no idea what i'm supposed to do to get this working correctly.

However, please give this version a try. I doubt that it'll fix the problem but it's worth a try: http://jpct.de/download/tmp/jpct_ae.jar

zammbi · March 28, 2012, 11:04:52 PM

Sorry it didn't fix the issue. Don't worry about it, if its going to be a hassle.

I've just done this:

Quoteprivate static final String[] vboBlackList = {"Mali-400 MP"};

   public static void SetupJpctOptionsForGPU(final GL10 gl){

      final String renderer = gl.glGetString(GL10.GL_RENDERER);

      for(String test: vboBlackList){
         if(test.equalsIgnoreCase(renderer)){
            Config.useVBO = false;
         }
      }
}

However I can keep on testing anything you give me.