Periodically, error in flexsim when drag object into model

Question

question

robert.nevin asked Dec 16 2016 at 8:35 AM Ben Wilson commented Mar 02 2017 at 3:18 PM

Periodically, error in flexsim when drag object into model

time: 0.000000 exception: Exception caught in start() of activity "Run LC process" in "Schedule". Continuing throw… time: 0.000000 exception: Exception caught in Executive::processeventinlist(). Throwing. time: 0.000000 exception: Exception caught in Executive::steptotime(). Throwing. time: 0.000000 exception: Exception caught in Executive::tick(). Throwing. time: 0.000000 exception: Exception caught in Executive::tick(). Throwing. time: 0.000000 exception: int runthemessageloop() #4 exception: core->theexecutive.tick(); time: 0.000000 exception: int runthemessageloop() #6

re-opening the application, the error disappears!

Software Version:

FlexSim 16.2.1

graphics object creation generic error

· 3

Arun Kr commented · Dec 16 2016 at 11:51 AM

Can you share the model?

0 ·

Sam Stubbs ♦ commented · Dec 16 2016 at 2:53 PM

IF leaving the program and reopening it causes the issue to disappear it could just be an error somewhere when loading the back end logic of the software. What happens if you reopen the file (after the error is gone) save the file and reopen it again? Does that remove the error permanently?

If not, as @Arun said, we'd need to see the file in order to debug it.

0 ·

robert.nevin commented · Jan 20 2017 at 3:31 PM

rob.fsm finally i have an example of the error (flexsim 2017.0.1). To get the error, run the model briefly...stop and reset. This model doe not serve a practical purpose but is the only one where i can generate the error systematically!

0 ·

rob.fsm (16.4 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 · 2017-01-20T17:16:38Z

Phil BoBo answered Jan 20 2017 at 5:16 PM

Your activities are structured such that they cause an infinite code loop.

It throws an exception to keep the program from crashing on your infinite loop.

If you put a Delay activity anywhere in that code with a value > 0, then it won't be an infinite loop anymore.

Answer 2 · 2016-12-19T17:07:01Z

Ben Wilson answered Dec 19 2016 at 5:07 PM Ben Wilson converted comment to answer Mar 02 2017 at 3:15 PM

Errors when dragging objects into the 3D view are a common symptom of graphics issues.

Please see this article regarding graphics issues and how to solve them.

The short answer is to update your graphics drivers, but please check the article for more details and other ideas.

question