From: Dan B. P. <ph...@cs...> - 2007-06-14 21:04:41
|
Brian Paul wrote: > Dan Phung wrote: >> Hi all, >> >> I'm trying to get the setup where the local (app) node sends its >> rendering data to a remote node to get rendered, and then sent back to >> get displayed. From what I've read, I should use the VNC SPU. > > Do you want to use VNC? > > Or, are you trying to render back into the original application window? I guess I don't really want to use VNC, but that's what I read as one way of going about this... but yes, I'm trying to render back to the original application window. > > >> However most of the docs I find are related to vncproxy, which (from >> what I understand) is only needed if I'm using DMX. >> >> Here's the setup I tried (mothership and app node are the same): >> >> app node: start mothership >> python vncdemo.conf Xvnc >> rendering node: start crserver >> app node: crappfaker >> >> Here's what I think it should look like... >> >> crappfaker --(net)--> crserver-> vncspu <--- vncviwer >> >> Should I be connecting the vncviewer to the vncspu? I tried that, but >> the viewer doesn't show anything...I can connect directly to Xvnc and >> see my server though... > > The VNC SPU is derived from the passthrough SPU so it needs to be > followed by another SPU, typically the render SPU. I'll update the > docs about that. > > >> Is there any documentation on how to get this setup? What happens >> if the crserver gets disconnected and then later reconnected? > > You can't dynamically disconnect/reconnect crservers like that. > > -Brian |