FlexSim 2019 Update 2 Beta is available. (Updated 28 August 2019.)
To get the beta, log in to your account at www.flexsim.com, then go to the Downloads section, and click on More Versions. It will be at the top of the list.
If you have bug reports or other feedback on the software, please email dev@flexsim.com or create a new idea in the Development space.
Backwards Compatibility Note: the following changes may slightly change the way updated models behave.
Backwards Compatibility Note: the following changes may slightly change the way updated models behave.
Hi,
warehousing is a great library. Is available a manual? The help is empty. Probably a tutorial to explain the basic idea is necessary.
Which are the compatible NVIDIA card for RTX mode? I have a NVIDIA Quadro P3200, but a popup appear when I active the mode. Isn't it enough or I need to active some graphic card configuration?
Probably I found an issue with transporter. It doesn't update correctly the position during travel task to the source.
The new Warehousing objects do not have documentation yet. We are still working on documenting them. More documentation will be available as we release subsequent iterations of the beta.
A Quadro P3200 is built on the Pascal architecture, which should be compatible with RTX Mode. Try updating your graphics driver and make sure you are using 64-bit FlexSim.
Thanks for pointing out the issue with the transporter. We'll look into it.
Hi,
Nice addition with all new racks. Some things I found/noticed:
-When I change the visualization of a floor storage rack to "Repeating bay supports" the visualization is a little bit of. The drawn supports are outside the object. This holds for multiple option in the visualization. I don't know if that is a setting that should change in the GUI or if it is a small bug (see picture)
-If you don't drag in a Storage system object you are not able to change the visualization of the rack objects. Not sure if that is intentional or not. I guess I will need to read the manual when it is there.
-The option to collapse event in a wait for event is really nice, it would how ever also be nice if you would be able to remove the first event from a wait for event, now all events can be removed but the first not. Is this something that is forgotten or would this be a new feature?
Thanks for the new Beta.
The transporter's default Flip Threshold was changed from 180 to 179 so that it would back out of a Drive In Rack by default.
We will change it back to 180 so that it works for this situation by default again, and we will add a note to the documentation of the Drive In Rack about how you can adjust the Flip Threshold to 179 for a Transporter to back out.
Thanks again.
1. We'll look into the weirdness of trying to use visualizations on the floor storage that weren't designed for floor storage. Thanks for pointing that out.
2. This is by design. The objects use default visualizations if you don't have a Storage System in your model. If you want custom visualizations, you need to add a Storage System.
3. This has always been that way. In 19.2, we just made it so that the UI is collapsible so that large lists of events don't take up so much real estate on the screen that you can't access the entire popup. I'll add a case to the dev list to consider being able to remove the first event from the list.
Thanks for the feedback.
We didn't add a new "bool" datatype to FlexScript. That's just what the function returns in C++.
When we update the FlexScript API documentation, it should correctly say "int".
Thanks for pointing this out.
I found an error in the case of using the new storage objects like gravityflowrack etc. The example simple model is the captured;
The error is followed.
time: 0.000000 exception: Exception Caught in ObjectFunction248__project_library_FlexSimObject_behaviour_eventfunctions_OnTimerEvent object: /GravityFlowRack1 i: /GravityFlowRack1>variables/bays/1/levels/2/slots/1/slotItems/1 class: /GravityFlowRack1 time: 0.000000 exception: Exception caught in TreeNode::receivemessage() 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: int runthemessageloop() #4 exception: Executive::instance.tick(); time: 0.000000 exception: int runthemessageloop() #6
The error is same with using transporter.
Thanks for pointing this out. We will fix this for the next beta release.
This has been fixed in the 9-Aug beta.
Thanks for pointing this out. We'll look into it.
1. We've fixed the weirdness of the visualizations drawing outsize of the floor storage area in the 9-Aug beta.
2. We've changed the Storage System object so that it gets asserted when you create a Rack instead of needing to explicitly add it. This way, you'll always be able to see the visualization options.
Thanks again.
The beta released on 2019-08-02 had the following issues with tables:
This issue has been fixed for the latest release of the beta. However, if you have created a model in the version with this issue, you will need to run the following script, save the model, and then reopen the model to fix the issue:
treenode peopleTables = Model.find("Tools/PeopleTables"); if (!peopleTables) { return 0; } Array templates = ["StaffStateHistory", "LocationStateHistory", "TransportStateHistory", "EquipmentStateHistory"]; Array badTypes = [2014, 2025, 2034, 2044]; Array goodTypes = [2015, 2026, 2035, 2045]; for (int i = 1; i <= templates.length; i++) { treenode table = peopleTables.find(templates); if (!table) { continue; } if (getvarnum(table, "type") == badTypes) { setvarnum(table, "type", goodTypes); } }
In the beta previous to the 9-August-2019 beta, the Escort to Exit activity set contained a corrupted activity. This causes many chart templates, such as the Avg Staytime and Avg Time in State People Templates to not work correctly. To fix models built in older beta versions, you will need to delete the Remove Person activity and replace it with a new one.
This is fixed in the 21-Aug beta.
The latest beta (28-Aug) has more Warehousing documentation in it. See:
We are actively adding more documentation prior to the final release (several sections are still incomplete), but there should be enough documentation there now to get started learning how to use the new Warehousing features.
I posted an article with a demo warehouse model. I made it in the 28-Aug-2019 version of the beta:
https://answers.flexsim.com/articles/71515/2019-update-2-warehouse-demo.html
When 3D modeling using Rack and TaskExecuter, the transporter can not move.
The warehousing objects no longer behave as Fixed Resources using traditional port sending logic by default.
When you connect a fixed resource to a rack (or vice versa), it sets a variable called "Use as Fixed Resource" on the rack that tells the object to use the traditional port sending logic:
(The model also isn't working because Use Transport isn't checked on the upstream Exit Transfer.)
This appears to be a bug that the Rack isn't setting that variable automatically when connecting from a Conveyor. You can manually check the box to fix it. Thanks for pointing this out. I'll add a case to the dev list to look into it.
I knew already the edit mode control of up2 version. It's very not comfortable. I am looking for easy control feature of the old 'Layout' features. It provides Columns, Offset, width, Length and orientation for each chair's row and column. The new 2019 version can't provide the good and convenient setting interface like my attached picture. I hope you should use HC 5.3.10 Layout control features.
If you draw 60 chairs of it, will you add the more chairs and change the position again for each chair?