We've got a lot of 'crossover' Inventor users that need to refer to Revit, Bentley, ArchiCAD files etc on a regular basis for their designs. Yes they can request another generic CAD format like STEP/IGES etc etc, but the ability to receive IFC formats would be a very welcome addition to Autodesk's BIM offering, and would silence the Solidworks squad on another topic (as SWX has been able to do this for - ahem - a while...) Many thanks,  Luke   Show More

Hi all.   I would like to see the option to "Include Decals" in the export to 3D PDF dialog.   At the moment when you export to 3D PDF the decal is lost (this is the same for exporting to Showcase and A360).  This would be a big selling point to all users and marketers who need to send lightweight viewables to their clients with logos, warning labels etc.  This is possible when saving to DWFx but PDF and A360 would be great.   I have attached example files.    Kind Regards. Show More

Inventor should get the possibility to export iParts and iAssemblies in a cpixml-fielformat.   The CPIXML format is a proprietary XML format defined by RIB Software AG as part of the development and market launch of the RIB iTWO® software. "CPI" means "Construction Process Integration".   In construction, this format is used in conjunction with BIM to create a connection between model geometry and calculation software. Show More

When using Inventor for design of steelstructurs, and later use theese in BIM (Tekla), we need the assembly structure to be able to identify the induvidual parts and beams. As the export functions works now, the entire structure is exported into one component. Show More

Hi,   When exporting .RVT files from Inventor, there currently aren't any options to change the .rte template file that Inventor uses for the .RVT export. We have several .rte templates set up with our own project parameters, sheets, starting views, families, project base points, and more. It would be great if we could choose our own .rte template for the export.   The template could either be stored and replaced in the user's C drive for the RVT export to use: C:\Users\Public\Documents\Autodesk\Inventor 2023\Templates\en-US Alternatively, when selecting Export -> RVT in the Inventor menu, you could include a browse button that allows you to choose the .rte template.   Additionally, having the flexibility to specify whether the 0,0,0 (origin) should become the project base point, internal origin, or survey point would be highly beneficial. This could be implemented as an option as part of the RVT export settings.   Thanks, Becki Show More

