Recently active
The following situation is given:top-assy | --- part2 | -- assy1 | --- part1part1 and assy1 one have a position number in the bom list.If user wants to create a bom flag by picking a geometry of part1 a confirmation dialog should bedisplayed by the system and user has to confirm to create a bom flag for part1 or assy1.Today always the bom flag for part1 will be created.Workaround in 18.1 M050: switch dialog option to create a bom flag by table entry and not by geometry.A confirmation dialog explained above would be better !
We want to try to use manikin model for evaluating of fitting the wearable computers to head and the game terminals to hands.But we can’t evaluate them smoothly because the current manikin model can’t be separated to head and hands. Please deliver a part such like a head and hands of manikin model.
I have a program in VB running in batch mode and I need to present the structure in OCX as lab view OCX and I can pass the structure directully to that OCX to be presented it will open a good field for development.
I would like to request the development of the ability to drive Windchill find numbers or line numbers from SolidWorks BOMs.The capability is announced for Creo and Autocad on M10.2 M010 but I would like the capability to also be available to other authoring applications.Creo and ACAD are good, but I also have the need for Solidworks driven Boms.thank you.
Abobe Message is not easy to understand.Please change the message for easier to understand.For Example,"Security Failure" to "Cannot get the license""press the 'Continue' button to save your session before you exit." to "After close this window to press the 'Continue' button to save your session before you exit,save the data to 'file' - 'save'.""you must wait until they are returned by some other user:" to "you must wait until they are released by some other user:"
I just read this documenthttps://support.ptc.com/appserver/cs/view/case_solution.jsp?n=CS151960&lang=enit recommends to create a feature parameter ECAD_HOLE_TYPE type string with the value MTG for the holes that shall be exportet as MNT instead of PIN.Wouldn't it be great if a table for standard holes could be used for that?e.g. using a ECAD.hol to make this features would automaically add the feature parameter ECAD_HOLE_TYPE = MNT?
In WGM for Drafting, managing drawings which are created by using Annotation feature needs to be supported.
When creating a BOM report in standard mode (Tools > Bills of Materials), the report can only be saved to an HTML file. I would like the options to export a BOM generated in Assembly mode to tab-delimited and comma separated text files.
I would like to add tangency conditions to a curve through points in IDD.
We 'd like enhance the Drafting-Tab with a new group "HALLO" in "Drafting".But the new group in the register drafting we can't export with EXPORT_TAB.It's only possible with "New Tabs". Please enhance this.Thanks.Urs Ammann
HELLO EVERY ONE , In Assembly level we are changing the names from A1 to A2, in the same way here we requires the renaming of instances names of parts automatically(Sheet Metal),Here we are getting below problems:1 For example in assembly we have 100 parts so, we are changing the names at every individual part. It is taking so much of time and It impacting cost.2 If the part instance renaming is not done then the Drawing will not open.For that there should be a column of instance name with renaming possibility.
Just like Creo 2.0 great enhancement that we can change units to all part files once in assembly mode.Please add ability to change model accuracy to all part files once in assembly mode too.For current Creo 3.0, we have to open all the part files one by one and change model accuracy, which always make me mad when the large assembly includes a lots of part files.
In SheetMetal we customized other tables. For example (eval '(sha-define-shop-table "air bending BYSTRONIC" .The table is very large and so we 'd like to define the tablewidth and the tableheight in our lisp-file.Also the necessary width of the "ColumnWidth". We need the Column as small as possible.Please extend this in your program.Many thanks, Urs Ammann
To whom it may concern:The whole purpose of a Reference Pattern is to quickly and easily use the source pattern to create a new pattern. However, this is not the behavior when the source is a Geometry Pattern.A Geometry pattern uses surfaces of a geometry to then copy/move/solidify as the pattern. The problem is that the pattern does not have embedded the source feature, like a typical pattern. Geometry Pattern is a great feature on its own, but causes issues with reference patterning. Example: Lets say I create a boss with grooves, ribs, drafts, rounds, chamfers... etc. Patterning everything regulary causes issues, so I use the Geometry Pattern and it works great. All in all, I want 30 members. The Geometry Pattern creates 29 members (as it does not include the first one).If I want to add hardware for those bosses and try to assembly the screw to the original boss, the reference pattern is not available. If I reference one of the other 29 bosses, the option is available -
If I am adding weights or other adjustments to a top assembly I want to be able to make the springs in a subassembly flexible at the top assembly level.
Darts and rounds are very limited in sheetmetal. This relief is -very- common in the manufacturing process.This needs to be support in the core sheetmetal product feature set.
Pre - Creo functionality of Layers allowed for users to add GD&T / Annotations to a layer(s) then control the visibility. Now per, CS95436, you must use the Show/Erase function for annotations. The statement of "Works to product specification for Creo Parametric" is provided as a reason. Not only is easier to toggle a layer but also easier to write into ModelCHECK standards.
We want to export the texture on a model to print this directly in color.When one creates a wall with brick texture, it is possible to print this in color directly.Some 3d printers have this functionality today, but it is hard and repetitive to add texture.Also for programs like Keyshot this could be helpful.
Currently detail views can't be rotated. A general view must be created to do this. When detail views contain things like text it's necessary to rotate them in order to allow the information on the drawing to be delivered in a effective manner.
Wenn man einen Schriftzug in ein Teil fräsen möchte benötigt man Linienzüge - keine Sammlung von geraden Linien.Unser BIO-Schriftzug aus dem Zeichnungskopf ist sehr gut mit einem Fingerfräser herstellbar, aber als normale Schrift nicht.Gibt es Vektorschriften die man nutzen kann?
Please make "fix index" work reliably. This would include retaining a BOM bln (at least most of the time) when using the replace command in the assembly, as well as working with flexible components. Fixing the index is a great idea to quicker match blns to their line in an automated BOM, and vice versa. I like the idea, but it has been implemented in a VERY error prone way. More Details below-----------------------------------PTC said this is intended functionality because they don't know how to handle situations where there is a quantity >1 for the item being replaced but a simple way to handle this might be to have it do a clean replace when qty is 1 and then if qty >1, then the replacing component will get a new number appended to the bottom of the table, and the remaining component(s) will retain the original number.
In terms of 3D Drawings, most funcitonal elements (Combined states, layers, cross-sections, exploded-states, styles) have the capability to add/remove/edit that element through the API in Pro/TOOLKIT. However, this does NOT exist for is for Views (orientations). There exists a function to "ProViewStore" (aka, create a view), however there is no capability to then delete a view. This means that any desired model cleanup must be done manually. A function exists for 2D drawings (ProDrawingViewDelete), however this requires an input of "ProDrawing" and will not work for 3D assemblies. Please create a function to delete a view (i.e, "ProViewDelete"), as well as to rename a view (i.e, "ProViewRename" or "ProViewNameSet"), to complete the functionality of the API, as it has been done for all the other functional elements of 3D drawings.
Virtually any feature that requires the use of a shift key is a waste of time, effort and slows you down. Drag handles on dimensions in the drafting environment...Now I have to use the shift key? Ridiculous. You've taken a step backwards.Accessing the properties only by double-selecting the extension lines makes it more difficult.Measuring features is now a pain in the rear.Thank you so much to the programmers who obviously have never actually spent any time designing parts in real life. Kudos!
Autosave always seems to hit at inopportune moments, and I often have very large workspaces. Can there be a wholesale memory dump that is parsed out by a background process?Is there a way to split functions that may have an overall longer processing time, but returns control to Modeling quicker?I notice zip.exe in the Windows Task Manager, would it run faster if it weren't being zipped?Is there a way to have a more continuous autosave, so each time a part is modified that part is saved?Maybe a more piecewise autosave, such that only parts that have changed since last autosave are saved?
The custom feature report lists all of the features and if they are valid or not. However; it does not list which part the features belong to when an entire assembly is checked. This makes it almost impossible to fix issues since many of the assemblies I have have hundreds of parts.If the report listed the part the feature belonged to, this would simplify fixing the issues.As can be seen below, the part the issues is associated with is not shown. This assembly has close to 300 parts.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.