Known Issues

The known issues apply to the current release (Version 1.8.3) of the software, and show workarounds where applicable. There is also a list of Defects Fixed for this and previous releases.

• The displayed fonts on model diagram in Firefox (for both published interfaces and online editing) can have character spacing issues, especially with Arial as the font. Using another font (Open Sans works well) gives better results.
• Displayed fonts can run over text boxes when the amount of text fills the box as interface windows zoom (this can happen on the desktop but is more noticeable when published). To prevent this leave some extra space in text boxes.
• If you release the mouse when dragging a slider on a computer with a touch screen the slider value may hide. This affects both desktop and published interfaces.
• If you are on the interface in experiment mode and editing a numeric input, clicking on the run button in the toolbar will not immediately get the value you are editing. Clicking on a run or continue button on the interface always works correctly (in experiment mode, presentation mode and published).
• If you uncheck the maintain aspect ratio on the Graphics Properties for a graphics box the image may appear blurry on some browsers (notably Chrome).
• Using the new dropdown page selector to move between multiple graphs or tables may not work in full screen presentation mode on a second monitor. It does work when published and in windowed presentation mode.
• Some of the random and discrete builtins generate very tiny differences on Windows and Macintosh computers (and on published simulations). Normally these are not noticeable, but if they are amplified by the model equations (through positive feedback) results may be measurably different.
• Printing will base its page count on the default printer settings. If you want to use a different page size setting, it will work best to set that as the default for the printer and then to close and reopen Stella.
• Comparative graph thicknesses set by graph in version 1.2 or earlier will be ignored. Line colors, patterns and widths for comparative graphs are set in the Graph Styles Properties Panel, and there is an override to set thickness for individual graphs.
• There is a precision limit on the knob on the interface of 0.01.
• Models saved in 1.8.3 not using features new to 1.8.3 are compatible with version 1.1 and later, with some exceptions. First, if opened in earlier versions, the results may not be available, because of updates to the isdb format, so any graphs or tables will start empty. Second, some name positions may be incorrect when a model is open in 1.1.x. The positions will be correct if the model is reopened in the current version (whether adjusted in 1.1.x or not).
• Comparative graphs and tables that have had specific runs selected for display will behave differently than in version 1.1 through 1.6 (see Graph Series Property Panel for more details).
• After typing into a text box, you may need to click twice on checkboxes on the panel (such as Transparent background) in order to change their state.
• When replacing a model using the Interface menu, any Model Views that have tables, graphs, graphics frames, or numeric displays visible will lose the visibility of those elements. It will work better to keep such objects on a template.
• Simulation Events (previously called Posters and Messages) translated from 10.1 that include navigation to interface locations will need to be redone. All simulation event actions will be applied to the interface, so you may need to move them to the model, depending on their purpose.
• Interfaces from 10.1 will come across, but will need to be adjusted. See Using Version 10 Models.
• Opening models from iThink or STELLA versions prior to 10.0.4 may lose interface information (especially stories). For such models, it will work better to open and save them in STELLA Version 10.1.2, and then open them in the new Stella and iThink products.
• If you have set a model to run by sector Storytelling will not work. Storytelling does work with run by module.