As the picture shows, it is very helpful that the four PF "Source" activities named like :Source1\Source2\Source3\Source4 when some exceptions occur with the PF. This can help us locate the problem activity quickly just like the 3D model. Show More

Hi, I would like to suggest adding a vertical acceleration parameter for ASRS movement, since I'm facing this limitation in the models I'm currently developing. I've seen a few posts complaining about it, but I think it hasn't been posted as an idea yet. Thanks in advance! Show More

In FlexSim 25.0, BasicFR and BasicTE have been removed from the standard 3d library. I am using them a lot when I teach FlexSim. Please vote to restored them in the standard 3d library. Show More

Conveyors can be performance inefficient if a model grows too large. Often, conveyor geometry does not match model logic, rendering FlexSim models with an inflated number of unnecessary conveyors. Being able to create polyline conveyors (such as in Anylogic and other simulation software) would reduce the number of conveyor objects, transfers (entry/exit), and unnecessary event listening (conveyor entry/exit). It would also help to produce models faster and less prone to errors due to "conveyor overlap blocking flowitems" caused by conveyor shifts or by the "join conveyors tool". Show More

It would be great if tables, queries and lists contents could be watched during the debug process: Show More

It would be great if the table editor window allowed users some very basic features: - line/column reordering - paste single value to multiple rows/cols - column filtering Show More

  Would be pretty neat if you could visualize the route that AGVs will take/have taken for a single travel task. This is wrapped up in a module I've developed, so I can't openly share the code, but would be great if it was part of standard FlexSim.   Show More

Model parameters and performance measures are tightly coupled to the model development. Often, as models grow complex, data structures need to be changed, and their mappings to parameters, performance measures need to be updated. Having to access three levels of windows to access the mapping of such structures is cumbersome and time-consuming. Having to three-click to access drop-down options is also frustrating and inefficient. A simple one level table with progressive columns to be used (or left empty) would improve usability and allow for more visibility of the current mappings. >>> In addition, the eyedropper option should be capable of mapping table values by their row/col numbers (or, even better, headers). I hope this helps. Show More

Hi FlexSimmers, This is a common performance measure requirement which is asked by many customers of us. Constructing the utilization vs time is not an easy task also. The user has to create the utilization vs time from the conceptual model which we provide. I believe that this graph will be a useful addition to the dashboard library in the state section.   https://answers.flexsim.com/questions/111045/how-to-graph-utilization-vs-time-in-dashboard.html Regards, Arun KR Show More

Deadzone: Adding a "Deadzone" to J1 of the robot which the robot cannot rotate through would be helpful. Create a setting which the user can input the deadzone size (Ex. 20 degrees) and the degree in which the center of the deadzone resides (Ex. 180 degrees). This would result in the rotation of J1 being between 170 degrees and -170 degrees, a total of 340 degrees.    Joint Speeds: Creating a way to use joint speeds while still controlling robot motions with the motion path option would be beneficial. This would allow the user to input the robot manufacturers joint speeds for J1-J6. Then instead of using the "MoveTime" in the robot motion paths to "weight" the individual motion, allow for the user to input a percentage of the max joint speeds to run the robot at for that individual motion. For example, this would allow for a single motion path to have the robot travel to an "above" point at 100% speed and then travel to the "pick" point at 30% speed. This could be set up to work only when the "Path Cycle Time" is set to "0" to have the "Path Cycle Time" remain as an option for some users.   Part Offset: Creating a registry of offsets to use with robot motion paths would be helpful. This would primarily adjust the X, Y, and Z location of the robots J6 by a preset distance from the actual point which the motion path is taught, adjusting the rest of the joints accordingly. For instance, this would allow for a pallet with 9 circular parts evenly spaced in a 3x3 pattern to be unloaded by the robot by using a single motion path. This would work by having the user input X, Y, and Z offset values into the columns of a table with each row representing an offset location. The user could then set a parameter in their process flow "Task Sequences" logic to use the desired offset. This parameter could be easily modified using custom code to increment or adjust the offset parameter being used, so all 9 part locations could be picked by using the same block of logic as well. With this, the user could set the motion path to have the robot pick up one part off the pallet and then apply the "part offset" to the same motion path the next time the robot picks from the pallet. This would move the robot to the adjusted location (likely above the next part to be picked). This would either prevent the robot going to the same point on the pallet (where the first part was picked) while using a single motion path to unload all 9 parts, or this would prevent the user from taking the time to create a motion path for all 9 of the parts individually.   Light for Robot Vision: Adding a light to represent the robot executing a vision process would be beneficial. This light would be on the underside of the robots EOAT, so the user could position the robot above the pallet or parts which are being scanned and then turn on the light. This light could be turned on by a process flow "Task Sequence" logic with options such as color, brightness, and duration (with a "leave on" option). This would be helpful to account for vision processes as adding the visual of the light scanning the pallet or parts is something that can be easily recognized compared to just adding a "Delay" while the robot is stationed above the pallet or parts.    Show More

