Currently when copying over models it erases all the object references in triggers (wait for event, event-triggered source) - despite the fact that the model might have the objects being referenced copied over.
Currently when copying over models it erases all the object references in triggers (wait for event, event-triggered source) - despite the fact that the model might have the objects being referenced copied over.
Hi @Christian P3, was Jason Lightfoot's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.
If you just sampled an object and had it's pointer (memory address) in the activity's object field, then it will not be able to know to which object that refers when transferred to a new model since everything has a different memory address.
You can refer to objects using groups, find() or label pointers on member objects within Object Process Flows such that your process flows are portable - but you need to design them that way.
15 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © Autodesk Inc. All rights reserved