3DVIA Composer FAQ
Question: What is the fastest way to import SOLIDWORKS files into 3DVIA Composer? Answer: Install a licensed version of SOLIDWORKS on the same PC that Composer is installed on (ensuring that version of SOLIDWORKS is supported for use with the version of Composer in use; see S-055391) - In SOLIDWORKS, disable "Large Assembly Mode" (System Options > Assemblies) and "Automatically load components lightweight" (System Options > Performance) - Run this licensed version of SOLIDWORKS alongside Composer - In Composer, ensure that the version of SOLIDWORKS that is running is chosen in Application Preferences > Input - In Composer, enable the "IOSWImportGraphicData" option in Default Document Properties > Advanced Settings** - Open the SOLIDWORKS file(s) in Composer
**This option was implemented in V6R2012 and has some caveats (refer to Composer's Help for more detailed information on this topic). If the import does not work, or there is a problem with it, then disable this option. For earlier versions of Composer, this solution still applies, minus that step.
Question: Is there a way to merge 3DVIA Composer floating license installation information into the install so that the end user does not have to perform any action to run Composer? Answer: Yes. Floating licensing information for Composer is controlled by one registry key on the client computers. In order to "merge" this with the Composer installation, a registry file must be created that will need to be deployed to the client machines after the install is performed.
The registry key that a floating license, client Composer computer needs is:
"HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager", with a string of, "SEEMAGE_LICENSE_FILE = server name"
A sample registry file is attached (note: if this is used, please edit the file and change the server name to reflect that of the customer's server). After installing Composer, if you apply this registry file to the same computer, and then launch Composer, it will run without needing to enter or input anything.
888.688.3234 | GOENGINEER.COM
Creating a batch file that launches the Composer install, then the registry file would accomplish this in one task.
Question: Question marks display in the user interface (UI) when launching 3DVIA Composer; how can the UI be changed to display one of the supported language's text and characters?
Answer: There are two ways to do this:
1. - Go to Control Panel -> Regional and Language Options - Click the Advanced tab and select the appropriate language for non-Unicode programs - Click Apply and OK and reboot the machine - Launch Composer and go to Application preferences -> General - Select the language needed from the drop down menu - Click the "Reset GUI layout" button and restart Composer
2. - Download the Microsoft AppLocale utility (http://www.microsoft.com/globaldev/tools/apploc.mspx) - Launch this utility and select the "Launch an application" option - Browse to the 3DVIA Composer executable (C:\Program Files\Dassault Systemes\3DVIAComposer\
If at any time the UI contains question marks, then go to Application preferences -> General, click the "Reset GUI layout" button, and restart
Question: Is it required to have a SOLIDWORKS license/install to be able to import SOLIDWORKS files into 3DVIA Composer? Answer: Yes. The import of SOLIDWORKS files into Composer requires the presence of a SOLIDWORKS or SOLIDWORKS Importer installation. The following scenarios are possible:
1. 3DVIA Composer is installed on a computer that does not have SOLIDWORKS installed (user has no SOLIDWORKS licenses). In this scenario, you can either:
888.688.3234 | GOENGINEER.COM
a. Install SOLIDWORKS Importer which allows you to import SOLIDWORKS files directly into Composer b. Export to 3DVIA Composer using the 3DVIA SOLIDWORKS plug-in.
Typically the engineer who created the SOLIDWORKS files can do this using the free 3DVIA SOLIDWORKS plug-in. Installing the plug-in creates a 3DVIA SOLIDWORKS plug-in add-In that can be enabled/disabled in SOLIDWORKS; the add-in enables a menu where files can be exported to the SMG file format.
2. 3DVIA Composer is installed on a computer that does have SOLIDWORKS installed (user has licenses of SOLIDWORKS). If this is the case, then SOLIDWORKS files do not have to be exported to SMGs first. Users may directly open the SOLIDWORKS files in 3DVIA Composer.
3. 3DVIA Sync is installed on a computer that has SOLIDWORKS installed. This tool can be used instead of the 3DVIA SOLIDWORKS plug-in by SOLIDWORKS or non-SOLIDWORKS users to automatically convert SOLIDWORKS files that are present on the computer to the SMG file format.
Note: Starting with 3DVIA Composer V6R2009x HF15, users who do not have SOLIDWORKS installed on the same computer as Composer will be able to directly import files. See solution, S- 033630 for more information.
Question: How is a 3DXML file saved with textures from 3DVIA Composer so that they display when uploading to the file 3DVIA.com?
Answer: Textures are not supported for 3DXML files published from Composer.
However, there is a way to display them on 3DVIA.com. To publish Composer (SMG) files as 3DXML to 3DVIA.com with textures use the Publish to 3DVIA.com functionality and use the "3DVIA Composer Experience" option.
Once an SMG is published in this fashion, go to 3DVIA.com and see the 3DXML file uploaded to the account. Then open the 3DXML and play it. The default player is the 3DVIA Player; as mentioned above, textures will not display in this player. However, publishing using the 3DVIA Composer Experience option enables users to view the 3DXML in the 3DVIA Composer Player, where the textures will display. See the images below showing this:
888.688.3234 | GOENGINEER.COM
888.688.3234 | GOENGINEER.COM
Question: Why is the import of SOLIDWORKS models into 3DVIA Composer slow, even when SOLIDWORKS is already open?
Answer: There are two known scenarios that can cause slow translations even when a session of SOLIDWORKS is already open:
1. If a commercial version of SOLIDWORKS and the SOLIDWORKS Importer are both installed on a machine, and the commercial version is running, SOLIDWORKS Importer will be launched when importing SOLIDWORKS models into Composer.
To resolve this scenario, uninstall either the commerical version of SOLIDWORKS or the SOLIDWORKS Importer.
2. If multiple, commercial versions of SOLIDWORKS are installed, the SOLIDWORKS version specified in Composer's Application Preferences (Input page) is set to "Auto detect", and the newest version of SOLIDWORKS that is installed is NOT open, then the newest version of SOLIDWORKS will be launched in the background to perform the translation, slowing the process.
For example, commercial versions of SOLIDWORKS 2009 and 2010 are installed, the SOLIDWORKS version is set to "Auto detect" in Composer and SOLIDWORKS 2009 is open alongside Composer.
888.688.3234 | GOENGINEER.COM
When a SOLIDWORKS translation is initiated, the active 2009 session is ignored and 2010 is launched to perform the translation.
To resolve this scenario, ensure that the SOLIDWORKS version specified in Composer's preferences is the same as the version opened.
Question: Is a new license file always required for each new major release or hot fix release of 3DVIA Composer? Answer: No. Users do not always have to request a new license when a new version (including service packs) is released. See S-035225 for a customer specific solution.
Composer licensing is dependent upon the version's build date, the license's start date, and its maintenance (entitlement/subscription) end date, if applicable. A license containing maintenance will have either an "S_PublisherMaintenance" (for Composer) or "S_SyncMaintenance" (for Sync) increment in it.
Maintenance Scenario: Composer will run if its build date is equal to or less than the maintenance end date.
No Maintenance Scenario: Composer will run if its build date is less than or equal to the start date plus 30 days.
In either scenario, the error message, "Your maintenance is expired. You must register a new license!", will be displayed when attempting to run a version of Composer that does not abide by the aforementioned rules. A new license file must be requested.
Note: a new license must also be requested if: - the server hosting a floating license is changed - Composer is to be run on a different computer
Question: What does the following error mean when starting up 3DVIA Composer, "Invalid host. The host ID of this system does not match the host ID specified in the license file? Answer: This error indicates one or more of the following problems: - The license file (standalone or floating) contains the wrong host ID for the computer (the license server or a standalone client) - The way in which the computer is connecting to the Internet (its network adapter) has changed since requesting the license - The registry key that dictates where Composer looks for the license is wrong - A floating license has been placed in the standalone license location - There is another license(s) present in the standalone license folder
888.688.3234 | GOENGINEER.COM
Composer licensing is “node locked” to the Host ID of a network adapter. This means that its licensing will only work if the Host ID in the license file matches with the Host ID of an active network adapter.
To isolate what the problem may be:
1. Use knowledge base solution S-016878 to verify that the Host ID is correct. If it is not, that is the problem and a new license file must be requested.
2. Verify that the value of the following registry key is pointing to the correct license file path:
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\SEEMAGE_LICENSE_FILE
3. Verify that the correct license is being used. If a floating license has been placed in the standalone license location, remove it and ensure that Composer has been properly setup for a floating license environment (see S-030095 for detailed instructions how setting this up)
4. Verify that only one Composer license file (Sync, Safe, Check, and Composer Player licenses can coexist in this location):
Windows® XP "C:\Documents and Settings\All Users\Application Data\Dassault Systemes\3DVIAComposer\License"
Windows Vista® / Windows 7 "C:\ProgramData\Dassault Systemes\3DVIAComposer\License"
Question: In a floating license environment, can the 3DVIA Composer add-ons (Safe and Check) be floated to multiple Composer users as is possible with SOLIDWORKS add-ins? Answer: No, 3DVIA Safe and Check licenses cannot be floated to multiple users like SOLIDWORKS add-ins can be. This is because the add-ons cannot be turned on and off in the user interface; SOLIDWORKS add-ins can be thus its licenses can be floated to multiple users.
Example: a user has 3 Composer licenses and 2 Safe licenses. If two users start Composer, they will take 2 Composer licenses and 2 Safe licenses. If the third user wants to use Safe, one of the other users will have to close Composer to free up a Safe license.
Note: Sync licenses can be floated between multiple users. Sync is a separate product and does not need to be installed for all users, thus its licenses are available to those users who chose to launch Sync.
888.688.3234 | GOENGINEER.COM
Question: Why does the geometry of Pro/ENGINEER® files import poorly into 3DVIA Composer? Answer: For Pro/ENGINEER files, 3DVIA Composer uses reverse-engineering tools to import the geometry. This means that the models are not loaded into session during import. The files are only read and their geometry is directly extracted. This can cause problems with any Pro/ENGINEER object that requires regeneration when it is opened in Pro/ENGINEER.
Objects like cabling and assembly cuts are not stored in Pro/ENGINEER .prt and .asm files; they are regenerated and created when the part/assembly is loaded into a session of Pro/ENGINEER. Instanced objects can also cause problems unless instance accelerator files (.xpr and .xsm files which can be read by the Composer importer) are used.
These problems can be minimized by first opening the entire assembly in Pro/ENGINEER (where all the necessary regenerations of the geometry will occur), and then exporting it to a neutral 3D file type (for example, a STEP or IGES file). This way, the Pro/ENGINEER files' proper geometry can be read by the Composer importer.
Furthermore, Composer offers relative and absolute refinement options for the import of any file type. Information on these options can be found in the Composer help file in the "Default Document's Properties - Input" section.
Question: Is there any advantage to using the import option, "Merge file into one actor per part", when importing SOLIDWORKS files into 3DVIA Composer? Answer: Yes, there are a few advantages:
1. Update 3DVIA Composer Document will work even when body names change in 3DVIA Composer. 2. The assembly tree will closely resemble that of the SOLIDWORKS FeatureManager design tree, in that part file names will be applied to the body node in the Composer assembly tree. 3. Multi-body parts will be imported as one body. 4. Using this option will help to reduce file size.
Note: If this option is not selected, then bodies will be imported into Composer. This will result in the Composer assembly tree displaying the part with an assembly icon and the body with a part icon.
Question: Is it possible to see who is currently using a 3DVIA Composer license? Answer: There is no direct interface to check this information. However the log file stores information on the activity on the server. From there it is possible to find out which user has taken the license. After launching license management, go to the config services tab and select "View Log".
888.688.3234 | GOENGINEER.COM