IMAGINiT Technologies Support Blog

NEW Home for the IMAGINiT Support Blog

Our team enjoys providing tips and tricks, beyond what you read here on the blog. Check out our new home on the IMAGINiT Technologies Resource Center.

There you'll find many of our older posts, as well as on-demand webcasts, video tips, ideas for future improvement, and more. 

Content from our amazing technical team will continue! We hope you’ll join us: https://resources.imaginit.com/support-blog.

Design Review Fails to Open DWG Files

By: Heath White | SR. MFG Support Specialist

Issue:
When attempting to open a DWG file in Autodesk Design Review nothing happens and there is no error shown. The image below is what you would see, and the Open command remains available. Other file types open without issue.

Causes:
Design Review by itself cannot process DWG files. It requires an installation of DWG TrueView to process DWG files. The other piece of the puzzle is the fact that for this to work, you not only have to install DWG TrueView, but it must be the same version as your Design Review installation.

Autodesk has not released a new version of Design Review since 2018, which many users are not aware of. That means that to have the capability to open DWG files inside of Design Review, you will need to install DWG TrueView 2018.

Solution:
Autodesk has several KB articles regarding this issue, however, several of the articles involve extensive troubleshooting steps that in many cases are not necessary to resolve this issue. We encourage you to try this simple fix prior to attempting the more complex solutions.

Download the version of DWG TrueView that is the same version as your installation of Design Review. In most cases this will be DWG TrueView 2018. If you have an older version of Design Review, you can download previous versions of DWG TrueView from the following link:

https://knowledge.autodesk.com/support/dwg-trueview/learn-explore/caas/sfdcarticles/sfdcarticles/Where-to-download-previous-versions-of-DWG-TrueView.html

System Requirements for DWG TrueView 2018:

https://knowledge.autodesk.com/support/dwg-trueview/learn-explore/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-DWG-TrueView-2018.html

If you have downloaded and installed the compatible version of DWG TrueView and this did not resolve the issue or if your issue involves crashing, please see the following articles for advanced troubleshooting steps:

https://knowledge.autodesk.com/support/dwg-trueview/learn-explore/caas/sfdcarticles/sfdcarticles/How-to-open-a-DWG-file-in-Design-Review-with-DWG-TrueView-2015.html

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Design-Review-does-nothing-when-a-DWG-file-is-selected-to-open.html

If you are using a much older version of Design Review (i.e. DR 2013), please see the following article for additional resources:

https://knowledge.autodesk.com/support/dwg-trueview/troubleshooting/caas/sfdcarticles/sfdcarticles/Cannot-open-a-DWG-file-in-Design-Review.html

Warning! Problems caused by improperly editing the Windows registry could render your computer/operating system unusable. Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base. Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry as well as the system.dat and user.dat files as outlined for your operating system in the Microsoft Knowledge Base. Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.

IMAGINiT Utilities – How to point a network install to the license server

By: Ken Williams | Tech Support Specialist

Issue:
You install IMAGINiT Utilities on users’ machines and you want to make it a Network and point to the license server easily without opening the program.

Solution:
1. Create a file called IMAGINiTLicense.txt
2. Open IMAGINiTLicense.txt file in Notepad and edit to contain one line.
3. Inside the IMAGINiTLicense.txt file it should say 27051@MyServer
4. MyServer in line 3 is the name of your IMAGINiT Utilities reprise license server.
5. Copy the IMAGINiTLicense.txt file to C:\ProgramData\IMAGINiTTechnologies on as many machines as needed.
6. Now when the IMAGINiT Utilities are open for the first time, it should be set to network and be pointing to the license server.

AutoCAD Raster Design 2021 Background Plotting Does not show Unsaved Images

By: Jeff Arbogast , CSV | Solution Center Team Lead

Issue:
AutoCAD Raster Design 2021 Background Plotting Does not show Unsaved Images.

Causes:
When using Background Plotting unsaved images do not display.

Solution:
You must save unsaved images before Background Plotting or the unsaved image will not Plot the unsaved display.

Creating a Network Deployment for AutoCAD 2021

By: Ken Williams | Tech Support Specialist

About Deployments

