question

Tam P avatar image
0 Likes"
Tam P asked Matthew Gillespie commented

Pro Flo Tut 4 sec 4.4 Invalid destination at move object

I am getting this error.

time: 229.369036 exception: Error: Invalid destination at move object activity "Move Object: Into Model" in "Sticker Roll Logic"

I have what the tutorial shows. How can I fix this?mistake-note.jpgproflowtut4atmpt2.fsm

tutorial
mistake-note.jpg (230.9 KiB)
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

·
Joshua S avatar image
0 Likes"
Joshua S answered Matthew Gillespie commented

Use up(current) instead in the Destination field, current.up worked on older versions.

· 5
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Tam P avatar image Tam P commented ·

That seems to fix the problem. Thanks a million. Will you be fixing the tutorial for future users to not have to encounter that? Thanks. I am glad I finally got it to work.

0 Likes 0 ·
Joshua S avatar image Joshua S Tam P commented ·

Yes, we are compiling a list of things that need to be changed in the manual as new versions come out.

0 Likes 0 ·
Steven Hamoen avatar image Steven Hamoen commented ·

@Joshua S This answer confuses me a bit, because the dot notation has come to Flexsim since version 2016 or something and the up(current) was always there. So are we going back from current.up to up(current)?

0 Likes 0 ·
Joshua S avatar image Joshua S Steven Hamoen commented ·

@steven.hamoen

This confused me to so I played around with it a little and found out that there was something going wrong with the referencing the first time current.up was put in. removing it, running it, even if errors pop up, restarting it then putting current.up in fixed it. current.up is fine, just something weird with some sticky referencing going on with this model.

0 Likes 0 ·
Matthew Gillespie avatar image Matthew Gillespie ♦♦ Steven Hamoen commented ·

No, current.up is newer and correct. There was a bug that made properties on current look for a label instead of the property (i.e. current.up was looking for an "up" label on current). This bug has been fixed and there's no need to use the up() command.

@Joshua S, your answer is incorrect. There are no older versions where current.up worked and up(current) would not.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.