It's a minor pain, but having to Import the family, then Import the UI, then Import the Sizes is dumb. Provide users either one import button for both the UI and sizes {system would import them in that order, but one user command} or if the user has an appropriately named JSON file in the same folder as the family being added, to automatically import the JSON to the UI and Sizes. Show More

Ability to lock down components from changes (manual and automatic). the UI can pop up a message to say "the changes can't take effect because the following components are locked". Show More

I have search through many of the Idea postings and found bits and pieces of a request for specific site planning tools, but I wanted to group these all into one BIG idea. It seems to me this is one HUGE vertical market which has been ignored for a while and that is the planning market. Yes, we have roads, bridges, and drainage, but a significant part of site planning includes grading for buildings, parking lots, parks, plazas, and other similar site planning components.  My of my colleagues who work in planning are often quite amazed at what Infraworks can accomplish with the toolset available today but are routinely disappointed that I cannot do a simple right angle or simple geometric primitives such as rectangles, circles, and n-gons, nor can I create a simple parking lot that connects to a component road and has simple curbs. While the manual creation of coverages and land areas can accomplish some basic attributes, I end up reverting back to CAD or other tools to do a simple function such as drawing an elliptical shape for a paver, then much convert that to a SHP file so that I might import it into InfraWorks. Needless to say, the current workflow is a complete turnoff to the average planner or architect.  I see so much potential for InfraWorks in both the planning and architectural vertical markets, yet it still seems to me to be still stuck languishing in the infrastructure side of the toolset. So, to be more constructive with my comments above, I propose the following areas of focus, which could be introduced as a bonus pack fo the AEC collection: 1. Basic CAD Tools for drawing - This would include all the basic drawing tools you would see in Autocad; polylines, rectangles, ellipses, polygons, snapping, splines, etc.  2. Grading Tools - I will defer to my colleagues who know this discipline much better than I, but the existing tools lack some basic grading options than just the nodes on a coverage area and the flatten function.  3. Curbs and lots - Cannot do a parking lot properly and cannot get the "hacked" lot to work and integrate with a component road. If this were done properly, you can derive quantities and areas, and have some tools to fill out parking bays and other markings.  4. Construction planning for lots - This would be GOLD for the construction side of planning, how to get equipment and supplies into and out of a site. Even some basic tools to start would be useful and add further augmentations such as space planning to determine how many loaders you can run at a time and how many trucks can move through, add functions to work with the Mobility module for traffic simulation, determine quantities for excavation, assign color coding for specific contractors, etc. I am sure the construction people could add more ideas here. 5. Interface site planning with Civil 3d and Revit - Use the site planning capabilities to plan out what would ultimately be finished in both packages. InfraWorks can import a Revit model, why can't you send the resulting site planning information back to Revit? 6. Integration with FormIT - You can do basic building massings in InfraWorks. Why couldn't you send those to FormIT, augment the design, then send that back to InfraWorks? Why not the same for Revit?  7. Better site tools would allow for better landscape design - This goes without saying. I would even recommend adding quantities calculations for plant types and planter areas. With this, you could determine water requirements or maintenance requirements. Perhaps this might even tie in with many of the drainage tools.  8. Integration with CFD tools - After some basic site planning is completed, it would be ideal to send this to the cloud for some basic CFD or similar calculations for analysis of the site. With the addition of an API, this would open up numerous possibilities for third-party modules.  9. Access to a store for 3D models - This needs to be an Idea request by itself, but many of the site planners have a range of items they like to use regularly. Autodesk needs to have a range of 3D objects to assist planners in adding specific items or character to their site design. People, cars, lamps, vegetation, etc. I realize this is a big ask, but I envision this as a HUGE benefit to the planning community and would be welcomed happily by the InfraWorks user base in general.   Show More

