Hi Colin,
Which release of Wildfire are you using?
Amit
↧
Re: clipping diameter dimensions
↧
Re: could any body give a review of creo parametric 3.0?
First of all, are you saying that Drafting is totaled partially because you can no longer type in code, instead of just clicking on what you want, and bolding, italicizing and underline with industry standard shortcuts (ctrl+B, etc)? Or is there something else? I personally like this method because for people who don't use it every day syntax can be hard to remember and then they come ask me, taking both of our times!
Secondly, what build of Creo 3 are you using? PTC quickly (and admirably) added back in the ability to use the old (OLD) text box so as not to disrupt some users workflow because of some real advantages of a separate editor box opening. I think the buttons, inline typing, and keyboard shortcuts for formatting are really great. Now I too would be frustrated if they don't work all the time, but I just tested some of the old format coding methods (such as @[-A-@] ) still work within that old box but not inline. I really like how PTC made it an option (eventually).
I agree that I think it was a terrible idea to require the user to dimension using the 2 buttons instead of one. It is just annoying to me, but I know users that hate using their left hand (and they really should NOT have to for something like this!). I don't understand why they went through with doing this considering how many people hated them doing that in the model to the measuring tool! Thankfully for us, most people at our company just display model dimensions and it is heavily discouraged using the dimension creation tool (except for when it occasionally is needed)...though there are situations were we are analyzing a model in a drawing and we need to create lots of temporary dimensions.
I am not sure about modeling yet, as I am still testing it. but, Davor Granic, I am glad to hear you didn't have any problems with ribbon and config! I likewise have not found issues there yet.
↧
↧
Re: could any body give a review of creo parametric 3.0?
I have not seen the new interface yet because I have no reason to go through the install.
I do have to make this decision on a new computer that's already gathering dust for this very reason.
It seems like every upgrade is a few steps forward and some painful steps back.
I still use Creo 2 M040 because I know all it's quirks, I reported most of them, and in the last 2 years I have received a lot of "we won't be fixing that ever" solutions to the support cases filed. And as Creo 2 was coming up, it became more buggy, not less.
So the answer for me was to stick with what I know. Creo 2 is more functional in day to day world than Creo 3 or 4. When 1/2 of your world is drafting, it is important that people are not forced to change their way of being efficient. If it wasn't for this huge error on PTC's part, I might already be running a late version Creo 3 now looking forward to a stable C4.
BTW, the other parts that they completely messed up, even back in C2, was the sizing of annotation elements. Do this a few times with a single annotation element and then go look at the proper editor. You will see the entire string delimited out the wazoo. That is not allowed in my datasets. Sorry but poor execution behind the scenes is what appeared to be covered up by PTC by removing the editor in Creo 3. They knew they had a problem in Creo 2 that was patched (one of my support claims). It is unprecedented that the users could actually force the editor feature back into the product. This is a new one from PTC in years of involvement.
There are a few nice updates and features, but nothing that makes my day to day life any better... just worse.
↧
Re: could any body give a review of creo parametric 3.0?
Antonius Dirriwachter Sadly enough, I completely agree with your statement:
...
It seems like every upgrade is a few steps forward and some painful steps back.
...
When we went from Wildfire 4 to Creo2 I was very frustrated at some of the functionality they removed ( List (and discussion) of features removed when going from ProE (WF1-WF4) to Creo(2) ), and especially how they destroyed the Show/Erase dialog and replaced it with the Show Annotations which no longer shows ALL annotations!
In order for any company to continuously improve, they will disrupt someone's workarounds. I hope we can agree on that, even though we may feel very strongly that PTC has removed good functionality that was not based on broken workarounds (like the show/erase dialog which worked so well!). The biggest problem is that if a company takes a long time to fix an issue, people have already created their own workarounds and gotten used to them and then don't want to change...even when it is (in itself) a positive change. Again a double hats off to PTC for giving back the textbox dialog even though the new input method finally matches every other program in the world and can edit inline (without people asking me how to put a box override in or one of the other codes they forgot how to do).
A coworker sent me this cartoon a while back which I think summarizes software improvements and workflow issues, from the programmers perspective. I hope you enjoy!
↧
Re: could any body give a review of creo parametric 3.0?
I do honestly believe they fixed the Creo 2 problem in Creo 3 by just covering it up.
And the proof is still there as the problem is still there as far as I know.
At the very least, people don't know their text is turning into scrambled eggs as they try to size their text string with the mouse,
...or someone has verified that this is still occurring in the latest release.
My only "workaround" as you call it is to not use the "feature" that doesn't function well, the auto-whateveryoucallstretchingandsquishingtext
is to not use it.
That means a flaky feature with the potential of gumming your annotation strings behind the scenes is an acceptable workaround FOR PTC! ... Not me!
And it is my choice to NEVER use it in Creo 2 or 3 and likely 4 if PTC doesn't solve this.
And no, most people working on "every other tool" doesn't need symbols and special characters at every other text element.
They also do not have different buttons to push in order to complete a basic string.
When I make drawings, inline control is not only needed, it is a critical tool for managing workflow, not just a workaround.
How do you go about finding the appropriate text symbol as you type using scientific notation?
You buy an interface that presents them in a simpler format than what Word allows.
The way Creo 3 worked out of the box, I might as well have to open the character map every time I needed a special symbol.
...when before the symbol was presented when I opened the dialog.
↧
↧
Re: Drawing Export Settings to PDF - Where's All the Color?
This was without using a pen table. ("Use pentable" was unchecked on PDF output options.)
↧
Re: Using the VB API to create a drawing with a custom template, getting error pfcExceptions::XToolkitNotFound'
Got this solution from PTC Support:
The reported error XToolkitNotFound will be received if the specified Template Drawing (not format) “D-CUSTOM.drw” does not exist in any of the below mentioned locations
- 1. In the current working directory (OR)
- 2. Creo 3.0\MXXX\Common Files\templates\ (OR)
- 3. In any directory which is loaded in creo as a search_path (or through Search.pro file)
So, Could you please make sure that the template drawing file “D-CUSTOM” is located in any one of the above mentioned locations ? Also, if the template drawing is located in the Common Files\templates\ folder, make sure that file does not have any version extensions .drw.#. Please rename the file and remove the .# extension. Please try this and let me know it works. If this did not solve the issue, please send me your code snippet, template drawing and an example solid model.
↧
Re: How do you modify/remove the lines on the cut edges of Section Zone?
Not sure why it shows that way but if you are just looking to shorten the view, I would use a partial view instead of a section zone.
↧
Re: How to reduce &fam.inst.param.name in 2D region?
Thank you Matthew,
I tried this, but do not go.
I create the relation LENGTH=fam_inst_param_name, but I am not sure what does mean "do such processing as is desired(here, searching for : and getting the substring up to but not including the colon)
And how to call out the LENGTH?
I tried, but all values was hiden.
Thank you very much
Roman
↧
↧
Re: How to reduce &fam.inst.param.name in 2D region?
Hi Martin,
thank you for your help.
I have to say... I know this way. But here i have another problém:
When i done this and verified instances=> the part has the GREEN sign. If I open the part second one (some instance) it isn't in GREEN but has a YELLOW sign.
And the same thing is by using the part in assembly.
and the second thing: there is the critical warning:
Relation LENGTH=LENGTH:FID_1354 override family table values of instance D\:práce\konzola1<konzola>
Thank you for your reaction.
Best regards
Roman
PS: Sorry for my english
↧
Re: How to reduce &fam.inst.param.name in 2D region?
Hi,
can you upload your model ?
See How to Attach a File to a Discussion Reply document describing upload procedure.
MH
↧
Re: clipping diameter dimensions
Hi Colin,
To create a clipped dimension do the following:
- Select a reference
- Hold down the CTRL button and select a 2nd reference
- Continuing to hold down the CTRL button, select the 1st reference again
- Use the MMB to place the dimension
Let me know if that doesn't work.
Thanks,
Amit
↧
Re: clipping diameter dimensions
Amit's method is for a created dimension. For a shown dimension, use show as linear, and clip witness line (from the dimension properties dialog), IIRC.
↧
↧
Re: could any body give a review of creo parametric 3.0?
Can you send an example of what you mean when you get jumbled text behind the scenes? Also, what build of Creo3 did you use when you tried?
As mentioned previously we are not yet using Creo3 in production and have only done light testing so far, but I have not yet seen this issue yet so would really like to know when Creo scrambles the text/code behind the scenes. Since Pictures are worth a thousand words, I threw a string together using the special characters/symbols below all inserted with the mouse to put them in so that it looks like this (ignore red box as that is the table cell boundary):
but when I go into the properties it correctly shows the old coding style:
And what symbols are you looking for that are in the old dialog box? These are the ones that I see and they are the normal ones that I have used in the text editor:
The above string uses the same style superscript as in scientific notation. Now I wish PTC would have added the keyboard shortcut used in word to make superscript and subscript (Ctrl+= and CTRL++, but that would make a good improvement on the other keyboard shortcuts they gave).
↧
Re: could any body give a review of creo parametric 3.0?
Right, it does fine if you never auto-length the text string with the mouse.
Problem is, a lot of times when you grab the annotation, it sizes instead of moves.
You just created your first extra delimiter in the field without even knowing it.
This is true in Creo 2 and 3.
It is the note properties where everything gets tangled. It presents fine.
If you play with a complete note set long enough, you will get character style formats delimiters just about every other character.
That is WAY TO MUCH OVERHEAD for Creo drawings. You can no longer select continuous text strings from the face of the drawing.
you will start getting unexpected results from editing your text style.
In all, it was a real boneheaded function that was added and it has been a problem ever since.
And this is not original Pro|Engineer functionality. This is PTC trying to add something to the core drafting set way after the original code.
That is why sometimes it is better to leave things alone rather than trying to keep up with the Jones'.
As stated earlier, I have no use for updating Creo 3.
I think I am at M010. Certainly not F000.
↧
Re: Creo becomes pixelated when working with large components
If you can afford it, I would recommend upgrading the video card to the NVidia Quadro 4000 or 5000 series with 4GB or 8GB RAM. Also, I would recommend using HP Performance Advisor for Creo which will check the drivers (vs the certified version) and will also propose some tuned values for Creo. I will also handle CPU Affinity and other interesting performance settings.
↧
Creating vertical notes in Creo Parametric 3.0 and 4.0 takes so much longer compared to Creo 2.0.
In Creo 3.0 when making multiple vertical notes you have to select :-
Note > Unattached Note > Select LOCATION for note > Type the note > MMB to finish typing > RMB > Properties > Text Style > Angle > Type 90 > OK > LMB click in empty area of screen.
For subsequent vertical notes you have to do all the above again.
In Creo 2.0 you select:-
Note > No Leader > Vertical > Make Note > Select LOCATION for note > Type the note > Enter > Enter
For subsequent vertical notes you just have to select Make Note, as the last settings are kept.
At no point on creating a note in Creo 3.0 are you able to specify 'vertical'.
↧
↧
Re: Creating vertical notes in Creo Parametric 3.0 and 4.0 takes so much longer compared to Creo 2.0.
You can grab the handle now and rotate. It doesn't really snap to 90 but it's not too hard to get it vertical.
Not a perfect solution but maybe better than the large number of clicks.
↧
Re: Creating vertical notes in Creo Parametric 3.0 and 4.0 takes so much longer compared to Creo 2.0.
I've always thought that rotate tool fairly useless exactly for that reason, it doesn't snap to vertical or horizontal.
↧
Re: Creating vertical notes in Creo Parametric 3.0 and 4.0 takes so much longer compared to Creo 2.0.
I agree. Other than a mapkey, or setting one note up and then copy and pasting and editing the subsequent notes, I don't think there is a good solution.
↧