Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Add option in Creo Parametric to import DWG files without hidden layers (to have right sizes)Archived

I opened a case in the ptc customer support site (C13519222) because I have some dwg files that if imported in Creo Parametric have wrong size. Investigating ptc told me that wrong size are caused by hidden layers in the original dwg files. Observing Creo View or DWG True View there isn't this behavior and size are correct. Then I asked to ptc if is there an option to avoid import of hidden layers to solve my issue. They answered that it is not possible, solution for them is to clean the original files, but I can't, it isn't for me a solution. I can't ask to my suppliers to clean drawings because Creo Parametric doesn't have the option to see files like Autocad or Creo View.   This is the original conversation: PTC: Behavior is caused because of the items placed outside the format in original file. Dwg file is having many views scattered outside the format in original file. These scattered items are      hidden in layer and exported with that condition. Creo drawing format size automatically get increased to accommodate these hidden items. Opened this file in AutoCAD 2013 & deleted all      items outside the format - Saved the file. Retrieving this will resolve the issue. ME: Is possible to use some option (config.pro or dwg_import...) to avoid hidden layers import? If yes I can set it and I will have the same behavior of Creo View or Dwg True View. PTC: I found this Config.pro in order for the hidden layers not to be exported: Set configuration file option intf_out_blanked_entities to no And also: Refer to Suggested Technique for      Filtering Imported and Exported IGES Data with Layers : http://support.ptc.com/cs/cs_23/howto/idt620/idt620.htm . I will close the case , as the issue has been solved ( via a      workaround ).I wish that the explanations was helpfull. ME: I tried to set in my config.pro: intf_in_blanked_entities no. Then I imported the affected dwg and I see hidden layers yet. What is wrong please? PTC: If Hidden layer items are available in AutoCAD file, they will be imported as hidden in Creo automatically. Can’t avoid them. They will stay as hidden in Creo also, but increase the drawing      format size. There is no currently such option any settings to avoid it. We can use “WBLOCK” command in AutoCAD to select the needed objects & save to new file. Import this new file, so      we will be knowing what we are importing in Creo. ME: Idea Created (but for me it is a bug)      

Better ECAD Collaboration IDX support for components that are assembliesArchived

The current ECAD MCAD Collaboration IDX support works best when the components are a part. However, our libraries are setup where the components are assemblies. This allows multiple benefits: Assembly can include multiple part sources that are allowable in our ERP system and allows the engineer to review each source to ensure it still works with the design As sources for components are disqualified/added, the librarian can do the same within the library assembly without affecting any higher level designs (disqualified parts can be hidden). Datums/Curves/ECAD data is added at the component assembly level and not at the part 'source' level. Some components from manufacturers just import as an assembly and work best that way   That is why we have the components as an assembly. However, when we export idx files with components that are assemblies: We get a warning in the log "Could not find a suitable solid geometry for model <XXXXXXXX.ASM>" IDX and EDA geometry in the ecad tool does not get created, just a bounding box.  Bounding boxes include curves, and not solid geometry (bigger than it should) ecad_comp_xsec_def_name option also doesn't work with assembly components and more...   Please fix so that we can more forward with our ECAD MCAD Collaboration.  PTC can reference support ticket: 14174943 for files and specific details   Thank you!

Explicit specification of the Creo View recipe file used by ProProductviewFormattedMdlnameExport()Archived

We have a need to use ProProductviewFormattedMdlnameExport() to export to Creo View specified child models of the current assembly while using different recipe files.   ProProductviewFormattedMdlnameExport() lets one do an export of any part or assembly that is currently in memory. It allows one to specify the name and the directory of the exported Creo View file. A ProProductviewExportOptions object is also an input argument. It is used to specify the type of output (ed|edz|pvs|vpz). Currently the only way to specify that a recipe file other than the default ed|edz or pvs|pvz recipe file be used is via a config.pro option like "intf_out_pvs_recipe_file". Unfortunately, setting the config.pro option to point to a recipe file and then changing it again to point to a different recipe file does not work. I have implemented a workaround that involves pointing to a temporary recipe file that I overwrite as needed. Before calling ProProductviewFormattedMdlnameExport() I have to overwrite it with my recipe file contents. After the call I have to overwrite it with the contents of the default recipe file. This is so that a user doing a SaveAs in the UI will get the expected recipe file. This workaround will be broken if the user uses one of the mechanisms for overriding the default recipe files.   So, the request is to add an API that modifies the ProProductviewExportOptions object so that it can optionally contain the fully-qualified name of the recipe file to be used by ProProductviewFormattedMdlnameExport().