Possible bug: dropuserlibraryobject() causes exceptions during an experiment

Question

question

Jordan Johnson asked Feb 06 2025 at 5:16 PM Jonah K commented Mar 05 2025 at 8:05 PM

Possible bug: dropuserlibraryobject() causes exceptions during an experiment

Note: This question was essentially asked originally in the comments attached to the following idea:
https://answers.flexsim.com/idea/175340/as-onpreparescenario-onscenariostart-trigger-to-ex.html
I chose to extract the relevant information to make it more discoverable.

I am trying to configure my model via code in the OnSet of a parameter. When I change the parameter and reset the model interactively, everything appears to work as I expect; the model is configured according to the parameter. However, when I run an experiment and view the performance measures, I see System Console exceptions on the Console Output tab.

To replicate this issue:

Open the attached model TestDropUserLibrary_Broken.fsm
Load the attached user library UserLibrary1.fsl
Run the Experiment job in the Experimenter
Open the Performance Measures window and view the System Console output.

I didn't expect these exception messages. It seems like a bug because the model behaves differently as part of an experiment run compared to interactive run. Is this a known issue? Is there a workaround I can use?

Software Version:

FlexSim 24.0.8

experimenter bug report user library

testdropuserlibrary-broken.fsm (35.9 KiB)

userlibrary1.fsl (1.6 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2025-02-06T17:26:36Z

Jordan Johnson answered Feb 06 2025 at 5:26 PM Jonah K commented Mar 05 2025 at 8:05 PM

That does seem like a bug. After some investigation, it turns out that the dropuserlibraryobject() command uses the licensehasfeature() command, which is currently broken when called during an experiment. I have added this issue to the dev list.

Until we fix this bug, you can avoid it by removing that check. The check is there to prevent exceptions if a license isn't there. So if you delete the check and you don't have a license, you'll get different exceptions. But if you do have a license, deleting the check will avoid this issue. Add the following code to your OnSet (or in this case, a usercommand that OnSet calls):

treenode licenseCheck = Model.find("MAIN:/project/exec/commandlist/dropuserlibraryobject/node/Check License");
if (licenseCheck) {
    licenseCheck.destroy();
}

See the attached model and use the same user library from the original question:

TestDropUserLibrary_Fixed.fsm

testdropuserlibrary-fixed.fsm (36.0 KiB)

· 2

question