Skip to main content

Filter by idea status

Filter by product

6851 Ideas

Build a CREO camera analysis tool like Solidworks Camera View.Acknowledged

Please include detailed documentation such as screenshots, images or video.1. What product and version are you running?CREO Version 7.0.12.02. What is the problem?I have a lot of problems, but we'll concentrate on this one...  Unlike Solidworks Camera View, Creo Manikin lacks including but not limited to field of view, camera type, positions, depth of field, target points, and camera rotations to perform visual analysis through its camera lens.These limitations have prevented our top-level design team from using CREO as the main CAD tool and constantly resort to using Solidworks to perform camera view analysis.https://help.solidworks.com/2023/english/SolidWorks/sldworks/HIDD_DVE_CAMERA_PROPS.htm?verRedirect=13. Are you using a workaround? If yes, please describe it.Solidworks Camera view in Solidworks.  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.Camera view analysis through a camera lens is critical to our commercial satellite development.The camera view analysis is to study various camera field of view, depth of field, line of sight, positioning, and other requirements to ensure proper camera fitting to view external and internal critical areas of the satellite during its operation in harsh environment. The camera view could have other practical applications in sea, air, and other spacecrafts where the human body cannot endure the harsh environment.5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)Roughly about 3 top level designers are affected.If CREO had the same camera analysis tool as Solidworks, designers could have completed the analysis in 6 to 8 hours in CREO vs. 8 to 10 days in Solidworks.WHY - Unlike CREO, Solidworks is not a powerful top-down CAD tool to support and manage large model assembly. As a result, users spend hours and days watching Solidworks spin the blue circle of death loading and/or responding to user commands. After all set and done with the camera analysis, users will go onto a tag team wrestling match with SAVE and CHECK-IN of the files. If successful after 10 hours, users can celebrate their victory with a 10-year-old bottle of bourbon. If not, users will move onto Royal Rumble, WrestleMania, Solidworks support. If all else fails, admin submit a CREO enhancement request.Vote for my idea.

Improve Property Change Logic (glitches)Archived

Problem: Changes to assembly properties should be saved at the part level. Visibility, Color, Position Otherwise changes to properties of parent or child (assembly or part) may conflict - with odd results. Here's one way to see this error:   Time (seconds) Item Action Visibility 1:00 - 2:00 Part B  Fade Out True -> False 2:00 - 3:00 Assembly A (contains all) Fade Out True -> False 3:00 - 4:00 Part B Fade In False -> True 4:00 - 5:00 Assembly A Fade In False -> True   Part B fades out, but immediately at time = 2:00 Part B suddenly reappears and then fades out again. Whatever causes this is the crux of the problem.   It's not a big issue in this particular example, but in other situations it expresses itself in more frustrating ways that cause problems with our augmented reality training for technicians. Sometimes a multi-part tool will stay visible in the wrong steps because its visibility Boolean was messed up somewhere along the way. I turn visibility of assemblies and sub-components on and off, both for the product, and the set of tools that are used. Sometimes a particular tool will fade out but then suddenly become visible in all previous steps.   Solution When a user changes a property of an assembly, logic should be run in the background that goes through every single sub-component and decides whether or not to change its property. All properties should be retained at the lowest part level.   Example:   Assembly A Part B Part C 1) Fade out Part B Creo checks B for sub-parts none found so transition to B.visibile = False 2) Fade out Assembly A Creo checks A for sub-parts B.visible = False, so no change C.visible = True, so yes change Only transition to C.visible = False 3) Fade in Part B Creo checks B for sub-parts none found so transition to B.visibile = True 4) Fade in Assembly A Creo checks A for sub-parts B.visible = True, so no change C.visible = False, so yes change Only transition to C.visible = True