Subject:
|
Re: LDGLite colour bug
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 15 Jan 2002 16:01:13 GMT
|
Viewed:
|
718 times
|
| |
|
|
In lugnet.cad.dev, Travis Cobbs writes:
>
> "Don Heyse" <dheyse@hotmail.spam.go.away.com> wrote in message
> news:GpF5sJ.66C@lugnet.com...
> > In lugnet.cad.dev, Jacob Sparre Andersen writes:
> > > What do you mean by "using the Mesa driver"? In both cases
> > > the example was rendered directly on the monitor of a third
> > > (Intel based) machine over the network.
> >
> > The third machine with the monitor is immaterial. The opengl
> > driver runs on the machine where the ldglite executable is
> > running. Based on your use of a remote display, I'm going to
> > assume you're probably running linux (and most likely a Mesa
> > opengl driver) on the intel machine where you ran the ldglite
> > executable. Does it have the same version of Mesa? On
> > ldraw.org, ldglite prints this when I run it:
> >
> > GL_VERSION = 1.2 Mesa 3.4
> >
> > What does the intel machine say?
>
> Actually, with a remote OpenGL display setup, OpenGL drivers can be active
> on both machines. If Mesa supports the GLX protocol, and the machine he is
> displaying onto also supports GLX, then the ldglite machine will simply
> create the OpenGL commands and then send them over the network for the other
> machine to interpret and display.
Really? Where can I get more information on this? I was under the
impression that GLX could only accelerate locally when used with DRI.
I had no idea it had its own remote rendering protocol. Is this
something new in XFree 4.0? Is there any way to tell if it's being
used, perhaps something with glXQueryServerString() or glXIsDirect()?
(Actually I'd prefer a glut or gl function for this since I'm not
currently calling any GLX functions directly.)
> This is significantly faster than trying to render on the remote machine and
> then send the bitmap graphics over the wire. However, it means that the
> actual OpenGL rendering is done on his local workstation. The remote
> machine simply creates the list of commands to call.
That sounds great, but makes troubleshooting a bit tougher unless I
can tell who is doing the rendering. Does glGetString(GL_VERSION) get
passed via the GLX protocol to the remote machine?
Don
|
|
Message has 1 Reply:
 | | Re: LDGLite colour bug
|
| (...) I did a quick check and found a few things you should find useful. At opengl.org I found a good definition of what GLX is (which includes the remote display portion): (URL) above also contains a link to the GLX specification (which may or may (...) (23 years ago, 15-Jan-02, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: LDGLite colour bug
|
| "Don Heyse" <dheyse@hotmail.spam....away.com> wrote in message news:GpF5sJ.66C@lugnet.com... (...) Actually, with a remote OpenGL display setup, OpenGL drivers can be active on both machines. If Mesa supports the GLX protocol, and the machine he is (...) (23 years ago, 12-Jan-02, to lugnet.cad.dev)
|
14 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
