For a timed DES project, you should never run the SD controllability or S-singular prohibitable behavior check without first making sure that the system is activity loop free (ALF). If the system is not ALF, then running the SD controllability or S-singular prohibitable behavior check may enter an infinite loop. This was because the algorithm was originally written assuming that ALF will always be checked first, but the new DESpot interface allows SD controllability to be checked separately. This issue should be corrected soon.

You should not modify your project (including any DES - this includes the "revert to file" function of the DES editors) while using the DES simulator as this will cause DESpot to crash. If you need to make changes, close the simulator, make the changes, and then reopen the simulator.

You should never have a DES open in multiple editor windows at the same time. This is unsupported.

DESpot has both a tabular DES editor and a graphical one. If changes are made to the DES in the tabular editor, the graphical information will not update until the project is reopened. The DES data will update fine and no data loss occurs.

The MPI distributed processing feature sometimes crashes unexpectedly when a check is being performed. This usually happens when one of the flat project checks doesn't pass. With the current changes, this may not even compile.