GL_SELECT causes long delay

Engines, Libraries and Tools Xith3D Forums
#1

[quote]As of GL_SELECT, this is definitely a driver issue. If someone can create a test case which also measures picking performance, then we can run it across different systems.

Yuri
[/quote]
A small testcase which doesn’t measure the time, but you can use a stop-watch :slight_smile:
Currently I can’t sign JARs, so no Webstart. :expressionless: Please use this Testcase.zip file, which you can unpack and then start the runable Testcase.jar file. It uses the current Xith and Jogl classes inside the xith.jar file next to it.

The testcase takes some seconds to load a Lightwave model twice, with about 47 000 polygons each. Then, whenever you click on the screen it takes ~7 seconds on my Ati Radeon PC (the more models there are in the screngraph, the longer it takes). During this time you see the CPU load is 100%. To see the click works you can move the selected model with awdx keys, or move the camera with pressed middle button.

The picking I start with this line:
PickRenderResult[] bla = myview.pick(myview.getCanvas3D(0), xmouse, ymouse, 1, 1);

#2

you do know you can create a self-signed cert don’t you? It’s not very professional I agree, but none of us here would care :slight_smile:

Will.

#3

We tried the testcase and got the following results:

  • Geforce3, driver version 6.14.10.5672: 2-3 sec.
  • Geforce4 ti4600, driver version 5.6.7.2: 2-3 sec.
  • Radeon 9200, catalyst 4.3: about 7 sec.

the geforce4 showed some strange artefacts. But this is probably related to the old driver:

http://3d.uni-muenster.de/temp/Bild1.png

On every system we saw the “ghost window”. When I maximized it on the geforce3 system, it was just black and everything else still worked fine.

I checked my app on the geforce3 system and noticed times between 2-3 seconds with 80.000 triangles and about 4 seconds for 160.000 triangles. I never had problems with the ghost window in my app.

hope it helps, gismo

#4

Ghost window is a side effect of new JOGL. Check my thread related to JOGL update in this forum.

Yuri

#5

[quote]We tried the testcase and got the following results:

  • Geforce3, driver version 6.14.10.5672: 2-3 sec.
  • Geforce4 ti4600, driver version 5.6.7.2: 2-3 sec.
  • Radeon 9200, catalyst 4.3: about 7 sec.
    (…)
    hope it helps
    [/quote]
    Yes, I think it helps us all. In particular it’s helpful to Yuri when we users post such infos with different configurations on the GL_Select topic here.

Interestingly not only does the Radeon need much longer to open the GlCanvas for the first time, but also to do Gl_Selection… While I think that the newest Ati drivers do provide a solid OpenGL environment (in contrast to former drivers) they’re slower than Nvidia cards for certin things.

Still we need to find a way to do the picking much faster with any card. :slight_smile:

By the way: the “ghost window” thread Yuri mentioned can be found here:
Changes to match latest JOGL build

#6

Hi Will. Yes, I’ve done that many times but … there’s some Jarsigner and jar bizarreness currently (again) with my system which I can’t solve. (It’s been an official bug in former JDKs but now it re-shapes on my PC).
In case you’re wondering what this is, please have a short look at my thread: jarsigner and jar bizarreness