PDA

View Full Version : Problem with the reset button FS 5.0


luis quinones
05-31-2010, 04:57 PM
Hi, I am having a little problem with the reset button on FS 5.0 . The problem is:
1) I drag an object on the 3D view and place it for example on the (0, 0, 0) position
2) I click on the reset button (nothing happens as expected)
3) I move the object to the position (7,7,7)
4) I click again on the reset button and then the object automatically moves to his original position (0,0,0)
I am working on Vista and I installed the software un C//Flexsim5.
Thanks,
Luis Quinones

Tom David
05-31-2010, 10:59 PM
I am not sure, what you mean by 2) … nothing happens as expected …

What I guess what is going on is, that you set a reset position for the object (right click / Edit / Set Object Reset Position). If you now move the object and press Reset, it will jump to the Reset Position.
You can check the Reset Position in the tree under Variables / resetposition. Just delete the node in the tree, if you want to get rid of the Reset Position. Or use the Edit Selected Objects and Clear the Reset Position.

I hope this helps, if not, please try to explain a bit more clear what is not working as expected.

Phil BoBo
06-01-2010, 09:59 AM
In the Flexsim 5.0.0 evaluation version, it set the reset position of the objects automatically when you save the model to ensure repeatability. This has been removed in the latest version.

You can use Tom's suggestion about the right-click option Edit > Set Object Reset Position or the Edit Selected Objects window to change the reset positions.

JMEngelhart
08-26-2010, 08:43 AM
I have seen similar issues with Reset in V5. It appears that you sometimes have to click Reset twice to get everything to apply. This is especially true when you have copied variables from one object to another.

Doing the double reset seems to work consistently.

Steven Hamoen
08-26-2010, 08:57 AM
I expect that you have to take a good look at your code and see if you use the setrank command or change object positions in the tree in a different way.

Because the reset simply walks through the tree and that way if you move an object into a tree position that is already passed in the reset loop, the resettrigger of that object will not be executed. So a second reset is necessary to execute all code.