Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Embedded Creo Mozilla based browser: use standalone Firefox browser (like IE) or provide latest Mozilla updates for secure and fast browsingArchived

Current situationThe Mozilla based browser is installed along with the respective datecodes of Pro/ENGINEER and Creo.It is independent of the Mozilla Firefox installation on the clientThe used Mozilla code is very old, that means:Unsecure for browsing the InternetDoes not contain latest technology including performance improvements. Below you find some test results I got with IE10 and the embedded Mozilla browser with about 14000 objects in the workspace (remark: IE10 is currently unsupported with Creo Elements/Pro 5.0 M200 and Windchill 10.2):Test step short description Time 10.2 F000IE10 / sTime 10.2 F000Mozilla embedded / sDifference 10.2 F000Mozilla embedded /IE10(1) Search for assembly220%(2) Add to Workspace: time until "Download succeeded"5631262124%(3) Workspace Refresh142471%(4) Open dialog: Save As36100%(5) Save As: collect required dependents106not finished after 15minnot finished after 15min(6) Save As: cancel dialog and workspace refresh31-67%(7) Save As: process for one assembly455113%(8) Syncronize and Workspace refresh 354631%(9) Open dialog: Remove from Workspace65not finished after 10minnot finished after 10min(10) Remove from Workspace is processed206not possible as it depends on the previous stepnot possible as it depends on the previous stepFor secure embedded browsing user needs to use the Internet Explorer insteadWhat should be doneSolution (A)Use the Standalone installed Firefox version on the machine for embedded browser. This is regularly updated by Mozilla and updates run by the user and contains all necessary security fixes and other improvementsSolution (B) - if (A) is not be technically feasibleProvide latest Mozilla updates for embedded browser of all Creo Releases and datecodes that are maintained. The updates should be possible to execute separately to a datecode or release update. This ensures that a datecode update is not forced by a security issue in the embedded Mozilla browser.See alsoPTC Document - CS19452 "Mozilla based Browser versions used with Creo Elements/Pro and Creo Parametric":https://www.ptc.com/appserver/cs/view/case_solution.jsp?n=CS19452&lang=enImprovement details: Mozilla and Creo Elements/Pro:http://www.ptc.com/appserver/wcms/relnotes/note.jsp?&icg_dbkey=826&im_dbkey=84076"In some cases, the Mozilla-based browser engine performs better, particularly when running embedded Windchill applications."Discussion: http://communities.ptc.com/message/193032#193032"I'm experiencing some "challenges" with the FIRST Windchill 10.1 server lately.  I'm getting a bit concerned since kickoff is barely more than a month away. Is anybody else experiencing extremely slow refresh rates, slow downloads and incomplete searches?".. "by client side install firefox 17.0 or 17.01 and will run like a flash!".. "Great tip!  There is definitely a performance improvement!"Creo 2Creo Elements/Pro 5.0 M170

Allow "Circular Trim" to be Set as DefaultAcknowledged

Current Version 8.0.8.0The default Fillet option in sketcher is "Circular" which adds construction lines to all fillets.These construction lines are only useful when needing to dimension the theoretical sharp corner, which is rare and usually non-preferred since it is difficult to measure.For most fillets, the "Circular Trim" option is preferred, which creates no extraneous construction entities. The "Circular" construction lines add unneeded complexity to the sketch, and when the sketch changes, they frequently become detached.Since the construction lines are not deleted automatically when the fillets are deleted and sketches get littered with extra construction lines that are not used.They can cause unintended modeling constraints and even incorrect geometry.In complex sketches that have been through multiple iterations and handed off to multiple people, the extraneous construction lines start to stack up and cause the sketch to slow down.This is especially pronounced when inexperienced users are involved in the iteration process. This results in increased design time in having to set the "circular trim" option every time (usually having to delete previous fillets because , even as an experienced user, I forget to set it at first).It also results in increased rework time having to find and delete errant construction lines left over from deleted fillets in models that have been handed off. PTC, please allow "Circular Trim" to be set as the default fillet for the sketcher.

