How to Apply a View Matrix Directly in Creo Simulate Without Recalculating the View

[ilyachaban]

Hi all,

I'm trying to automate the process of taking screenshots of simulation models from different angles in Creo Simulate. My goal is to change the view orientation without triggering a full recalculation of the model.

I discovered that Creo Simulate can write the view matrix directly into an .rwt file. So, I wrote a simple Python script that generates a custom view matrix and inserts it into a template .rwt file. When I reload the file, the view updates to the new orientation as expected.

However, there's a problem: instead of simply rotating the model, Creo seems to fully regenerate or recalculate the view, which adds unnecessary delay. I was hoping for a lightweight change—just to adjust the camera/view angle without triggering a full redraw or computation.

My question is:
Is there a way to apply a custom view matrix directly to the current view in Creo Simulate, without forcing a full view recalculation?
Alternatively, is there a more efficient way to programmatically change the view orientation (e.g., camera direction) for screenshot automation?

Thanks in advance for any advice or ideas!

[vnamboodheri]

Hi @ilyachaban,

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Regards,

Vivek N
Community Moderation Team

[RolandRaytchev]

Hi @ilyachaban ,

I see that no answer here so checked it but seems for me not clear why such workflow should be used and what is the automation effect in that case.

so when I check Analysis in Creo Simulate I need to open it according to the steps ´described in:

https://support.ptc.com/help/creo/creo_pma/r11.0/usascii/index.html#page/simulate/simulate/resltui_loading.html

So when I open an simulation results:

here example above of static analysis with template provided by default in Creo simulate

So I could set a view /predefined in Creo Simulate:

Or I could use dynamic view

or you could use simple activate a view by click on the view  and rotate with the Creo  by mouse with MMB . Later when you have the desired display you can save it then to rwt template - where we need to check that it should save also the model orientation - means that what you want to change later via python directly to the rwt file

For me is not clear what is the more value when you change the rwt file. Possibly you need then to open it and to take the picture but how , Therefore for me is not clear why should be better to have the automatic change of  rwt file. Possibly if you provide some details about your workflow will be helpful. e.g. how do you open the efile and then take the snapshot.

So here is not clear what you meant with recalculate. Why is that a  option which bad Performance? e.g. comparing e.g. to dynamic rotation?

So far I know the  rwt template contains  only metadata Information - e.g. the orientation. So means having the orientation we need to calculate from 3d result geometry  the 2d projection what is displayed in the  result window- it is always projection. What is different  in that case.?

What I believe , when there is an difference  - is that Simulate will see that the rwt file is changed and will interpret it as completely new rwt - so will not consider only the  view change what obviously is required in you case  but also every thing because possibly the dev team did not indented such workflow so via manually  change of rwt and reopen it. 

But as mentioned it depends on your workflow to say what could be an alternative techniques . Do you use some kind of trail file or else ( e.g. Creo Toolkit) in background to start the simulate results?

[ilyachaban]

Purpose of Automation:

The goal of this automation is to export multiple GIF files from modal analysis results, each with a predefined camera position. These animated visualizations serve as a compact and easily interpretable data package, replacing the need for heavier or license-dependent formats.

We only require GIF exports from the modal analysis; no other result types are needed. This approach provides several advantages:

• Readability: GIFs offer a quick and intuitive understanding of mode shapes.

• Lightweight: File sizes are small and easy to share.

• Compatibility: External stakeholders can view the results without any PTC software or licensing requirements.

• Internal Standards: Camera positions are normalized across all parts based on internal conventions, ensuring consistent presentation.

---

Automation Workflow:

1. Simulation Template Load:
   A predefined mapkey opens the simulation results using a prepared template from a designated folder.

2. Frame Capture:
   Screenshots are taken sequentially, exporting all animation frames to a specified directory.

3. GIF Creation:
   Once all frames are captured, a batch script is triggered to:

   • Compile the frames into a GIF.

   • Clean up intermediate image files.

4. View Adjustment:
   The mapkey then changes the view angle according to the next required orientation and repeats the screenshot and GIF creation process.

5. Exit Procedure:
   The mapkey concludes by closing the simulation result window.

---

Rationale Behind This Approach:

This method ensures consistency in visualization across different parts, aligns with our internal normalization protocols, and makes sharing results both practical and accessible — especially when working with external partners unfamiliar with PTC tools.
resources

[vnamboodheri]

Hello @ilyachaban, 

It looks like you have a response from our support expert. If it helped you solve your question please mark the reply as the Accepted Solution. 

Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.