Package com.openinventor.remoteviz.rendering

Overview

See: Description

Class Summary

Class	Description
Client	Represents a client application instance using RemoteViz.
ClientSettings	Settings that define a Client.
Connection	Represents a connection from a Client to a RenderArea managed by the RemoteViz service.
ConnectionParameters	Field-value pairs included in the URL during the client connection.
ConnectionSettings	Settings that define a Connection.
EncodedFrame	This class provides the features of an encoded frame that is sent to the client.
FrameEncoders	Defines a couple of encoders that are used to encode still and interactive frames.
IFrameEncodingPolicy	This class is the base class of KeepFramesPerSecondPolicy and KeepFrameQualityPolicy.
KeepFrameQualityPolicy	This class provides a calculation policy which allows to manage the FPS (frames per second) and the quality of interactive frames sent from Remoteviz service depending on the network bandwidth allocated to the Connection.
KeepFramesPerSecondPolicy	This class provides a calculation policy which allows to manage the FPS (frames per second) and the quality of interactive frames sent from Remoteviz service depending on the network bandwidth allocated to the Connection.
NetworkPerformance	This class refers to measures of service quality of the network.
RenderArea	Defines the rendering area.
RenderAreaHardware	Settings to setup hardware of a render area.
RenderAreaListener	This class can be overridden by an application to receive notifications from a RenderArea.
Service	Defines the RemoteViz rendering service.
ServiceListener	This class can be overridden by an application to receive notifications from the rendering Service.
ServiceSettings	Settings that define the rendering Service.

Enum Summary

Enum	Description
EncodedFrame.EncodingFormats	Encoding format.
FrameEncoders.Encoders	Frame encoder.
FrameEncoders.Status	Frame encoder status.
ServiceSettings.Extensions	Each enumeration represents an Open Inventor extension.
ServiceSettings.RunModes	The run mode is used to change the behaviour of the RemoteViz execution in three environments.
ServiceSettings.SecurityProtocols	Each enumeration represents a security protocol.

Package com.openinventor.remoteviz.rendering Description

Overview

Open InventorRemoteViz enables software developers to easily integrate advanced 3D visualization into their web- based applications. It brings rich remote 3D interaction and visualization capabilities to web-based applications, while maintaining a high level of interactivity and visual performance on any display device including tablet, phone, laptop, or workstation.

Principles

Current mobile devices allow for the development of interactive 3D applications that download data and render locally. However, most of these devices have limited bandwidth, computing power and storage capacity, which make visualization and interaction with 3D data very limited. 3D data can be extremely complex in terms of geometry (large number of triangles) and size (large volumetric data). Using local rendering means data transfer time is limited by the network bandwidth, data set size is limited by the local memory and rendering performance and image quality are both limited by the local graphics hardware. Transferring data to a remote device may also not be possible for data security reasons. To face such constraints, Open InventorRemoteViz offers a Client/Service model: the data access, computing, and 3D rendering are performed on the server side by the Open InventorRemoteViz service, while the client application only needs to provide the user interface and display each frame (image) sent from the service. No 3D hardware is required on the client side. 1. The Service is in charge of executing the Open Inventor code:

1. interprets events from client
2. renders scene using Open Inventor
3. sends image to client

2. The Web server serves the web page containing the displaying area.

3. The client:

1. captures user requests and system events
2. sends them to the remote RemoteViz service
3. receives images and displays them

Windows Service

RemoteViz is not usable as Windows Service. Indeed, Windows creates the service processes in an isolated session that does not have access to the video driver (no OpenGL context found). This means that any attempt that a service makes to render graphics fails.

Licensing

RemoteViz is protected by the Open Inventor license key mechanism limiting its usage to specified computers or network environments based on commercial agreements. RemoteViz uses floating license. For each connected client to a RemoteViz service, it requires one Open Inventor license, one RemoteViz license and if Open inventor extensions are used in the RemoteViz service, a license of the extension is also required for each connected client. A client represents an application instance using RemoteViz (client-side). In the case of HTML5 applications, a client is identified for a single instance of a web browser and for a single domain name. For more details about floating server license configuration, please refer to the Open Inventor licensing section.
To use an Open Inventor extension with RemoteViz, please refer to the documentation of the method RemoteViz.Rendering.ServiceSettings.setUsedExtensions.

Run a demo

We will start RemoteViz in your own machine, this means that the server will run on your local machine.

1. Go to "OIVHOME/examples/bin/OIVARCH/RemoteViz" and run "RemoteVizHelloConeRenderingService.exe". (By default, the HelloCone sample uses the port 8080)
   WARNING: Note that if the selected port is used, an error will occur. Refer to reference manual to solve this problem.

