HOOPS Visualize 3DF Documentation

Building the Samples and Sandboxes

Below are instructions for building and using the samples and sandboxes available in Visualize downloadable packages. Each section includes a general description along with instructions for building and running the sample application.

The table on the right includes a full list of the available samples, along with the supported OS for each one.

Note: Throughout this document hoops_dir refers to the directory where the HOOPS 3DF package is located on your system.

3D Part Viewer

Description: The Part Viewer is an example of a fully featured application which showcases many of the features available in HOOPS. For a full description of the functionality available in this application, please visit: Reference Applications section.

Availability: Windows only

How to Run:

Launch hoops3dpartviewer.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the hoopspartviewer project and choose 'Build'

Command Line Arguments:

The 3D Part Viewer supports limited command line arguments to make it faster to load and export files. They follow this pattern:

hoops3dpartviewer.exe [input_file] [options]

Valid values for options are:

Command Line Argument	Description
–help, -h	Shows usage message
–output, -o <output_file_name>	Name of file to export

When an input file is specified, it is loaded at startup. If an input file is specified, an output file can optionally be passed as well. This will cause the application to export the file as soon as it is loaded. The export format will be implied based on the extension of the output file name.

C# Simple

Description: Sample application built with the intent to show how to use the C# 3DF API together with Windows Forms GUI toolkit. It allows users to load HSF and HMF files, create spheres, cones, cylinders and annotations. When the orbit operator is active, the camera can be orbited using the left mouse button, panned using the right mouse button, and zoomed using the mouse wheel. The scene can be sent to a printer, and the code shows how hardcopy support can be added to a C# application. It is meant as a starting point for customers to prototype their applications. It uses the DirectX 11 driver by default.

Availability: Windows only

How to Run: Launch csharp_simple.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.cs, if you haven't done so already
Right-click on the csharp_simple_cs project and choose 'Build'

Cocoa Simple

Description: Cocoa Simple shows customers how to add HOOPS Visualize to a MacOS application built using the Cocoa GUI toolkit. It allows users to load HSF and HMF files, manipulate the camera and add annotations to the scene.

Availability: MacOS

How to Run: Launch cocoa_simple.app from hoops_dir/bin/<platform>

How to Build:

Open the samples XCode workspace from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Select the cocoa_simple scheme and choose Build

Holographic Remoting Simple

Description: The Holographic Remoting Simple sample shows how to create an AR application which renders its content locally on a machine but is displayed remotely on the HoloLens.

It is meant as a starting point for customers to prototype their applications.

Availability: Windows only

How to Run:

Make sure that your HoloLens is turned on, and connected to a Wi-Fi network
From the HoloLens start the Holographic Remoting app. If this app is not present, you will have to download it from the Windows Store on your HoloLens. It is available at no charge.
Note the IP address listed in the Holographic Remoting app. Leave the app open on the HoloLens.
Using the Command Prompt navigate to hoops_dir/bin/<platform> and launch holographic_remoting_simple_v<version>.exe passing to it the appropriate command line arguments

Command Line Argument	Description
`-ip <ip_address>`	IP address of the HoloLens, acquired in step 3. This argument is required.
`-filename <file_to_load>`	Path to the file to load in the application. Only HSF, HMF, STL and OBJ files are supported by this sample.
`-scale <model_scale>`	Amount by which to scale the model. Defaults to 1
`-offset <offset_x,offset_y,offset_z>`	Three comma-separated numbers which indicate the amount by which to translate the model along the X-, Y- and Z-axes respectively. Example: `-offset 1,0,0` Defaults to no offsets

Once the window pops up on the desktop, press the space bar to connect to the HoloLens remotely. You should be able to see the model through the headset now.
While the remoting demo is running you can interact with the scene from the HoloLens in the following ways: a. A single tap will position the model where your gaze is b. Tapping and holding, and then moving your hand left or right will rotate the model in that direction

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the holographic_remoting_simple project and choose 'Build'

Hololens Simple

Important: The Hololens Simple project is only available in 32-bit packages of Visualize – please be sure to download the 32-bit package to access this sample.