Enable a new part to use an existing *.prt or *.asm for its material & merge its geometry to startAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?8.012. What is the problem?I would like to use an existing part/assembly as the material for a new part file and at the same time have CREO import the files geometry as if using the merge feature and have the first item in the new part's browser be that file. Further detail; to start a new part I would like the ability to select an existing file as the start part/template file. Along with this, if an existing part is selected, as suggested, I would like CREO to recognize this referenced part/assembly as the new part's material with option to utilize the materials library as is. For example if an existing part is allowed as the template/start part it would be beneficial for CREO to automatically default the material parameter to no material needed.3. Are you using a workaround? If yes, please describe it.No, there is no work around. It is possible to use the merge feature to reference the part needed, but CREO/Windchill cannot push the merged part as the material to GEMS. This must be manually added to the EBOM.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation. Well, there are three scenarios where time could be greatly cut down if the function I described above could be implemented.Process drawing sets: Forging, Rough-out, Machining which each successive step using the part prior.Weldment process drawing similar to No. 1. (Prep/Weld/Machining)Modification drawings, where an existing inventory item needs to be modified by some process (machining/welding, etc.).I also believe as should you that this ability would impact your entire install base as the other prominent CAD system have had at least partial ability as I’ve described above. For instance, the derive component feature in Autodesk Inventor works in just this way.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Here at SLB I’m told we have an install base of 1300+ users, which is spread among several subsidiary entities. Hours saved? Annually perhaps in the thousands companywide if the majority of users have just a couple instances like the ones I described above. When you consider how long it would take now to create a merge and then must manually create a reference in GEMs to represent the material for a simple part that’s under a re-work scenario. I also believe as should you that this ability would impact your entire install base as the other prominent CAD system have had at least partial ability as I’ve described above. For instance, the derive component feature in Autodesk Inventor works in just this way.

Mechanisms - 'Enable regeneration value' follows Model hiërarchyAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?9.0.2.02. What is the problem?Regeneration will fail if 'regeneration values' of 'Mechanisms' conflict, even in different levels of the assembly3. Are you using a workaround? If yes, please describe it.Not really a decent workaround.We're using the 'enable regeneration value' option when making the drawing. When the drawing is released, we disable it again.Snapshots isn't a proper solution as they are position and not constraint based. Changing the components doesn't update the snapshots.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.We're using mechanisms to represent cylinders, hinges, linear actuators,... on their correct position. We're also using mechanisms to make simple moving elements movable to quickly check for collisions. Idea:When regenerating, the algorithm should ignore the 'enable regeneration value' of subassemblies if this is necessary to satisfy boundaries of regeneration values in the top assembly Application:- Cylinders, hinges, and subassemblies can get a proper regeneration position to make a nice representation on drawings or when opened individually.- Assemblies can still satisfy their mechanism constrains.- No unclear errors when a component has regeneration value enabled...5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Expose the default text style of a table for editing in the table propertiesAcknowledged

Please include detailed documentation such as screenshots, images or video.1. What version of the software are you running?8.0.5.02. What is the problem?After a table is created, its default text style cannot be changed.  New rows will always go to the default that existed when it was created, no matter what changes have been made since. This problem has been previously reported, upvoted, acknowledged, then archived in Creo Idea 469536 It is passed off as current functionality in CS52055  Make the default text style of tables editable in the table properties.3. Are you using a workaround? If yes, please describe it.Delete the entire table and recreate it from scratch after setting the default values in the drawing settings.4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.Eliminate lots of rework for minor changes5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)I need to do this to 3 tables on each of our 10 formats, with repeat regions and relations.  Even if I did recreate them all, the default justification can't be set to anything but left, so it's pointless since the same action (text style, existing text) is used either way to fix it.  But if you must know, recreating all of these tables would take 5 to 10 hours of work.  Just hope that nothing changes in the standard later, because then they all have to be recreated again!  If it weren't pointless.