Just change the names to 'multi-girder member' or 'single-girder member' so that different categories don't have to be made for things like LONGITUDINAL STIFFENERS, or DIAPRAGMS… these can just be part of the generically named components. Creates a more generic naming convention that gives more clarity to users and removes the feeling like you're 'tricking Infraworks' or using it in a way that it's not intended. Show More

An option to place 3D text in a model, so you can show Street names for instance. Show More

The ability to swap out any component and if the parameters are common between them (for example, swapping out one cross-frame family with another), then the new component retains the parameter values of where it is currently instanced (as an option; alternative would be to input with Family size info).  Show More

Hi,   As we often create multiple Proposals to communicate a complex construction or time sequence, it seems logical to add the ability to transition between them during an animation sequence. That way could shown the changes taking place during an animation e.g. using an orbit or camera path animation preset and seeing the site change.   It could for example be added to the existing Transition drop down along with Cut, Face from Black and Fade from white. Alternatively, you could add the option to define the proposal for each storyboard and then transition between them on an additional timeline. Essentially a 'Proposal Storyboard' allowing you to add your storyboards and fade or cut between them.   Cheers, Steve Show More

I would like for Autodesk to take the ideas on there own forums, ideas that they are asking for, seriously. Currently, it seems like Autodesk is ignoring or doesn't care about the ideas on these forums as 16 of the top 20 ideas are still gathering support. Vote this idea up and perhaps Autodesk will hear us. Show More

Create a column that gives users an option to have the stack panel area defaulted as collapsed or expanded on component selection. Show More

hello friends.. why when we create an intersection or roundabout we can't setup splitter island .. as niggle peters say (( The roundabout tool in InfraWorks is based on the roundabouts tools in Civil3D and Vehicle Tracking )) .. if infraworks tools based on civil 3d so we should have this option in infraworks because is that an important part... please do something for this   Show More

Create a 3D sketch in Inventor. Infraworks recognizes it for being a 3d Sketch with a specific prefix in its name and drives it as a parallel path offset by the same amount as the center point is from the original path. Allow users to create repeating patterns within the Inventor models that will be along the Infraworks alignments/corridors/paths. Useful for handrails on a spiral. Show More

Ability to create and populate drop-down menus in the family UI screen... The button is there… but doesn't work Show More

Values can be reset to the defaults for that member… but the slices should remain on the girder and in the same locations. Ideally, if some of the parameter names are the same, it would also retain the original values that each of the slices had for the parameters that match. Show More

Ability to add Cross-Frames with options instead of default values. Current setup forces users to wait for the default cross-frames and quantities to be shown. This can take quite a long time and forces the user to wait while it loads in something that might never be uses. This is especially painful if you're installing something like a diaphragm where it is just located at a pier station with a qty of 1 per girder set. Show More

Update the girder slice command to give the ability to create multiple slices. Users would then be able to either rapidly click where they would like slices (eg. Holding ctlr+click allows for multiple slices to be created) or prompt the user for how many slices they would want and then have them just spaced evenly from the start point to where the user selects (they can move them later). Current setup is cumbersome for creating multiple-slices; users have to create one. Wait. Select the new one. Hit plus. Create new one… repeat. Show More

Hello   Id like the cross section to keep the zoom level when moving the yellow tracker along the road. Default zoom in cross section view is always to small for my narrow roads, i need to zoom in all the time. And If i zoom in the cross section view and then move the yellow tracker along a road the zoom level jumps out.      Show More

With the ability to have Civil 3D use Property Sets on 3D Solids coming from Dynamic Corridors, it would be logical to not only have these Properties available in Navisworks but also viewable in InfraWorks models. Specific 3D Solid objects should then also need to become selectable.   Check this page for more info on Property Sets in Civil 3D Show More

I would like to see a new Array option to create instance copies from one 3D imported object. Then duplicating these objects in a linear, polar or path transform would be real easy. The instances should be parametric, much like the AutoCAD rectangular, polar and path Array function.   Something like this below:   Show More