Recently active
With the spin center off, Creo willspin around the model where the middle mouse button (MMB) is clicked. It usually works well, especially when zoomed in.When a part or assembly is sectioned, however, it spins around some gemoetry in the removed part of the model. This makes the model spin off screen very easily adn isvery difficult to control.The selceted spin center should only be on visible geometry.
Not sure if this is the place for ideas on improving the forum, but I'm going to go ahead anyway. The spell checker here is pathetic, can we turn it off and allow the browser spell check to work instead?
When a Datum Feature, let's say a datum plane, fails due to a missing reference, I am presented with the definition dialogue box, in which the failed/missing references are highlighted with a little red dot.What Should Happen:I click on a reference of the same type as the failed/missing reference and click OK. The object regenerates without a problem.What Actually Happens:I click on a reference of the same type as the failed/missing reference and the remaining good reference(s) are removed from the dialogue box. I curse, click Cancel and try to remember/write down the good references in case it happens again. I try again, Right-Click, Remove the failed/missing reference, press and hold CTRL, click on a reference of the same type as the failed/missing reference and click OK. The object regenerates without a problem.The software knows what is wrong, it knows what reference it requires, it knows which reference has failed. Why, then, does it not accept the first appropriate click I make a
Please allow the possibility of relating a free floating annotation to be related to another annotation/weldnote.Such as the words "EACH TUBE" to be related to the weld note so that when you move the note around the text will follow it.Thanks, Dale
Many times we need to make a pattern of holes for a rectangular flange. Typically when the pattern is small users will manually deselect the internal instances of the pattern to produce the required result. PTC tech support suggest the best option is to configure a pattern table as per https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS75132We think it would be nicer to just have an option under pattern to [more quckly] exclude the innermost pattern instances so the result is a 'rectangular hole pattern'.I respect the fact that a curve driven pattern with a carefully constructed curve and a constant hole distance is a solution in some cases but it doesn't cope with patterns that have a different spacing in X to Y.
There are several pick filter options in the lower right user interface. These selections should also include "solid" as there are times such as mirroring when the whole solid does need selected.The only other way I can see this accomplished is by selecting the part off the top of the feature tree. Unfortunately this includes everything when only the solid is needed.
Whenever I create a note on a drawing, if it has no leader I almost invariably want to 'Group, Relate to Object (or View)', so that it moves with whatever it refers to. For example, if I create a note saying 'TYP 2 PLACES', I may relate the note to the BOM balloon that occurs in two places.My idea is that, whenever a note without leader is created and 'DONE' is clicked, Pro/E (Creo) should immediately prompt the user to select the item or view to which the note should be related. Middle button means none - the note is unrelated.This could not only save a lot of unrewarding mouse-wafting, but, more importantly, would prevent the frequent problem of notes staying put when a view or a dimension is moved.Please vote up if you think this would help you.
If section view , projection view or detail view has been moved to another sheet it should automatically reference the sheet name of the parent viewWhen views are moved to different sheets, it is sometimes difficult to find which sheet the parent view resides on. When drawings are plotted then this becomes even more difficult unless the views themselves are annotated specifying on which sheet the parent view resides.So the idea here is that when a view that child of another view is moved to another sheet, the note for that view is automatically updated with a parametric note that specifies the sheet of the parent view. If the sheet of the parent view changes then the note should update accordingly.
Importing an ECAD board creates hundreds of unneccessary layers. We would like to be able to turn that aspect off ASAP. Importing 3D data from our IDEAS legacy system results in layers with names like colors etc. We don't want those layers brought in either. Making a Cross Section and a datum on the fly results in a XSEC_DATUMS layer being added, we don't want that either. Making a drawing using a template of a part that has annotations on it seems to produce a drawing level layer called ANNOTATIONS also, we don't want that either.
Our business is a collection of bought companies and people. What we find is that there are multiple 'standards' at work when it comes to layers. Even if we could persuade everyone to join up to a single paradigm it wouldn't be painless because the dozens of years of legacy data (and data from contractors and on and on) will be using a different set of standards. These non-standards make viewing the assembly layer tree completely painfull. Would prefer to have all the non-standard stuff dumped into a default system node so that our normal layers don't end up drowned by the almost limitless other layers that exist in our legacy datasets.
Speed up HLR of large assembly drawings by leveraging the multiple cores that are present in almost all engineering hardware these days.
Most of our userbase can get their head around Replace in Sketch but we fail to get the majority to understand how to reroute (edit definition). I think it would make more sense in their heads if they could just RMB/Replace the missing reference (say a surface in a draft feature) from teh dashboard where it's showing red already. Here's what Hole dashboard looks like for example.
We have on occasion a requirement to design a component in a bent state but then unbend it. Naturally we cannot use sheetmetal to create it and have to rely on manual techniques to build back the 'unbent form'. Here is a simple sketch of a situation our engineers find themselves in relatively frequently even though our guidance on this matter currently would be to design the flat and apply a toroidal bend. I guess an inverse toroidal bend function would be the request for this case.
International drawing standards highlight that the hidden portion of a Datum Target Symbol referencing an entity on the rear side of a view should have the affected portion of it drawn in a hidden font to reflect that fact.
Would like to have a built in tool to provide a more automated way of finding outlines of scanned in pencil sketches, i can't imagine this would be tough for the excellent programmers at PTC as even web pages can do this to some degree these days, e.g. http://arohatgi.info/WebPlotDigitizer/app/). Perhaps a pre-processing step would occur whereby the tool would suggest 'options' based on what it can see and how complex you want the result to be (e.g. did you intend to draw splines or lines etc). The user would pick a result and then manually finish off the sketch afterwards.
It would be beneficial to us if we could take in a PDF file as a Legacy file and have the import result in 'converted to editable' lines and text format. Ideally in the same way as www.scan2cad.com/ suggests is quite easily possible. An intelligent approach to re-interpreting a PDF may prove to be an easier proposition than trying to deal with all the variables involved in the export/import process of 2D from legacy 2D/3D CAD systems.
In order to make it practical to use the extension to exactly replicate an exploded assembly drawing view, LMX needs some functions to setup an appropriate explode state in the assembly.It should be possible to convert a table into a Creo table.
Please enhance Creo Parametric's ability to to pick objects when using Import Data Doctor. I often need to change the line style of imported curves, or the color of imported surfaces. As it is now, I cannot "fence" (click and drag) to highlight entities.
Please enhance the delete functionality in Creo Parametric's Import Data Doctor to allow "fencing" (click and drag) of mulitple objects when deleting items such as surfaces, datum curves, etc.
Please enhance Creo Parametic's sketcher to include commonly used shapes, specifically an obround. I realize that I can get any shape via the sketch pallete, however, that functionality is difficult to use, at best.
Simulateにおいて、ティモシェンコ梁の新計算方式と旧計算方式を切替て利用できる機能がほしい。(コンフィグでのON/OFFでも可)提案理由 解析を行うのはエンドユーザであり新旧どちらの計算方式で、より実機に近くなるのかは検証を踏まえて判断する必要があります。 つまり、新旧計算方式どちらを採用するかをエンドユーザで選択できなければならないため。(実測上、旧計算方式の方が実測に近い場合があるので新旧両方を使い分けたい) 影響度 WF4.0での解析結果とCreo2.0の解析結果が大きくことなる場合があり信頼性がかかわる。
I need the Japanese version of "VB API User's Guide", in order to understand the function of VB API correctly.
We strongly want to propose to improve the specification about rwd file.By the current specification, the path to study directory is written as relative path name from the working directory when user saves the rwd file, and the study directory will be fixed as relative path from working directory when the rwd file is opened.Because of this specification, the path of study directory will be lost when user changes the working directory. Then the error of "The study directory was not found" is occurred, or the wrong rwd file in other directory which user does not expect is shown when opening the rwd file.Incidentally, we understand there is no problem if the configuration option "sim_pp_path_absolute" as "yes" instead of "no".However in that case, it is impossible to open rwd file if the folder which includes model and analysis result moves to another location.We hope to change the current specification like following.As the new specification, the path to study directory is written as rel
When you import a model using the Solidworks interface it doesnt copy threads over, just draws the diameter. It would be good if threads were recognised.
Within a part with repeated geometry it is possible to define one instance as a formelement and then to propagate this formelement.However, when the part is stored it occupies more disk space than the part with repeated geometry.An alternative is to define the geometry that is to be propagated as a separate part and then to propagate this part.This technique for reducing the disk space required for repeated parts should also apply to formelements within a part.
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.