AStar does not release nodes for longer than Deallocation Time Offset

Question

question

Shinya O asked Jan 09 2025 at 1:19 AM Shinya O answered 6 days ago

AStar does not release nodes for longer than Deallocation Time Offset

Hi,

AStar does not release nodes for longer than Deallocation Time Offset.

In the attached model, TaskExecuter2 is leaving the node in front of TaskExecuter3 at 5 seconds, so it should release that node after DellocationTimeOffset (2 seconds) has passed, but that doesn't seem to be the case.

Is this the same issue as the post linked below?

https://answers.flexsim.com/questions/165940/241-astar-node-deallocation.html

Are there any workarounds?

Thanks in advance.

deallocationTimeOffset.fsm

Software Version:

FlexSim 24.0.7

astar astar navigator deallocation time offset

1736385447972.png (413.2 KiB)

deallocationtimeoffset.fsm (84.5 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-04T19:46:11Z

Jeanette F answered Feb 04 2025 at 7:46 PM Jeanette F edited Feb 05 2025 at 4:55 PM

Hello @Shinya O,
No this is not the same issue. It was determined that model was not repeatable.
I am not seeing the issue you are. I am using 24.0.8. Can you see if upgrading to the latest bug fix resolves your issue?
Edit: dev has been notified of this issue.

· 2

Answer 2 · 2025-04-02T01:04:06Z

Shinya O answered 6 days ago

This issue has been fixed in 24.0.9 as stated in the release notes.

Fixed an issue with allocation release time when travelers become blocked.

question