Problem
You have license or compatibility issue when you start using HOOPS Visualize 3DF and HOOPS Exchange together, or if you upgrade to the newer versions.
Solution
1. Identify the compatible versions
HOOPS 3DF version are compatible with specific version of HOOPS Exchange. Please access the release notes page to know what version of HOOPS Exchange you should use.
Example:
- HOOPS 3DF 25.10 is compatible with HOOPS Exchange 2020 SP2
2. Set a fresh installation and test it:
In this example we are using HOOPS 3DF 25.00 and HOOPS Exchange 2020 SP1 on Windows:
- Generate a new license key on our license generator.
- Download a HOOPS Visualize 3DF 25.00 fresh package (vs140 or vs141)
-
Update hoops_license.h
HOOPS_3DF_2500\Dev_Tools\hoops_3dgs\source\hoops_license.h
with the generated key - Download a HOOPS Exchange 2020 SP1 fresh package
-
Update hoops_license.h
HOOPS_Exchange_Publish_2020_SP1\include\hoops_license.h
with the generated key -
If you are using the environment variable
HEXCHANGE_DIR
please make sure it points on HOOPS Exchange 2020 SP1 root directory -
Copy all the content of
HOOPS_Exchange_Publish_2020_SP1\bin\win64
intoHOOPS_VISUALIZE\OFFICIAL\HOOPS_3DF_2500\bin\nt_x64_v141
andHOOPS_VISUALIZE\OFFICIAL\HOOPS_3DF_2500\bin\nt_x64_v141d
-
Build & Run
hoopspartviewer_v141
-
Import the file
HOOPS_Exchange_Publish_2020_SP1\samples\data\catiaV5\CV5_Aquo_Bottle_Aquo Bottle.CATProduct
You should get the following result. That means your license key and binaries for 3DF and HOOPS Exchange are all correct.
If the versions of the Visualize and Exchange binaries are not compatible, the Part Viewer will display a VersionMismatch error. For example,
3. Check your application development set up
- Check all the licences set in your application code by searching for the call to
1HC_Define_System_Options("license = <> ");
- Check the HOOPS Exchange DLL used by your project are the correct ones
-
Check the HIO_Exchange binaries are correct
HOOPS_3DF_2500\bin\nt_x64_v141\hio_plugins\hio_exchange\hioexchange2500_x64.hio
-
If you build HIO_Exchange yourself, be sure
HEXCHANGE_DIR
is correctly set and you build it against the correct version of HOOPS Exchange