[Qt5-feedback] OpenGL ES 2.0 requirement

[Linos]

El 01/06/11 15:34, Konrad Rosenbaum escribió:
> On Wed, June 1, 2011 13:35, Linos wrote:
>> How will affect this requirement to remote desktop apps via vnc, nx or
>> rdp? i
>> use any small qt apps i have developed via rdp and nx only.
>
> I just checked with VNC and software rendering - this scenario works (I
> could see the gears of glxgears). I can't check VNC and hardware rendering
> till much later today.
>
> If you have a machine with a fairly modern graphics board and KDE running:
>
> glxinfo tells you whether you have software or hardware rendering active:
> OpenGL vendor string: Mesa Project
> OpenGL renderer string: Software Rasterizer
>
> The above would tell you it is software. This one is trivial: it works. If
> there is a different vendor/renderer then it is probably hardware (at
> least if it somehow correlates to your graphics hardware).
>
> glxgears is a nice little demo of OpenGL (comes in some Mesa package).
>
> Now start Desktop Sharing in KDE and connect from a different desktop. If
> you still see the gears in VNC then you are fine.
>
>
>
>      Konrad
>

well with nx it seems we are out of luck.

skuda at nasCentral:~/Escritorio$ glxinfo
name of display: :1203.0
Error: couldn't find RGB GLX visual or fbconfig

skuda at nasCentral:~/Escritorio$ glxgears
Error: couldn't get an RGB, Double-buffered visual

in rdp sessions directdraw it is disabled so i think that should not work 
either, maybe to use qt5 in remote control protocols we will need to wait for 
someone to write a stable software opengl emulator for qt?

Only the console session should have this hardware acceleration (if gpu present 
and driver supports) enabled, no? if you are using vnc to connect to the console 
session maybe glxgears works but i think any other remote control protocol that 
uses sessions in background like rdp or nx will fail.

Regards,
Miguel Angel.