The IDEA is: be able to retrieve the display name of a material (or an appearance) as defined in a specific xlf file, independently from the active localization. The material internal name (or any other reasonable strategy) can be used as a fallback. Whatever hereinafter stated for a given "Material" can be stated the same for a given "Appearance".   The issue is known to Autodesk development, but only votes on IDEAS can trigger an action from their side. On this aspect IDEAS is "politically incorrect": the few votes that may promote this particular idea will be probably coming from those CAD admins managing hundreds of licenses by international companies with a similar problem (I'm administrating 150, does my vote count for 150? )   [THE ISSUE] The xlf file does an excellent job in generating the localized display name for any existing inventor localization (xlf files are xml files with a different extension that translate the display names of a given adsklib file into the specific locale; they are saved to the same folder than the adsklib file with the suffix -loc.xls). When a certain material is applied from the adsklib library a local copy of that material is saved into the part using the display name valid for the active localization. Unfortunately if users with different localizations are working together, a situation as the one in the following image can occur:       In this scenario positions from 1 to 9 are the same material, but have been inserted with EN (1 to 3), DE (4 to 6) and FR (7 to 9) localizations of inventor. Positions from 10 to 15 are "Brass" in EN, DE, IT, FR, ES, RU localizations.   While via API* incoherent localizations can be corrected, it would be preferable to be able to select WHICH localized display name should be retrieved. Considering that any other multilanguage need can be reasonably managed with some systematic use of iProperties (as demonstrated by attached PDF), being able to retrieve a certain localized material name would bring the workflow from 95% to 100%.   [BACKGROUND] As a German based company with subsidiaries in USA, China and Poland, the only practicable solution that we could find at the current status is to switch the material library to "English only". This not only disturbs the vast majority of German sub suppliers (they cannot handle English ), but also forces our Chinese employees to translate material names so that their sub suppliers can handle them (they also cannot handle English  ). Thus even the universally accepted English is in this case a compromise. Having the xlf workflow implemented to the end would solve the issue.   [CONCLUSION] Please, vote up: the issue can be realistically solved, but only IDEAS votes can convince Adsk management to assign the task to developers. Thank you       *the API for anybody who might need it: Private Sub refreshMaterial(pDoc As PartDocument) 'pass byRef a kPartDocumentObject to the sub If pDoc.ActiveMaterial.DisplayName <> pDoc.PropertySets(3).Item("Material").Value Then ' Debug.Print pDoc.DisplayName & " - " & pDoc.ActiveMaterial.DisplayName & " - " & pDoc.PropertySets(3).Item("Material").Value pDoc.PropertySets(3).Item("Material").Value = pDoc.ActiveMaterial.DisplayName End If End Sub   Show More

With all of the options there are for importing igs, step and parasolid parts into Inventor, there are no options to select which template should be used once this part is imported.  Quite often a user will have different templates depending on the operation or units being used.  There should be an addition under the open dialog to allow a user to select which template they would like to use.  Whether it is a custom one or the default out of the box.  Just give us the freedom to select.   Original Author: Cadmanto   8/2/2013 Show More

Hello, When you export an assembly file that contains subassemblies to an IFC file, the result is a single IFC! I want a multi-assembly IFC file in the result. For example, I have several windows in a house. I export all the windows at the same time because I have a lot of them. And the result is an IFC group of multiple windows! It's not good. I want several windows with multiple properties. How to do ? Show More

Please support IFC version 4 at least for BIM exports. Show More

Idea: Upgrade Inventor's IFC export function to official version supported by ISO 16739-1:2018 - IFC4 ADD2 TC1. Include an import function with AnyCAD to deal with this file format. Show More

Dear all,   First, thanks for the implementation of PMI to the export of JT-Files. As described in the previous idea ”Export JT with annotation” we mostly use assemblies for the JT export and the implementation with the Update 2020.2 only supports the inventor-Part mode. So, my idea is to support PMI export to JT-Files in assemblies, too. Then it will be possible to document complex situations in an assembly via 3D and we can reduce fails, because for a lot of workers on the shop floor it is strange to read complex situations in 2D.   Kind regards Carsten Show More

We are working w/ 2 different companies to do web based parts pages for our customers, and both require an SVG format.  To this point we're struggling to get an IDW to SVG workflow.  Only success we've found is via DWG which would be OK, but even that work flow requires several steps and 3rd party apps.   Thank you! Show More

Hi!   Nowadays, when importing a Step file, based in an assembly created in other cad package, we have only the chance to import it like a multisolid part.   Most users receive Step Files and the current workflow to open Step files in inventor is very weak.   To really improve interopabilyty it’s better to add several options as:   Import Step Files workflow. 1-Bring it back the availability to import step files as an assembly 2-Rename the solid bodies based in the browser multibodies features (which are the actually the parts when importing a step)   For any workflow 3-In the workspace project folder: have the availability to manually change file’s File Names without loosing assembly links (and drawings, etc) 4-Tool to change File Names based in the Part number, without loosing assembly links (and drawings, etc)   Make a pause in ANYCAD development and really improve interoperability for most users. Of course you can turn a multisolid part into an assembly easily, using tool Make Components, but the issue is:   the multibody part will maintain the name of the original assembly parts in the browser tree… but in the Solid Bodie’s folder, inventor will name the solid bodies as Solid1, Solid2…etc, therefore, when you use Make Componentsto turn a multisolid in an assembly, you will loose the original names of the parts with this workflow, you will have a nice assembly with parts called Solid1, Solid2, etc.   This is a awful interoperability issue. Imagine to rename undreds of parts, rename parts, and resolve links due that…. Multiply that for undreds of parts… Why the need of so much work when this info come with step file.   I strongly believe that, for most users, those options have at least the same importance as the AnyCad workflow, In my case have a lot more, since I received Step Files daily and I don’t want to loose track of the original parts name Show More

In Inventor export dialogue is missing the option to include all work features to exported files. It is interesting that when I import any exchange files, the import option for work features in the dialogue appears. I   It seems that the translator is only able to read (import) the work features but it is not able to export them. Please improve the translator! Include the same export option as it is in import dialogue. This way the planes, axis and points can be transferred to other software. It is important for fixture and measure jigs manufacturers who need to use the work features as limits, measure points, for constraints etc. We would like to provide them with a set of work features in exported format to avoid design mistakes. Now we have to open our IPT models (which include work features) with Creo, save them as (STP, IGES, SAT, STL and others) files including work features and send them to our collaborator, supplier, vendor etc. for next work. It is obvious that exchange files can comprise work features and some translators can export (not only import) them. Why Autodesk does not implement it?   Archived old idea (without solution) is here: https://forums.autodesk.com/t5/inventor-ideas/export-work-features-as-step-files-planes-and-axis/idi-p/6269890   It was also discussed at Inventor Forum (without solution) here: https://forums.autodesk.com/t5/inventor-forum/exporting-work-planes-points-and-axis/m-p/2079175#M273219   Why Autodesk lets his competitors beat him in this field? And push his customers to use competitive software? Show More

Make it possible to export annotations in UI and API, see: https://forums.autodesk.com/t5/inventor-customization/export-jt-with-annotation/td-p/7802476   Cheers René     Show More