4 ms·

We're testing remote 3D rendering over WebRTC. We render the 3D world in the cloud. Video and controls go over a WebRTC-connection. I wrote a simple nodejs webs

by pasiaj 13y ago

We're testing remote 3D rendering over WebRTC. We render the 3D world in the cloud. Video and controls go over a WebRTC-connection. I wrote a simple nodejs websocket server to handle the signaling. It has been a quite wonderful experience despite the tech being somewhat experimental. Google Chrome offers excellent tools (chrome://webrtc-internals/ & chrome://webrtc-logs/). First I wrote the client and a mock server to work in the browser while a colleague started implementing webrtc to work in the renderer with the PeerConnectionpp-lib. Debuggin was awesome, when you had a working mock renderer in the browser. All the bugs I encountered we're my own and I found all the answers I needed in the dev API doc: http://dev.w3.org/2011/webrtc/editor/webrtc.html http://dev.w3.org/2011/webrtc/editor/webrtc.html

netcraft 13y ago
This is quite interesting. Does this mean all clients are seeing the same video rendering? What made you do it this way rather than render on the client and update positioning over WebRTC? Regardless id love to read more about your progress if you have anything written down.
- pasiaj 13y ago
  > Does this mean all clients are seeing the same video rendering? Yes - all clients connecting to the same renderer instance are seeing the same video. > What made you do it this way rather than render on the client and update positioning over WebRTC? This is a part of a larger [research project](https://forge.fi-ware.eu/projects/miwi/ https://forge.fi-ware.eu/projects/miwi/) to create and test the viability of different kinds of UI enablers. One use case for cloud rendering is low-end mobile devices that can't handle the rendering of complex 3d-scenes. Or you could create a live presentation using a 3D world, eg. about an architectural design. Other people in the project are building tools on top of WebGL to do the rendering in the browser - mainly porting the [realExtend toolset](http://realxtend.org/ http://realxtend.org/) to Javascript. Everything I do will be released as open source later on. I'll give you a shout when we got something to show.

by pasiaj 13y ago

netcraft 13y ago

This is quite interesting. Does this mean all clients are seeing the same video rendering? What made you do it this way rather than render on the client and update positioning over WebRTC? Regardless id love to read more about your progress if you have anything written down.

pasiaj 13y ago
> Does this mean all clients are seeing the same video rendering? Yes - all clients connecting to the same renderer instance are seeing the same video. > What made you do it this way rather than render on the client and update positioning over WebRTC? This is a part of a larger [research project](https://forge.fi-ware.eu/projects/miwi/ https://forge.fi-ware.eu/projects/miwi/) to create and test the viability of different kinds of UI enablers. One use case for cloud rendering is low-end mobile devices that can't handle the rendering of complex 3d-scenes. Or you could create a live presentation using a 3D world, eg. about an architectural design. Other people in the project are building tools on top of WebGL to do the rendering in the browser - mainly porting the [realExtend toolset](http://realxtend.org/ http://realxtend.org/) to Javascript. Everything I do will be released as open source later on. I'll give you a shout when we got something to show.