It would be great if the properties window of the tree had buttons available for the options in the view pop-up menu. In addition it would be great if the user could set a name width for the tree view as part of the global preferences. Show More

When we import an Excel table of data and we want to use one of the fields (columns) as a Parameter in our model, we currently have to duplicate this information field in the Parameters table. This can be done automatically through code but it's inefficient because we already have the info in our model but just not in the right table. And yes we can import Excel data directly into Parameters table but most of the time (in my case) the table I import has 20 columns of data that is used in the simulation but only one of these columns needs to be a Parameter. A solution to this would be to be able to put Parameters in a Global Table. Maybe have the option to designate a column as "Parameter Data Type" and it would be recognized everywhere as a Parameter even if it is not in the Parameters Table. Thanks, Show More

Hello, I noticed that when an object is destroyed manually, any open code or table window relative to that object remains open having to be manually closed. In addition, if the model is saved, closed and reopened, the window will come back with a NULL reference. I would like to suggest that such windows are closed automatically when the object is deleted, to increase model housekeeping. Thank you. Show More

Hello, currently the tree uses different icons for objects, code nodes, and general nodes. However, as objects have two "modes" (i.e. a "folder" node - colorful - and "object property" - grayed), sub-nodes will have different behaviors depending on which mode they were created (e.g. "dropscript" does not execute if placed under an object in the "folder" mode, which is appropriate, but can be overseen by an user). It would help to have a visual distinction for the sub-nodes in this case, to facilitate modeling and error reduction. This also would help users to understand better the syntax required "/" or ">" when accessing nodes. Thank you. Show More

In general, that would be a value added for our leads & users if the corrected models were available for download for each tutorial. That helps a new user to compare if he has built the model correctly. Some tutorials also act as demo models, you can download the tutorial model to check if this tutorial really matches the features you want to learn / build. In some competitive software, like Anylogic, you can download the corrected model for each tutorial phase. Ex: https://anylogic.help/tutorials/job-shop/1-simple-model.html If FlexSim wants to improve the quality of tutorials, please add a link to download the corrected model for each tutorial in the user manual. Show More

GIS Map route works on FlexSim using two parameters (Duration and Distance). Since we use a TaskExecuter to do this trip, it would be very handy to use TaskExecuter's speed values, varying its trip duration. I think adding a function on GIS Map to consider the TaskExecuter's speed values would be a good improvement to the GIS Map functionality and to the results and statistics got using it. Show More

It would be great if one could export/import configurations for collectors, calculated tables, dashboard widgets, charts, etc. from one model to another, as copying/pasting is currently unavailable. Thank you. Show More

Since the usefulness of a delay 0 is now acknowledged by the new Breathe activity, and given that you almost always want to do a Breathe after a Wait for Event, I propose to add a checkbox "Breathe before releasing token" to the Wait For Event properties and switch it on by default. Show More

Having a single, global "Simulation Stop" button in the interface would help to speed up debugging and enhance control when breakpoints are in use. With breakpoints, several portions of the interface become non-responsive to user clicks, the Stop button being one of them. In some unfortunate cases, a chunk of a process or code might become an unintended infinite loop. When that happens, FlexSim crashes or has to be killed manually, not allowing for any recovery in the same session. Show More