Add support for Creo Parametric 3.0 M110

[adamnagel]

OpenMETA's Creo functions are designed to work with Parametric 3.0 M060. Recently I got a chance to test them with M110, and they seem largely to work, although some hacks were necessary to get things running.

This ticket is for capturing the notes I have so far. I'm glad to provide debugging access to the machine running M110, although I don't feel qualified to make the relevant OpenMETA code changes myself.

Registry Key Location

For M060, the Registry Keys for Creo Parametric are expected to be here:
HKLM/SOFTWARE/WOW6432Node/PTC/PTC Creo Parametric/3.0/2015290
For M110, PTC has moved the keys here:
HKLM/SOFTWARE/WOW6432Node/PTC/Creo Parametric/3.0/2016260

Note that "PTC Creo Parametric" has been shortened to "Creo Parametric" and the final key reflects a new date.

Undiagnosed Bug

In operation, there seems to be a difference with how search paths work, and how files are copied into the results folder. This occurs in a proprietary model that I cannot share, but I haven't created an open-source reproduction model yet.

In my model, one OpenMETA Component links to a Creo Assembly, while the rest link to Creo Parts.

If you run META-Link, the model builds and displays properly.

If you run CyPhy2CAD, the operation succeeds. The assembly Component's CAD path appears in config.pro. The resulting Mass, BoundingBox, etc calculations appear to be correct. However, the files for the assembly component are not copied to the results folder, so when you open the system assembly file, those elements are missing.

[ksmyth]

However, the files for the assembly component are not copied to the results folder, so when you open the system assembly file, those elements are missing.

The config.pro file is only read if you double-click in explorer. If you open Creo, then open the file, it will not find the .prts

[robertowens]

In general, I don't think we should copy unmodified files to the results folder. This would be intractable for a large assembly. If you double click on the top-assembly and then from the to-assembly open sub-assemblies, Creo should follow the config.pro paths. Please let me know if this is not the behavior you are seeing.

[robertowens]

Registry Key Location

On my machine, M120 is installed. The registry location follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PTC\PTC Creo Parametric\3.0
My suspicion is that for M110, PTC made a mistake, which they corrected with M120.
There is a Toolkit function (ProEngineerReleaseNumericversionGet()) that returns the version number, but for that to work, Creo would have to be started by the CreateAssembly program. The CreateAssembly program currently reads the registry information before starting Creo. To do otherwise would result in compatibility errors, between the CreateAssembly program and Creo, that would be harder to detect/report. I could add a check in the CreateAssembly program to check for the normal registry location and the M110 location, but it would seem easier to just install M120.

Search Path

With M120 the search path works properly. I am surprised it does not work with M110. There have been issues where double clicking on an assembly tries to open Simulate or a Creo Viewer. The first thing to verify is that double clicking is trying to open Creo. I probably need to see the example to help with this.

[ksmyth]

Search path: the best thing to do is to unselect Creo Simulate when installing, since we aren't licensed for it.

After-the-fact fix: change HKEY_CLASSES_ROOT\creoFile\Shell\Open\Command to Parametric.