Description: This sample project is named hololens_simple, which is located in demo/uwp and can be accessed via the samples_arvr_v141 solution in the root folder of the Visualize package. In contrast to the HoloLens remoting sample, this sample creates an application to be deployed directly onto the HoloLens hardware.

Native HoloLens applications are compatible with the DX11 graphics driver only. Additionally, they require the HOOPS UWP libraries, as well as the ability to build UWP apps (Visual Studio should prompt you to install the requirements if they aren't already present).

For compatibility with the 32-bit HoloLens hardware, the sample is configured to generate 32-bit binaries.

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the hololens_simple_v1xx project and choose 'Build'

Adding HoloLens Native to Your Application

In order to add native HoloLens support to your application, the following items are required:

A HoloLens headset
HoloLens is currently only supported on Windows Desktop, when using the C++ API, and the DirectX 11 driver.

Here are the basic steps for setting up your application:

Set Up PC and HoloLens

You must enable Developer mode on both the PC and HoloLens, and pair the devices, to allow deployment from Visual Studio on the PC to the HoloLens device. For details, see Microsoft's documentation here: https://docs.microsoft.com/en-us/windows/mixed-reality/using-visual-studio

How to Run:

Right-click and select Set as Startup Project.
Select the preferred Solution Configuration (Debug or Release).
Set your deployment target to device.
When deploying your application to the HoloLens, your package must include the HSF file of the model you want to view. To add a new HSF file for viewing in the Hololens, in the Solution Explorer under the hololens_simple project, right-click Content and select Add->Existing Item
Right-click on the model you just added, select Properties, go to the General section, in the Content field change the value to Yes.
To set the model in your application, change the filename variable in hololens_simpleMain.cpp to the name of your HSF file.

Java Simple

Description: Sample application built with the intent to show how to use the Java 3DF API with the Java AWT GUI toolkit. This application provides basic functionalities, like loading files, manipulating the camera, creating simple geometries and selecting parts in the scene. It is meant as a starting point for customers to prototype their applications. It uses the OpenGL driver by default.

Availability: Available on Windows, Linux and MacOS

How to Run:

Windows:
1. Make sure that the JDK binary folder is somewhere in your system's PATH, so that Java can be used from any directory.
2. From the command prompt, navigate to hoops_dir/bin/<platform> and execute this command:
  java -jar java_simple.jar

Linux:
1. From the terminal, navigate to hoops_dir/bin/<platform>
2. Make sure that Java is somewhere in your path. To verify, try executing the 'java -version' command from the terminal and verify that the version of Java you have installed is returned to you as a string
3. Add the current directory to LD_LIBRARY_PATH by executing this command:
  export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.
4. Launch java_simple using the following command
  java -jar java_simple.jar

How to Build:

There are a few important notes about building java_simple, which apply to all the platforms:

The Java JDK needs to be installed on your system before building samples which use Java.

Debug Java 3DF wrappers are not being distributed at this time. This means that even when building java_simple in debug mode, it should target the release version of 3DF libraries.

If you have not already done so, open java_simple.java, found in hoops_dir/demo/java/java_simple and add your HOOPS license in the constructor of the JSimpleApplication class

Building java_simple in 32-bit mode on a 64-bit system using a 64-bit JDK installation is not allowed.

Windows:

METHOD 1: Using Visual Studio in Release Mode

Open the samples solution from the main hoops directory
Add the java_simple_v<version>.vcxproj project, found at hoops_dir/demo/java/java_simple to the samples solution
Make sure the solution is in Release configuration
You will need an environment variable named JDK_INSTALL_DIR which points to the directory containing the Java Development Kit.
Right-click on the java_simple project and choose 'Build' Once the project is built using Visual Studio, it can be launched using the command line instruction detailed in the How to Run section.

METHOD 2: Using Visual Studio in Debug Mode

Open the samples solution from the main hoops directory
Add the java_simple_v<version>.vcxproj project, found at hoops_dir/demo/java/java_simple to the samples solution
Make sure the solution is in Debug configuration
You will need an environment variable named JDK_INSTALL_DIR which points to the directory containing the Java Development Kit.
Because Debug 3DF Java wrappers are not distributed, the debug version of the project needs to be changed to link against the release 3DF Java wrappers as follows:
1. Right-click on the java_simple project and choose Properties
2. Click on Configuration Properties and then NMake
3. Under General expand the Build Command Line setting
4. Change the name of all the directories mentioned so that they don't end with 'd'. Example:
  
  Change:
  ..\..\bin\nt_x64_v141d\HJ$(HOOPS3DFVER).jar
  
  to
  ..\..\bin\nt_x64_v141\HJ$(HOOPS3DFVER).jar
5. Click OK to confirm the property changes
6. Right-click on the java_simple project and choose 'Build'

Once the project is built using Visual Studio, it can be launched using the command line instruction detailed in the How to Run section.

METHOD 3: Using Eclipse

Start Eclipse and click on File / New / Java Project
Give the project a name, and click Next
Click on the Libraries tab and then on the Add External JARs… button
Navigate to hoops_dir/bin/<platform> and choose the following libraries:
1. HCanvas<version>.jar
2. HIJ<version>.jar
3. HJ<version>.jar
4. HJCanvas<version>.jar
5. HJMVO<version>.jar
6. HJSTREAM<version>.jar
Click Finish
Using Windows Explorer, navigate to the source folder which was created as part of the project. Unless the default location was changed, it should be located in C:/Users/<user>/eclipse-workspace/<project_name>/src
Create a directory called 'com', within it create a directory called 'techsoft', and within this last directory, create another one called 'hoops', so that a directory structure like this one can be found: C:/Users/<user>/eclipse-workspace/<project_name>/src/com/techsoft/hoops
Copy java_simple.java, found in hoops_dir/demo/java/java_simple to the directory created in the previous step
Back in Eclipse, click on File / Refresh to update the project to include the new directories which were created in the previous steps. The java_simple.java file should now be visible within the Package Explorer pane.
Click on Run / Run Configurations and double click on Java Application on the left pane.
From the Main tab, click the Search… button and choose java_simple from the dialog which pops up.
From the Arguments tab, in the Working Directory section, choose Other, then click on the File System… button. Choose the 3DF folder where the 3DF libraries are located (hoops_dir/bin/<platform>)
Click Apply and then Run When using Eclipse with Java support as your IDE, java_simple can be run directly from it, rather than using the command line.

Linux: Building Java Simple in Release mode

Before starting, make sure that both the Java JDK and JRE are installed on your system. The bin folder of the JDK should be in your system's PATH. To check that this is the case, verify that './javac' can be called from any directory.
Navigate to the following directory /usr/lib/jvm And create a symlink to the directory where your Java JDK is located as follows:

sudo ln -s <path to the JDK directory> java-6-sun

It is important that the name of the symlink be exactly java-6-sun

Navigate to the main hoops directory, and use the following command to compile java_simple:
make java_simple CONFIG=release

Building Java Simple in Debug mode

Linux packages of HOOPS Visualize 3DF do not ship with debug libraries, but our makefiles are nevertheless setup to try to link against the debug version of our libraries when building a project in debug mode. Because of this, our makefiles need to be modified before building the Java Simple application in debug mode.

Before starting, make sure that both the Java JDK and JRE are installed on your system. The bin folder of the JDK should be in your system's PATH. To check that this is the case, verify that ./javac can be called from any directory.
Navigate to the following directory /usr/lib/jvm, and create a symlink to the directory where your Java JDK is located as follows:

sudo ln -s <path to the JDK directory> java-6-sun
It is important that the name of the symlink be exactly java-6-sun
Navigate to hoops_dir/demo/java and open the java.mk file with a text editor and perform the following edits:

a. Comment out the project dependencies as follows
JS_DEPS = \
# libhoops_utils.a \
# libhoops$(HOOPS3DFVER).so \
# libhoops_stream.a \
# libhoops_mvo_mgk$(HOOPS3DFVER).so
Since we want to link against the release version of the HOOPS libraries, which are distributed with the package, there is no need to rebuild them.

b. Comment out the make commands for directories other than java_simple as done above, by prepending '#' to the line containing those instructions

c. Change this line:

cd ./demo/java/java_simple && BIN_PATH=../../../

to this:

cd ./demo/java/java_simple && BIN_PATH=../../../bin/linux_x86_64
Navigate to the main hoops directory, and use the following command to compile java_simple:

make java_simple CONFIG=debug

The resulting debug application will be created in the release bin directory (i.e., hoops_dir/bin/linux_x86_64)

Java Simple SWT

Description: Sample application built with the intent to show how to use the Java 3DF API with the Java SWT GUI toolkit. This application provides basic functionalities, like loading files, manipulating the camera, creating simple geometries and selecting parts in the scene. It is meant as a starting point for customers to prototype their applications. It uses the OpenGL driver by default.

Availability: Windows only

How to Run:

Make sure that the JDK binary folder is somewhere in your system's PATH, so that Java can be used from any directory.
From the command prompt, navigate to hoops_dir/bin/<platform> and execute this command:
java -jar java_simple_swt.jar

How to Build: There are a few important notes about building java_simple, which apply to all the platforms:

The Java JDK needs to be installed on your system before building samples which use Java.

Debug Java 3DF wrappers are not being distributed at this time. This means that even when building java_simple_swt in debug mode, it should target the release version of 3DF libraries.

If you have not already done so, open java_simple_swt.java, found in hoops_dir/demo/java/java_simple_swt and add your HOOPS license in the constructor of the SWTApplication class

Building java_simple_swt in 32-bit mode on a 64-bit system using a 64-bit JDK installation is not allowed.

METHOD 1: Using Visual Studio in Release Mode

Open the samples solution from the main hoops directory
Add the java_simple_swt_v<version>.vcxproj project, found at hoops_dir/demo/java/java_simple_swt to the samples solution
Make sure the solution is in Release configuration
You will need an environment variable named JDK_INSTALL_DIR which points to the directory containing the Java Development Kit.
Right-click on the java_simple_swt project and choose 'Build' Once the project is built using Visual Studio, it can be launched using the command line instruction detailed in the How to Run section.

METHOD 2: Using Visual Studio in Debug Mode

Open the samples solution from the main hoops directory
Add the java_simple_swt_v<version>.vcxproj project, found at hoops_dir/demo/java/java_simple to the samples solution
Make sure the solution is in Debug configuration
You will need an environment variable named JDK_INSTALL_DIR which points to the directory containing the Java Development Kit.
Because Debug 3DF Java wrappers are not distributed, the debug version of the project needs to be changed to link against the release 3DF Java wrappers as follows:
1. Right-click on the java_simple_swt project and choose Properties
2. Click on Configuration Properties and then NMake
3. Under General expand the Build Command Line setting
4. Change the name of all the directories mentioned to not end with 'd'
  
  Example:
  
  Change
  ..\..\bin\nt_x64_v141d\HJ$(HOOPS3DFVER).jar
  
  to
  ..\..\bin\nt_x64_v141\HJ$(HOOPS3DFVER).jar
5. Click OK to confirm the property changes
Right-click on the java_simple_swt project and choose 'Build'. The resulting debug application will be created in the release bin directory. Once the project is built using Visual Studio, it can be launched using the command line instruction detailed in the How to Run section.

METHOD 3: Using Eclipse

Start Eclipse and click on File / New / Java Project
Give the project a name, and click Next
Click on the Libraries tab and then on the Add External JARs… button
Navigate to hoops_dir/bin/<platform> and choose the following libraries:
1. HCanvas<version>.jar
2. HIJ<version>.jar
3. HJ<version>.jar
4. HJCanvas<version>.jar
5. HJMVO<version>.jar
6. HJSTREAM<version>.jar
7. HoopsSwtCanvas<version>.jar
8. swt.jar
Click Finish
Using Windows Explorer, navigate to the source folder which was created as part of the project. Unless the default location was changed, it should be located in C:/Users/<user>/eclipse-workspace/<project_name>/src
Create a directory called 'com', within it create a directory called 'techsoft', and within this last directory, create another one called 'hoops', so that a directory structure like this one can be found: C:/Users/<user>/eclipse-workspace/<project_name>/src/com/techsoft/hoops
Copy java_simple_swt.java, found in hoops_dir/demo/java/java_simple_swt to the directory created in the previous step
Back in Eclipse, click on File / Refresh to update the project to include the new directories which were created in the previous steps. The java_simple_swt.java file should now be visible within the Package Explorer pane.
Click on Run / Run Configurations and double click on Java Application on the left pane.
From the Main tab, click the Search… button and choose java_simple_swt from the dialog which pops up.
From the Arguments tab, in the Working Directory section, choose Other, then click on the File System… button. Choose the 3DF folder where the 3DF libraries are located (hoops_dir/bin/<platform>)
Click Apply and then Run When using Eclipse with Java support as your IDE, java_simple_swt can be run directly from it, rather than using the command line.

MFC Simple

Description: Sample application built with the intent to show how to create an MFC application using the MVO API. Users can load HSF and HMF files.

Interaction with the scene consists of standard camera manipulation (pan, zoom, orbit, zooming to extents and zooming to a particular area), as well as the ability to create cylinders, cones, spheres.

Users can also select and highlight geometry using the Select by Window operator.

Three different render modes are exposed through the View menu (Gouraud, Hidden Line and Wireframe).

Finally, the scene can be copied to the system clipboard or sent to a printer.

An extra, unused button is added at the end of the toolbar so that customers can quickly add and try some code in the application. It is meant as a starting point for customers to prototype their applications.

Availability: Windows only

How to Run: Launch mfc_simple.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the mfc_simple project and choose 'Build'

MFC Simple – 3DGS Only

Description: MFC Simple – 3DGS Only is a stripped-down version of the MFC Simple application. It only links against the main HOOPS Visualize library, showing customers how to write an MFC application when they do not wish to use the MVO component of Visualize.

This sample is relevant for customers who wish to handle input from the user from an MFC application, but without using MVO. It supports loading HMF files, changing render modes and orbiting the camera.

Availability: Windows

How to Run:

MFC Simple – 3DGS Only needs to be built before it can be run. Please see the next section for instructions on how to build it.

Once it is built, it can be run as follows:

Launch simple.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the simple_v<version> project and choose 'Build'

NVIDIA Profile Creator

Description: This sample and associated project can be found in the demo/win32/nvapi_profile_creator directory.

This sample helps address the limitations of GPU selection using Set_Driver_Options("gpu preference = [xxx]"). nvidia_profile_creator demonstrates how to programmatically create an application profile that will make the NVIDIA GPU the preferred GPU for a particular application. As such, this method for GPU selection will only work on laptops with NVIDIA GPUs, and it will only work on Windows.

This is the programmatic equivalent to launching the NVIDIA Control Panel, adding a new application, and setting this preference via its GUI. This allows the discrete GPU to get used for any driver, and will work for D3DImageCanvas as well.

This sample demonstrates:

Initialize the NVAPI.
Create a new profile with given name.
Delete an existing profile of a given name.
Add an application to the new profile.
Add the settings which will make the NVIDIA GPU the preferred GPU for that application.
Save the profile so it will be used when the application is next launched.

Note that for the profile to have an effect, it must exist prior to launching an application. If an application is already launched prior to the creation of the profile, it will need to be closed and launched again after the profile is created.

We would recommend running this profile creation code as a step in your installer, or as a utility to run on demand.

Availability: Windows. C++ only.

How to Build:

This new sample requires the NVAPI SDK which can be found here: https://developer.nvidia.com/nvapi. It is free, but will require acceptance of a license agreement and a free NVIDIA Developer Account.
You will need to define an environment variable named NVAPI_DIR which points to the extracted location.

Out of Core Pre-Processor (OOC)

Description: The Out of Core Pre-Processor is used to turn ASCII point cloud files into a specially processed HSF file with the .ooc extension. Pre-processing a large point cloud is the first step towards visualizing very large point clouds with 3DF. A full description of the OOC functionality can be found in the OOC Technical Overview.

Availability: Windows only

How to Run:

Launch ooc.exe from hoops_dir/bin/<platform>, providing appropriate command line arguments. ooc.exe can be launched with the –help command line to see a description of all the available options.

How to Build: ooc.exe cannot be built by the user.

OpenVR Simple

Description: OpenVR Simple shows how to create a simple VR viewing application. The user can use this application to see how to use the VR API, how to collect data from VR controllers and how to create VR operators to interact with the scene. If two controllers are connected, the user will be able to move, rotate and scale the model, and to highlight parts of it. It is meant as a starting point for customers to prototype their applications.

Availability: Windows only

How to Run: Launch openvr_simple_<version>.exe from hoops_dir/bin/<platform>, providing appropriate command line arguments.

There are two command line options which can be passed to openvr_simple:

Command Line Argument	Description
`-filename <file_to_load>`	The file to load in VR
`-driver <driver_name>`	The driver to use. Valid options are dx11 and opengl2. Defaults to dx11.

A VR headset that supports OpenVR needs to be connected before launching OpenVR Simple.

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
You will need an environment variable named OPENVR_SDK which points to the directory containing the OpenVR SDK. The OpenVR SDK can be downloaded from: https://github.com/ValveSoftware/openvr
Right-click on the openvr_simple project and choose 'Build'

Parasolid Part Viewer

Description: The Parasolid Part Viewer is an example of a fully featured application which showcases how developers can use Parasolid together with HOOPS. For a full description of the functionality available in this application, please visit the Reference Applications section.

Availability: Windows only

How to Run: Launch parasolidpartviewer.exe from hoops_dir/bin/<platform>

How to Build: Prerequisites:

You will need an environment variable named PARASOLID_INSTALL_DIR which points to the directory containing the supported version of Parasolid. You can find which version of Parasolid is supported by which version of HOOPS from the Release Notes.
The directory pointed to by the PARASOLID_INSTALL_DIR environment variable should contain all the different versions of Parasolid you are interested in for a release. For example, if you are using Parasolid 30, and are interested in building 64-bit applications for Visual Studio 2017, you should place the appropriate Parasolid version in PARASOLID_INSTALL_DIR/base64_v140.

These are the different directories that our Parasolid projects will look for, based on which compiler you are using:

Visual Studio 2017, for 64-bit applications: PARASOLID_INSTALL_DIR/base64_v141
Visual Studio 2017, for 32-bit applications: PARASOLID_INSTALL_DIR/base32_v141
Visual Studio 2015, for 64-bit applications: PARASOLID_INSTALL_DIR/base64_v140
Visual Studio 2015, for 32-bit applications: PARASOLID_INSTALL_DIR/base32_v140

Building in Release mode

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Add the parasolidpartviewer_v<version>.vcxproj project, found at hoops_dir/demo/mfc/parasolidpartviewer to the samples solution
Make sure that you have fulfilled the Prerequisites listed in the paragraph above.
Right-click on the parasolidpartviewer_v<version> project and choose 'Build'

Building in Debug mode

The Parasolid Part Viewer cannot be currently built in Debug mode from our packages.

Command Line Arguments: The Parasolid Part Viewer supports limited command line arguments to make it faster to load and export files. They follow this pattern:

hoops3dpartviewer.exe [input_file] [options]

Valid values for options are:

Command Line Argument	Description
`--help, -h`	Shows usage message
`--output, -o <output_file_name>`	Name of file to export

Qt Simple

Description: The Qt Simple sample shows how to create a platform independent GUI application which uses the HOOPS API together with Qt. This sample provides basic functionalities, like loading files, manipulating the camera, and creating simple geometries. It is meant as a starting point for customers to prototype their applications.

Availability: Available on Windows, Linux and MacOS

How to Run:

Before attempting to run Qt Simple make sure that Qt is installed on your machine, and that it is somewhere in your PATH.

Windows: Launch qt_simple.exe from hoops_dir/bin/<platform>
Linux: Launch QSimple from hoops_dir/bin/<platform>
MacOS: On MacOS platforms QSimple needs to be built before it can be launched. Please follow the instruction in the MacOS section of 'How to Build' to learn how to build this sample.

How to Build:

Windows:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Add the qt_simple_v<version>.vcxproj project, found at hoops_dir/demo/qt/simple to the samples solution
You will need an environment variable named QTDIR which points to the directory containing the supported version of Qt. You can find which version of Qt is supported by which version of HOOPS from the Release Notes.
Right-click on the qt_simple project and choose 'Build'

Linux:

Building in Release mode

Place your license in hoops_license.h if you haven't done so already
Make sure that Qt is installed in your system. The currently supported version of Qt is 5. The makefile will look in /usr/include/x86_64-linux-gnu/qt5/ for your Qt headers and in /usr/lib/x86_64-linux-gnu/qt5 for your Qt libraries.
Navigate to the main hoops directory, and use the following command to compile QSimple: Make QSimple CONFIG=release

Building in Debug mode Linux packages of HOOPS Visualize 3DF do not ship with debug libraries, but our makefiles are nevertheless setup to try to link against debug version of our libraries when building a project in debug mode. Because of this, our makefiles need to be modified before building the Qt Simple sample in debug mode.

Place your license in hoops_license.h if you haven't done so already
Make sure that Qt is installed in your system. The currently supported version of Qt is 5. The makefile will look in /usr/include/x86_64-linux-gnu/qt5/ for your Qt headers and in /usr/lib/x86_64-linux-gnu/qt5 for your Qt libraries.
Navigate to hoops_dir/demo/qt/qt_simple and open the qt_simple.pro file with a text editor.
Change these lines:

linux*:CONFIG(debug, debug|release) {
    message(Debug build)
    LIBDIR=$${LIBDIR}d
}

To this:

linux*:CONFIG(debug, debug|release) {
    message(Debug build)
    LIBDIR=$${LIBDIR}
}

Navigate to the main hoops directory, and use the following command to compile QSimple: Make QSimple CONFIG=debug

The resulting debug application will be created in the release bin directory (i.e. hoops_dir/bin/linux_x86_64)

MacOS:

Place your license in hoops_license.h if you haven't done so already.
Open the QSimple.xcodeproj XCode project found in hoops_dir/demo/qt/qt_simple.
You will need to set an XCode location named QTDIR which points to the directory containing the supported version of Qt. To set a Location in XCode click on XCode / Preferences / Locations / Custom Paths. You can find which version of Qt is supported by which version of HOOPS from the Release Notes.
Build the QSimple project from XCode

Win32 Simple

Description: Win32 Simple is a sample demonstrating how customers can get started using Visualize with a Windows application, without using the MFC toolkit. This sample is relevant for customers who wish to handle input from the user using only Win32 calls. It supports loading HMF files, changing render modes, camera manipulation, simple geometry creation and selection.

Availability: Windows

How to Run: Win32 Simple needs to be built before it can be run. Please see the next section for instructions on how to build it. Once it is built, it can be run as follows: Launch win32_simple.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.h, if you haven't done so already
Right-click on the win32_simple_v<version> project and choose 'Build'

WPF Image

Description: WPF Image is a simple sample which showcases how to use HOOPS Visualize's C# API in a WPF application which makes use of D3DImage. While there is a performance penalty for using D3DImage, this workflow allows the superimposition of other WPF controls on top of the canvas. This approach is demonstrated in the sample, where all the buttons are WPF button elements floating over the canvas. This application allows the user to load files and to manipulate the camera, as well as toggling shadow visibility for the model. It is meant as a starting point for customers to prototype their applications. It uses the DirectX 11 driver by default.

Availability: Windows

How to Run: WPF Image needs to be built before it can be run. Please see the next section for instructions on how to build it. Once it is built, it can be run as follows: Launch wpf_image.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Add the wpf_image_cs_v<version>.vcxproj project, found at hoops_dir/demo/dotnet/wpf_image to the samples solution
Place your license in hoops_license.cs, if you haven't done so already
Right-click on the wpf_image project and choose 'Build'

WPF Simple

Description: Simple sample application built with the intent to show how to use the C# 3DF API together with WPF GUI toolkit. It allows users to load HSF and HMF files, create spheres, cones, cylinders and annotations. When the orbit operator is active, the camera can be orbited using the left mouse button, panned using the right mouse button, and zoomed using the mouse wheel. The scene can be sent to a printer, and the code shows how hardcopy support can be added to a C# application. It is meant as a starting point for customers to prototype their applications.

Availability: Windows only

How to Run: Launch wpf_simple.exe from hoops_dir/bin/<platform>

How to Build:

Open the samples solution from the main hoops directory
Place your license in hoops_license.cs, if you haven't done so already
Right-click on the wpf_simple project and choose 'Build'

top_level:1