And don't forget to register for the upcoming What's New with Autodesk InfraWorks and Civil 3D webcast, on April 19th. Ever wonder what Autodesk is thinking when we release new features? Why certain additions, improvements, and enhancements are or are not included in the latest releases of Autodesk InfraWorks and AutoCAD Civil 3D? This webcast will be your chance to find out, provide comments, and ask questions.
You 'll also probably want to review some of our handy What's New guides and other learning materials as you get acquainted with this newest version of InfraWorks. Here's an overview of free learning resources available to you:
One of our stellar premium support specialists, Louisa Holland, recently put together a great overview of hardware specs and recommendations for InfraWorks and Civil 3D. I thought her recommendations were spot-on, so I wanted to share them with you here. Keep in mind, that this is not an endorsement of any specific hardware companies, nor a list of formal system requirements -- but more of a helpful tip for some nice options, based on experience working in Civil 3D and InfraWorks.
You can find minimum system requirements and Autodesk's Certified Hardware Page here:
This document is meant to provide a comparison guide between currently available hardware technology with respect to working with Civil 3D and Infraworks. When it comes to Civil 3D and Infraworks, there is no such thing as “too much” RAM or graphics capability. On the Ideal side of this chart, Lou put forth suggestions that are high end, but fall within a realistic budget.
*Since AutoCAD is not multithreaded, fewer cores with stronger individual cores is preferable.
** Memory and storage are effectively commodified resources; brand and/or manufacturer makes very little difference.
Nearly all Autodesk products can be installed via a deployment. This holds true for Autodesk InfraWorks, although there are a few key distinctions about how to create a deployment for InfraWorks versus some other Autodesk products. Backing up a little bit -- a deployment is an efficient way to install one or more Autodesk products with a standard configuration on multiple computers. The files required for installation are stored on a workstation in the network, in a folder from which the product can be distributed to all workstations. Typically, this is a task that a Software Administrator will perform.
The main difference for installing InfraWorks to multiple seats through a deployment is that InfraWorks does not reach out to a network license server to determine who is licensed. Instead, InfraWorks communicates with cloud services to determine if you are entitled to the product once you log in. Therefore, to create a deployment of InfraWorks, you must create a multi-seat standalone deployment that does not connect to a license server but instead allows you to push an installation package out to multiple machines.
So, this article explains how to create a multi-seat standalone deployment for InfraWorks. Use this procedure to create a new deployment from the installer. In the process, you can create a default deployment by accepting the default configuration, or you can create a custom deployment by customizing the settings in the deployment.
Our intrepid product manager has started a practice of publicly posting the development roadmap for InfraWorks 360, and the latest update to our roadmap is now live on the community forum. Please give it a read, feel free to leave comments, and give Sarah a kudo for giving you insight into where the future of InfraWorks 360 is headed!.
InfraWorks 360 Roadmap Check In - January 2017
It's true that time flies when you're keeping busy! In the 6 months since I first shared the InfraWorks 360 product roadmap (here), two more updates have been released and I've had the opportunity to meet dozens of you. The September update introduced new capabilities for reality capture, road and bridge design, as well as quite a few other enhancements. Not long after that, the team hit the road to attend a variety of industry conferences, including I-HEEP, the AASHTO annual meeting, and the Country Road Administration Board's annual Road Design Conference in Chelan, Washington. Then it was time for Autodesk University. All the while development teams continued to extend and enhance InfraWorks 360, gearing up for the update that released last Friday, January 13th.
In this post I'll go over some of what's in the January update and provide some insight into the current product roadmap. But first a reminder for regular readers and a heads up for new readers about the ground rules:
We're sharing some of the highlights of our product development roadmap to give you a sense of the general direction InfraWorks is heading. There's a lot more work going on behind the scenes and this roadmap doesn't reflect everything the development teams are working on.
Roadmaps are plans, not promises. We're as excited as you to see new functionality make it into the products, but the development, release, and timing of any features or functionality remains at our sole discretion.
These roadmaps should not be used to make purchasing decisions.
Cool? Good. Let's get to the fun part. On the roadmap shown below, planned work is shown in the gray boxes. Things already delivered are shown in bright green. For things delivered in last Friday's update, look for the fire icon - those enhancements are hot off the presses!