FlexScript exception: MAIN:/project/exec/globals/nodefunctions/switchmodelhash

Question

question

Sung K2 asked May 15 2024 at 1:32 PM Jason Lightfoot answered May 20 2024 at 4:25 PM

FlexScript exception: MAIN:/project/exec/globals/nodefunctions/switchmodelhash

exception: FlexScript exception: MAIN:/project/exec/globals/nodefunctions/switchmodelhash

FlexSim throws an error message above, when I try to save the model after I edit/open/close some of Flexscript like usercommand.

If I ignore, close with SAVE, and reopen, the message is gone even though I save the model multiple times after edit the Flexscript for a while. But at some point it happens again. I couldn't find the exact cause yet. The only way for me to get rid of the error message is re-opening my model.

Anyone knows what I did wrong? Any clue about the error message? Any advice will be appreciated.

Software Version:

FlexSim 24.1.0

exception error flexscript exception switchmodelhash

______

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 · 2024-05-20T13:47:06Z

Jason Lightfoot answered May 20 2024 at 1:47 PM

If you can save a model such that when you open it and run applicationcommand("hash", model()) it gives an error - please upload for the team to check which part of the model is giving the error.

· 3

Sung K2 commented · May 20 2024 at 2:07 PM

Thank you for the explanation. However, I didn't run applicationcommad("hash", model()). I don't even know what it is. Is there a model event triggering the appllicationcommand("has", model()) automatically?? I am sorry that I can't share the model due to the confidentiality agreement with client.

0 ·

Jason Lightfoot ♦♦ Sung K2 commented · May 20 2024 at 2:14 PM

You'd run that from a script console. Yes it's triggered by default when you load and save a model.

If you can't share it then you'll have to try deleting successive objects and running that command until it runs without exception. Without knowing what those objects are we won't be able to diagnose or help further.

0 ·

Sung K2 Jason Lightfoot ♦♦ commented · May 20 2024 at 2:29 PM

Thanks! I will try to follow your suggestion, deleting successive objects to find out what causes the exception.

One question, though. If the model has an object that causes the exception, why it does not throw the exception when I reopen and save the model again? I can successfully edit my scripts and save the model multiple times after reopening the model. It works fine for a while, but eventually throws the exception at some point later. It seems so random to me...

Thanks again for your advice. If I found any, I will share it here again.

Thanks!

0 ·

question