A deployment provides an efficient way to install one or more Autodesk products with a standard configuration on multiple computers. The files required for the installation process are stored on the network, in an administrative image, in a folder to which all users have shared access. To install the products, users navigate to the deployment folder and double-click an installer shortcut (.LNK file).

Some essential facts about deployments:
• Deployments can be created for network licenses or multi-seat stand-alone licenses.
• Multiple deployments with different configurations can exist in the same folder, sharing the same administrative image.
• Each deployment installs products in a single language. If you need to install products in different languages, each language requires a separate deployment. For products that support language packs, you can include additional language packs with a deployment.
• An existing deployment can form the basis for creating another deployment with a different configuration.
• Deployments can be configured to generate a log file for each installation. Network administrators can use these log files for troubleshooting.
• Each deployment creates a subfolder, <deployment name>\SMS_SCCM scripts, which contains two documents to help you with the distribution of deployments using Microsoft Systems Management Server (SMS) and System Center Configuration Manager (SCCM): SMS_SCCM_ReadMe.txt and <deployment name>_SCCM.txt. The SMS\SCCM scripts folder also contains two files to help you create a batch file to automate the uninstallation of some or all of the products in a deployment. The two files are <deployment name>_Uninstall.txt and Product_Uninstall_ReadMe.txt.
• Per Autodesk https://knowledge.autodesk.com/customer-service/network-license-administration/network-deployment/overview-deployments/about-deployments

Best Practices for Creating a Deployment

• Create the deployment from a workstation instead of a server. This helps eliminate the need for the same computer to run the installer, read the media, and write the files. The combination of these tasks can increase the time necessary to create the deployment and can cause corruption in the deployment. Create the deployment to a shared network location from an administrative workstation.

• Do not create deployments over WAN or VPN. Connections over a WAN or VPN are typically slow and can cause errors during deployment creation. The deployment creation process may not be completed successfully, or some files may end up missing or corrupt.

• Copy physical media to a hard drive. If you’re working with physical media, copying the entire contents of the product media to a local hard drive can speed up the process of creating a deployment and reduce the potential for corruption. This is even more important when you consider that some product installers copy the data from the installation media to the destination folder multiple times, thus increasing the deployment creation time by a factor of three or more. Copying the product media to a local hard drive helps ensure there are no communication errors with the disk drive and increases the speed of creating a deployment by not having to read data directly from the DVD.

• Disable antivirus software. Antivirus software often causes problems when creating deployments. Active virus scans, where every file being written and read is scanned in real time, can cause the process to take much longer. Additionally, antivirus software can block certain files from being written or can modify those files and cause corruption.

• Create a shared directory. Before creating a deployment, create a shared directory on either a workstation or a server. Keep the share name simple and short; don’t include any spaces in the share name. Don’t bury the shared directory too deeply on a drive.

• Create a separate folder for each deployment image. Creating multiple deployments in a single folder can result in corrupt client installations or other serious problems.

• Create and store deployment images on NTFS filesystems only. Filesystems such as DFS, NFS, AIX, LINUX/UNIX and others are not tested or supported by Autodesk, including filesystems found on network attached storage (NAS) devices.

• Verify that all users have full read/write access to the network share where your deployments are located.

• Use a Uniform Naming Convention (UNC) when specifying network paths instead of using mapped drive letters. For example, use \\server\share\folder instead of M:\folder. Not all computers share the same mapped drive letters and restricting yourself to UNC paths will help avoid problems later.

• Avoid modifying an existing deployment once it is has been used to install a program. Instead, create a new deployment for each modification that you make (for example, when adding profiles, service packs, etc.).

• Avoid moving deployments between servers. If you must do so, you will, at a minimum, need to modify that deployment to insert its current location into the deployment structure.

• Per Autodesk https://knowledge.autodesk.com/customer-service/network-license-administration/network-deployment/overview-deployments/best-practices-for-creating-deployment

Creating the Deployment
1. Log into your subscription account: https://manage.autodesk.com

2. Download the products that you would like to create your deployments for.

3. The default location of the downloaded product will be c:\autodesk. Go into the folder of the product you would like to create a deployment for and choose “Setup.exe”

4. Choose “Create Deployment” from the splash startup screen.

5. Complete the Deployment name and path locations. For the path location use the Universal Naming Convention or UNC path. Choose next
For example: \\Network_Share\Autodesk\deployments\2021\autocad