2. Go to the folder "OIVHOME/examples/source/RemoteViz/HelloCone/Clients/HTML5" and open the "index.html" file inside a web browser. The HelloCone application will do the rendering and you will obtain a web page with the rendering of the scene graph.

   

3. Now you can use the mouse to interact with the scene.

   Mouse interactions:
   Mouse left button: spin the scene.
   Mouse move + Ctrl key: pan the scene.
   Mouse Wheel: Dolly/zoom camera.
   

4. Touch interactions:

   1 finger: spin the scene.
   2 fingers rotate on the screen plan: zoom and pan (rotation and zoom center are located between the fingers).
   Double tap: view the entire scene.
   

5. You can open again the index.html file then several clients are connected to the service; they will share the same rendering and send their own requests.

Build a demo

Build using VC++ Project on Windows

a. Start Visual Studio: open solution file: "OIVHOME/examples/source/RemoteViz/RemoteVizExamples.sln".

b. Select the Release or Debug configuration according the value of the environment variables and build RemoteVizHelloCone project.

REMARK: the HelloCone project requires the SceneExaminer dependency. This one manages the application camera and is delivered with the Open Inventor package. Its behavior can be overridden by modifying the SceneExaminer project (OIVHOME/source/Inventor/gui/ViewerComponents).

Regenerate project using CMake (Windows and Linux)

Run CMake to generate the Visual Studio solution on Windows and Makefiles on Linux
a. Set following parameters:
Where is the source code = "OIVHOME/examples/source/RemoteViz/HelloCone/HelloConeRenderingService"
Where to build the binaries = <outputCmakeFolder>

b. Select Configure: Generator

c. Select Generate: this command will generate the .sln and .vcxproj files on Windows and Makefiles on Linux in the folder <outputCmakeFolder>.

Demo in Docker

Docker containers wrap a piece of software in a complete filesystem that contains everything needed to run: code, runtime, system tools, system libraries - anything that can be installed on a server. This guarantees that the software will always run the same, regardless of its environment.

Containers running on a single machine share the same operating system kernel; they start instantly and use less RAM. Images are constructed from layered filesystems and share common files, making disk usage and image downloads much more efficient.

Docker can build images automatically by reading the instructions from a Dockerfile. A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Using docker build, users can create an automated build that executes several command-line instructions in succession.

We provide the Dockerfile necessary to build a container image that can run a demo.
A linux distribution is required and NVIDIA graphics card too.

To run a RemoteViz demo, an OpenGL context is required. To get an OpenGL context in a Docker container, you have to install the version of Nvidia drivers matching exactly (major and minor version) the version of Nvidia drivers installed on the host.

Run the RemoteVizHelloCone demo in a Docker container

Be sure you have copied your password.dat in OIVHOME/License folder and set the Open Inventor environment variables: OIVHOME, OIVARCH.
Go to the Docker folder in OIVHOME/examples/source/RemoteViz/Docker.
Open the ReadMe.txt file and follow the instructions.

To go further

The package provides many samples to help you starting with RemoteViz development.

1. BasicHTMLGUI: This example shows you how to interact with the RemoteViz service to change the color of the Cone.
2. BasicJQueryGUI: This example shows you how to use Jquery library in the client-side.
3. ClientWorkbench: This example enables you to load your Open Inventor 3D model and adjust the RemoteViz settings in real-time. This example is provided with a client written in JavaScript using Jquery library and a client written in TypeScript using Angular framework.
4. MobileApp: This example is made for mobile devices. The scene is displayed in full screen.
5. SharedViewer: This example enables you to load your Open Inventor 3D model and share the session between many clients.
6. ConnectionManagement: This example shows you how to filter the client connections (accept or refuse) by using the GET parameters included in the RemoteViz Service URI.
7. InventorApplication: This example shows you how to use RemoteViz with an Open Inventor viewer component. The scene graph is shared between the viewer component and the RemoteViz application.
8. SecureConnection: This example shows you how to enable the secure connection between the server and the clients.
9. IndependentService: This example shows you how to use your own render engine in a RemoteViz application by using the independent service mode.
10. HelloConeH264: This example shows you how to enable H264 encoding in a RemoteViz application. This demo requires an NVIDIA GPU Kepler or higher and CUDA Toolkit 8.0.
11. RemoteVizClientNode: This example shows you how to integrate remote 3D interaction and visualization into an Open Inventor viewer.
12. RemoteVizScreenDrawer: This example shows you how to integrate remote 3D interaction and visualization with a screen drawer into an Open Inventor viewer.

If you want to use RemoteViz with a webserver, please refer to the configuration tutorials in "SetupServers".