When DriveWorks Autopilot is used to round trip through SOLIDWORKS to produce 3D content in a 3D Preview control please use this checklist to ensure everything is set correctly.
DriveWorks 3D Preview takes the first active model it finds in your model rules. It looks in model rules from the bottom up until it finds a viable root component set.
A viable component set is a top-level model with a valid file name.
Component Sets can be bypassed in the model rules tree by setting their file name to "DELETE".
DriveWorks won’t use these models and will move onto the next one
During the Specification, you can set file names to be delete and then at release time you can switch them back so models generate.
When using Autopilot Mode, while specifying with DriveWorks Live, the Preview Service Location setting must be applied in the web.config file. See Configuring the 3D Preview Service Location heading in the 3D Preview Service Location topic.
This is the machine name that has DriveWorks Autopilot installed which is to be used as the 3D preview service.
When using the 3D preview Box control in Autopilot mode a location must be set for the Group Content Folder (see General Settings.)
Make sure you have the DriveWorks 3D Export add in enabled in the SOLIDWORKS application running on the DriveWorks Autopilot machine.
DriveWorks Autopilot must be running as a Windows Administrator. This is so that the 3D Preview service can run and access applications like SOLIDWORKS.
In DriveWorks Autopilot under 3D Preview Settings there is a check box to "Enable 3D Preview".
Make sure this is checked on the machine that you want to generate the 3D Preview.
DriveWorks Applications such as DriveWorks Live and IIS request 3D previews through port 8900. If this port is not accessible, then the requests will not go through.
|Knowledge Base Article Ref:||KB16113001|