6. Uncheck the “Create a network log file” box. Leaving this box checked will put a install log file on the server. The user will need write permission on the server log location. There is also an install log file created in the workstation’s Temp folder if needed. Choose next.

7. On the license Agreement page, make sure Country or Region at the top is correct. Make sure “I Accept” is chosen and click next.

8. Product information page – Choose license type. Input serial number and product key. For network license choose a license server model. Enter the license server name (you can insert an IP address for license server instead of the network name if you feel you are having DNS issues). Choose next.

9. Then choose the “Create” button.

10. After the completing the creation of the deployment, on the workstation you need to install the software. Go to the network share where you created the deployment and click on the Deployment name that you created in step #5 to start the install.

Effects of Single User Autodesk Products and your IMAGINiT Utilities

By: Jeff Arbogast , CSV | Solution Center Team Lead

Issue:
You want to know if there are any issues using your IMAGINiT Utilities when you switch to Autodesk Single User Licenses.

Causes:
Autodesk is using a new Single User Licensing model.

Solution:
There is really no effect with our Utilities and the new License model from Autodesk. The Network and Standalone licenses would work the same way.

The Network version would use the Reprise License Manager. When the User launches the Utilities the software would reach out to the server (That has the License Manager on it) and request the license. Once the system knows you have a license available it would start working and take a license from the network while the user was using the license.

The Standalone license, would be activated on the local system and would not need to reach out to a server to function.

One consideration although not an issue is that since the Autodesk licenses are mobile having the Utilities as Standalone would allow the end user to not have to be connected to the Server to use them.

Local Models Not Shown on Home Page

BY: Heath White | SR. MFG Support Specialist

Issue:
Users working in Revit 2019.1 and up (2019.2, 2020, 2021, etc.) report that they do not see their local models listed on the home page under “Recent Files”. Instead, they only see the corresponding central model and are prompted to create a new local model anytime they select the central model.

Causes:
This behavior is functioning as designed.

Solution:
Beginning with the 2019.1 update, users are seeing a newly designed home page that produces a more consistent workflow when collaborating on a workshared project, whether the project is on BIM 360 or the user’s local network. In both cases, a new local model is created each time the central model is selected, so that users do not inadvertently modify the central model.

This designed workflow on the Revit home page is in line with the best practice of creating a new local model when returning to work on a workshared project. Doing so will minimize the issues that occur when a local model and central model become out of sync, leading to data loss.

Additional references:

Revit Worksharing Performance

Revit – What’s New 2019.1 (Official Autodesk Blog)

Autodesk KB Article - Unexpected Generation of Local Models

 

How to determine if Twinmotion is activated and how to activate Twinmotion if it is not already activated

By: Heath White | SR. MFG Support Specialist

Issue:
You have paid for your Twinmotion subscription and you are not sure how to tell if your software is activated. Or you need to know how to activate your software for the first time.

Causes:
There are no, readily available, clear instructions indicating the proper process to activate Twinmotion.

Solution:
NOTE: If you do not already have the Epic Games Launcher, you will need to download the launcher before proceeding.

Please see the following link for instructions on obtaining the Epic Games Launcher: https://www.epicgames.com/help/en-US/epic-games-store-c73/launcher-support-c82/how-do-i-download-the-epic-games-launcher-a3516

Please see the following images and steps to resolve this issue:

If you are running a trial version, you will see the following –

And

To activate your software, please perform the following steps –

1. Go to the Twinmotion tab in your Epic Games Launcher
2. In the lower left corner, Left Mouse Click on your username and Choose “Redeem Code” from the pop-up

3. Then in the web browser window, input your Product Code in the field and hit the “Redeem” button

 

4. Now, go back to the Epic Games Launcher and on the Twinmotion tab, hit the drop-down and choose which version of Twinmotion you would like to install

5. Where the “Launch” button is in the images above, there will be an “Install” button. Select the “Install” button to install your chosen version of Twinmotion
 

6. Once your preferred version of Twinmotion is installed, follow the steps shown below to finalize the activation of Twinmotion

For additional information, please see the following article:

https://twinmotionhelp.epicgames.com/s/article/How-to-install-Twinmotion?language=en_US

