Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Creo View - Increase or Remove 4GB Memory LimitDelivered

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.Machine Automation. Creo and Windchill admin. Creo View Users. 2. What product and version are you currently running?Creo View 8.0.0.03. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.User's occasionally run across this error message when working on larger Creo View assemblies or having too many models open. This message is frustrating because it force closes Creo View and prematurely ends whatever work the user may have been working on. https://www.ptc.com/en/support/article/CS47101     We can train users to get around this arbitrary 4GB limit by telling them close unused models, open subassemblies instead of top level models, use Render Mode = Shaded instead of Shaded with Edges, etc. This 4GB limit has been around since Creo View 2 (March 2012 - roughly 11 years).   Upon investigating the Creo View MCAD Massive Assembly Option, I was floored by the awful pricing. It requires Creo View MCAD ~$3.1K floating list lease price plus either ~$5.5K registered user or ~$15.5K concurrent user for the Massive Assembly Option. This is significantly more than the cost of using Creo Parametric - all to increase RAM beyond 4GB. Pretty much impossible to justify buying.   Ideas: Increase the 4GB limit to 8GB for Creo View Lite/MCAD or get rid of this arbitrary limit. Creo View MCAD should include the 16GB Massive Assembly Option. Give the user a better experience if the arbitrary limit stays around. Force closing on users is a terrible user experience. Give an option to undo last action that caused them to exceed the limit. Provide a better error message that includes the GB limit and common ways to reduces memory usage, etc. 4. What is the use case for your organization?Easier to work with larger assemblies and take advantage of more powerful new computer hardware.5. What business value would your suggestion represent for your organization?Better user experience, better value for Creo View users, and less confusing licensing.

Modelcheck - detects limitation cases for positioning assemblies publicationAcknowledged

Windchill customers use more and more an advanced publication technique for their CAD assemblies, especially when the assemblies become large. It’s positioning assemblies. Basically, the worker opens an empty representation of the assembly, list the first level objects, get their position and stores them – it’s super fast.    But this mode has some limitations : https://www.ptc.com/en/support/article/CS130991?&language=en&posno=1&q=positioning%20assemblies%20assembly%20cuts&source=search • Process Steps • Flexible Components • Harness Features (identified using the out-of-the-box recipe setting adapter/harnessFeatList= , i.e. empty) • Other Assembly Level Features (identified by using the out-of-the-box recipe setting adapter/assyFeatList=911 915 916, i.e. Hole, Slot and Cut, respectively).   Until the latest releases of the publishing adapters, having a mix of Creo Parametric and any 3rd party cad model (using Unite) was also not supported.   To keep a good performance, there’s an extended positioning assemblies method that can help. This one let the worker opens the assembly in a predefined rep and it uses the positioning assemblies workflow for everything it can, and creates dedicated portions of the viewables for the remaining objects (such as 3 components that are cut by an assembly level cut).   OOTB, the users have to set attributes on the CAD assembly to chose what type of publication will be used.   That’s where modelcheck can play a good role. For instance, there’s a OOTB modelcheck control that can detect and count the number of flexible components in an assembly. Unfortunately, there’s no such controls for the other types of limitations (the assembly level features control that exist now can’t be used as way too many objects are detected as assembly level features (spools, annotations, …). Same for the process steps or the harnesses.   The idea is that modelcheck detects all those cases, creates some attributes based on the checks and then we can automatically switch the publication mode based on simple relations or logic.

Include a useable modern font (TrueType/OpenType) compliant with ASME Y14.2 StandardAcknowledged

The purpose is to switch from the ProE font.ndx/stroked stick font to a modern font.  This helps with: WYSIWYG Exporting while maintaining real searchable/editable text...especially for PDFs Creo4 essentially disabled font thickness control (except for entire notes) while the new Bold feature doesn't visibly bold for the stroked font styles. General downstream reuse is impaired by using a stroked font instead of a modern universal font.   It should at least have the following features/compatibility: According to the standard, it should be: All caps with exceptions Gothic/Sanserif (without flourishes) Single stroke (all letters are the same thickness everywhere in the letter)   To be useable it should also be: Monospaced (spaces and letters take up the same space)...this is essential for readability for text alignment and tables on Engineering drawings) Comprehensively changed and controllable with config options MBD compatible (ideally updateable with dwg config or mapkey-able from drawing) Symbol compatible (diameter, degree, etc) Whatever font is used it should be either universally present or embedded.  Not a big problem for Creo because startup scripts can distribute, so this is mainly for other applications (Creo View, pdf, dxf, etc). Nice to haves Ideally, this font should be especially easily legable with All Caps but also lower case. 100% differentiable between letters and numbers (e.g. Il1 = iL1, etc) A text style checkbox like in word to switch between sentence case, title case, all caps, Small caps)   Great discussion on this: Switching from Stroked Fonts to True Type Fonts - Drawings & Models - Observations & Questions    Please comment if I may have missed anything.

Need separate columns for locked status and checked-out status in Windchill WorkspaceAcknowledged

Need separate columns for locked status and checked-out status in Windchill Workspace. Currently it is part of General Status column where checked-out symbol is shown when that object is checked-out by logged-in user or any other user. But when we use preference setting Automatically lock objects added to workspace set to YES, the status of objects is shown with lock symbol overwriting checked-out symbol if that object is checked-out by some other user and not by logged-in user.We are using Windchill 10.2 M030-CPS08  and we have preference setting for Automatically lock objects added to workspace set to YES.But we are facing issue with objects which are checked-out by some other user but it does not shows the checked-out status if object is locked in workspace. Here it is overwriting check-out symbol by locked symbol. So user are not able to recognize if the object they are using is being modified by someone else or not, hence sometime users are using out dated or non-latest iteration of the objects in their assemblies.So if anyone wants to see if any object is checked-out by someone else, user need to manually unlock all objects and see the status which is time consuming activity.Here we propose to have either 2 separate columns one for locked status and other for checked-out status of an object or if with single column checked-out status should have precedence over lock, It means even object is checked-out by some other user, status should show checked-out symbol and not the lock symbol.Plz refer attached images for more information.Below is the preference I am talking about.Name  :  Automatically lock objects added to workspaceDescription  :  Set workspace lock default to automatically lock all objects that are not being checked out during Add to Workspace and Checkout operations. No - (Default) - workspace lock is not set on objects added to the workspace and not checked outYes - workspace lock is set on all objects added to the workspace that are not checked out