Re: Remote Rendering

New Message Reply Date view Thread view Subject view Author view

Angus Dorbie (dorbie++at++sgi.com)
Tue, 18 May 1999 11:30:57 -0700


The X server should be able to store the textures locally so it should
be possible with provided you don't draw too much and have the server
side resources to hold the texture objects.

Note that the rendering is done on the display server so it needs to
have the graphics capability, you can't put a 2D X server there and
expect the images to be displayed after rendering on the Octane, that's
not how GLX works.

Cheers,Angus.

Kevin Kronmiller wrote:
>
> We have a Performer application running 1280x1024 on an Octane currently at Irix 6.4. The application uses a terrain database with over 10Mb texture. Our customer has asked us to replicate the display at a remote site over a T1 link (1.5Mbps) at a reduced frame rate. They would like 10 fps if possible. I can think of several ways to do this although the T1 link seems to be a severe limit.
>
> 1 - Pipe the RGB output from the monitor to the remote site.
> 2 - Use X/ GLX to do the remote rendering.
> 3 - Send the application data over the network and run a subset of the application locally.
>
> Any suggestions or pointers are greatly appreciated.
>
> Thanks for your time
> Kevin Kronmiller
>
> -----------------------------------------------------------------------
> List Archives, FAQ, FTP: http://www.sgi.com/software/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com

-- 
"Microsoft's system was like a forest that hadn't had a controlled
 burn in decades, just waiting for one person with a match to turn
 it into a disaster. Melissa was Microsoft's fault. They left their
 system wide open to this sort of abuse, they knew it could happen
 and did nothing." -- Bruce Perens

For advanced 3D graphics Performer + OpenGL based examples and tutors: http://www.dorbie.com/


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Tue May 18 1999 - 11:31:23 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.