PDA

View Full Version : On board GPUs



devdept
02-05-2009, 05:45 AM
Hi All,

A long time ago we started this thread: The code is fine: except for wintel hardware (http://www.opengl.org/discussion_boards/ubbthreads.php?ubb=showflat&Number=245113&fpart=1). The discussions was about the visual artifacts that can happen on these hardwares without detecting them.

We found the solution of detecting the word "Intel" on the OpenGL vendor string and switching to Software OpenGL to avoid issues.

Today we have customer complaining because other OpenGL apps have better graphics performance on the same machine and other reporting crashes on another family of on-board GPUs: VIA-S3G.

Is there a better approach to switch to Software OpenGL on Windows than the one to check for manufacturer name in the vendor string?


Thanks so much for your thoughts,

Alberto

ZbuffeR
02-05-2009, 06:22 AM
Well, a reasonably basic Opengl code should work better with hardware acceleration than without, even on intel/S3. Forcing software looks like a last resort only.

It may be a tad extreme, but what about running GLintercept on DOOM3 with an intel video adapter, and base your "simple path for buggy cards" only on the GL calls you see in the log ?

Don't Disturb
02-05-2009, 06:22 AM
The solution is to use d3d on windows, and have limited support on linux/osx through opengl and shoddy drivers.He was right then, he's still right now. Unfortunately OpenGL is very poorly supported except by NVidia, and you'll keep getting problems like this unless you switch.

devdept
02-05-2009, 06:52 AM
Mmm... sound interesting but we are not so skilled I think.

Believe it or not a very basic textured cube can look very bad on these hardwares.

Alberto

devdept
02-05-2009, 06:53 AM
Don't Disturb,

Please read my post in reply to him...

_NK47
02-05-2009, 07:03 AM
might be an idea to keep a small database of known unstable driver versions which can be checked before starting and if below an approved driver switch to software. this way a verified driver will still be hardware accelerated and if not then at least a user warning can be displayed that you about to switch to software rendering. problem is to collect the database but usually you need one tested version and all below is ignored.

devdept
02-05-2009, 07:29 AM
_NK47,

Yes but this is incompatible with Trial Version of you OpenGL based program. If somebody evaluates it and notice poor performaces is not as bad as visual artifacts :-(

Big software vendors know how to do this and we need definitely to discover how.

Alberto

_NK47
02-05-2009, 07:41 AM
i think big vendors use two rendering APIs for there applications anyways. OpenGL has been neglected many times whereas Direct3D was the one always supported best in Windows. running on Windows and switching to Direct3D is probably the best way to avoid driver problems. OpenGL in this case is left for say Linux where drivers can be open and far more stable. have thought about the solution on this myself many times but still thinking. ;)

devdept
02-05-2009, 10:58 AM
Big software vendors know something we don't, believe me.

Alberto

_NK47
02-06-2009, 01:54 AM
heck, might be even true but i would be more interested on what facts your're basing this on and what "big software vendors" you suspect.

devdept
02-06-2009, 04:50 AM
Take Rhino3D for example, install it on a Wintel machine and magically they disable the HW Acc OpenGL. Same for SolidWorks.

Alberto