Vault Add-In won't load in Inventor-'System.IO.FileNotFoundException...'Autodesk.Inventor.Interop...'

Issue:

The Vault Add-In won't load in Inventor with an error similar to the following:

'System.IO.FileNotFoundException: Could not load file or assembly 'Autodesk.Inventor.Interop, Version=...'

Performing a repair on the 'Autodesk Inventor_version Add-In' in Control Panel doesn't get rid of the error.

Manually trying to load the Inventor Vault and Edm Add-ins keeps them unloaded.

Causes:

The error is caused by a missing folder and .dll file, see this Autodesk article:

"System.IO.FileNotFoundException: Could not load file of assembly 'Autodesk.Inventor.Interop, Version=##.#.#.#..." in Inventor when attempting to use or install the Vault Add-in

For example this based on the error above the following folder is missing:

Solution:

1.Uninstall and reinstall Vault Client to get the folder back.

• Go to Autodesk Account to get a full download: How to download in Autodesk Account
• Or use Autodesk AVA

2.Install the appropriate Vault Client updates based on the updates installed on Vault Server:

• Vault Build Numbers

 

 

Does the AutoCAD for Mac 2019 include the specialized toolsets?

When customers subscribe to AutoCAD 2019, they will have access to AutoCAD, AutoCAD for Mac, plus vertical toolsets for architectural design, mechanical design, electrical design, MEP design, and much more.

AutoCAD specialized toolsets only work on Windows and are not available for Mac users, unless they use a virtual machine running Windows such as Parallels or Bootcamp.

Subscribers to AutoCAD including specialized toolsets will continue to be able to use their serial number and product key to activate AutoCAD for Mac.

BIM 360 - Keys to Getting a "Seat at the Table"

One of the more common issues that our AEC customers encounter is a user being unable to access BIM 360 project files in Revit.  While there are a number of potential causes for this behavior, we have found that most of these cases are a result of the user missing at least one of the following four (4) key requirements:

1. A BIM 360 Design license
   
   
2. Revit Update/Hotfix
   
   
3. An accepted BIM 360 project invitation
   
   
4. Permission to folder

You might compare these fundamental requirements to the legs that support a table as illustrated below.  When one of these legs is missing, access to BIM 360 from Revit, represented by the table top, isn't supported and will fail.  Of course, the table itself needs a supporting surface such as a floor.  In this analogy the floor represents Autodesk's Cloud Services.  If there is a service outage, most, if not all customers will be unable to access BIM 360.

Since the purpose of this article is to help customers do some initial troubleshooting by checking that each of the four "legs" are in place, let's assume that Autodesk's Cloud Services are "Fully Functional".  (Service status can be checked at health.autodesk.com).

 

So if you or another person at your company cannot access BIM 360 projects in Revit, start by making sure you can answer "Yes" to these fundamental questions:

1. Does the user have a BIM 360 Design License assigned?
   • This license is assigned by an Admin or Software Coordinator in the Autodesk Account (manage.autodesk.com).
   • See the steps here for a user to check his/her entitlement.
     
     
2. Does the user have the latest Revit update/hotfix installed?
   • Autodesk released Security Hotfixes for several versions of Revit.  These updates are critical for Revit to connect to BIM 360 Cloud Worksharing.
   • It is always best practice to install all available updates for the version of Revit being used.  You can see available updates by version here:  https://knowledge.autodesk.com/support/revit-products/downloads
     
     
3. Has the user received and accepted the BIM 360 project email invitation by clicking on the "Go to your project" link?
   • Note:  clicking on this link changes a user's project membership from "pending" to "active"
     
     
     
4. Are the user's permissions to the BIM 360 project folder(s) containing Revit files set to a minimum of View + Upload + Download + Edit?
   • User permissions are assigned in the Document Management module by a Project Admin.  If they are not set to the level noted above, the user will not be able to initiate a cloud workshared model to the folder or open/sync a cloud workshared model.
   • See:  Folder Permissions

As stated at the outset, there are several other possible causes that could prevent a user from accessing BIM 360 projects in Revit (i.e. anti-virus/firewall settings; incorrect workflow), but you may find in most cases that once you ensure these four critical "legs" are in place, your team members will have a "seat at the table" and successfully access BIM 360 projects in Revit.