For users new to HOOPS Exchange, we recommend getting started by following these steps:
- Read the Technical Overview and this Getting Started Guide.
- Download and install the HOOPS Exchange package from the Tech 3D Developer Zone. If you are on a Windows platform, you may use either the installer or the zip file. Linux users must use the zip file.
- Begin reading the Programming Guide.
- Build and run the sample applications.
You must have a valid HOOPS Exchange license in order to use this product. Your license key can be generated using the "Generate Key" button located on the HOOPS Exchange downloads page in the Developer Zone. The license is delivered in a file called
A3DSDKLicenseKey.h, which you must compile into your application as part of your source. The file should be placed at
<HOOPS EXCHANGE INSTALL DIR>/include.
The next steps in getting an application up and running depend on whether you are planning to use automatic or manual initialization. More information can be found in the HOOPS Exchange Programming Guide.
Please see our Supported Platforms page for information on which platforms HOOPS Exchange can use.
- <hoops_exchange root directory>
- <platform> (DLLs for Windows and .so for Linux)
- data (sample models, sample code, images)
- exchange (sample applications for HOOPS Exchange)
- publish (sample applications for HOOPS Publish)
Licensees of HOOPS Publish enjoy a high-level of responsive support both from the core team located in Lyon, France, and from the local teams based in each major territory worldwide. If you require help getting started, in the first instance please contact your Consulting Engineer or Account Manager, who will direct you to the appropriate support channels.
The HOOPS Exchange help files are available:
- Online, at the HOOPS Developer Zone. Note that this area is password protected - please contact your Consulting Engineer or Account Manager if you do not have a password.
- In the HOOPS Exchange installation in the
The online documents provide a free-form text search. To search the documentation in the download package we recommend using a standard free-form text search such as grep, Windows Search, or Visual Studio's "Find in Files".
If you are already a user of HOOPS Exchange, or plan to evaluate HOOPS Publish along with HOOPS Exchange, please be aware that the two libraries share some technology. For this reason, HOOPS Publish and HOOPS Exchange are bundled in the same package. The installer allows you to install either or both SDKs. Please note that a joint license code is required to use HOOPS Exchange and HOOPS Publish together. Your license code is generated based on your Tech Soft 3D customer account details.
The installer places both HOOPS Exchange and HOOPS Publish in the same directory. Some libraries are shared between Publish and Exchange, and the two products share the same
bin directory. Distributing your Application Page lists which libraries are necessary for Exchange. The Publish version can be found here.
HOOPS Visualize is a 2D and 3D development platform for creating or enhancing professional-grade engineering applications. Visualize’s rich set of APIs enable developers to work from a very high level, dramatically jump-starting application development. Programming teams using HOOPS Visualize are able to produce more competitive applications and accelerate product delivery while reducing total research and development costs.
If you are an HOOPS Visualize user, you can use HOOPS Exchange to import CAD models directly into HOOPS Visualize using the MVO HIO Module
hio_publish (for Visualize 3DF), or the
HPS::Exchange classes (for Visualize HPS). The models may then be viewed, manipulated and exported using any of our supported exporters.
For more information, please see the HOOPS Visualize documentation.
- Care must be taken when using HOOPS Exchange along with HOOPS Visualize. The API functions related to edition are not meant to be directly used with Exchange to avoid inconsistency between Exchange and Visualize. These functions are:
Note that when a license for one product stops, that license will also stop for the other product*. Therefore care must be taken if you are a licensed user of one product and are evaluating the other, or if you have concurrent evaluations running that end on different dates. Once an evaluation license has expired you may need to revert to the original license for the licensed product. We advise you to always keep a secure copy of any licenses you generate along with the included products and termination dates.