Re: [GtkGLExt] Multithreading vs glXMakeCurrent()
- From: Norbert Schultz <norbert schultz insa-lyon fr>
- To: Jason Newton <nevion gmail com>
- Cc: gtkglext-list gnome org
- Subject: Re: [GtkGLExt] Multithreading vs glXMakeCurrent()
- Date: Tue, 4 Mar 2008 13:22:58 +0100
Ah thanks,
Weird, 3D Graphics API with no multithreading support in 21th century ;) I
will put it alltogether in one worker thread.
Greetings,
Nob
On Tuesday, 4. March 2008, you wrote:
> Multithreading with opengl is a bad idea, but only because of drivers
> using tls (thread local storage). Nvidia's driver is one such driver
> and a context can only be access/manipulated in the thread that created
> it. Essentially this means you must communicate with an opengl
> drawing/managing thread using message passing. The whole multithreading
> topic really leads to a nightmarish situation and difficult debugging
> given the sad state of affairs with many video card drivers, so if you
> want your program to run reliably on different computers, run all the
> direct gui code in a single thread. You might consider using processes
> instead of threads even, then tls cannot be an issue.
>
> Norbert Schultz wrote:
> > [.. Multithreading with nVidia drivers ..]
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]