UMI Release Notes 2.6.25 UMI will now respect changes to building visibility immediately, without needing to reload the project. The daylighting simulation now has an experimental streaming mode, which should reduce memory consumption substantially. Enable it with the UmiSetDaylightingStreamingMode command. 2.6.24 When exporting daylight results for buildings that have had no other simulations run, the generated CSV contains building names instead of building IDs. 2.6.23 Daylight sensor culling has a new pre-filter applied, drastically improving its speed. 2.6.22 Previously, when window or floor line previews were "disabled," they were still generated, but merely hidden. They are now properly disabled, substantially improving UMI's performance. Daylight simulation preparation has been improved: Some minor performance improvements have been made. The preparation is now more verbose. 2.6.21 The daylighting module shows more granular log output, and can be canceled in more places. The daylighting module now only includes objects (buildings, shading, physical boundaries) within a set distance from simulated buildings. The default distance is 100m. The distance can be edited with the UmiSetDaylightRadius command. Changes do the distance are not saved when Rhino is restarted. The "inclusion shell" can be viewed with the UmiToggleDaylightRadiusPreview command. 2.6.20 Some performance improvements have been made to the daylighting module: The module ignores Rhino autosave events like the rest of UMI. More of the module is disabled when no UMI project is loaded. Result sets are saved and loaded via streaming. The UmiWhereSqliteInterop command has been added to assist in diagnosing third-party module problems. Geometry generation within the shoeboxer is more robust. 2.6.19 The energy module can now consume weather files with spaces in their paths. 2.6.18 Thermal comfort calculation can now be disabled when projects' energy is simulated on an hourly basis. When energy simulations are run without thermal comfort calculation enabled, existing thermal comfort data are deleted, reducing bundle size and improving load times. The UmiSetBuildingSetting command now properly updates the building settings panel, and a project reload is no longer required to pass the new settings to simulators. 2.6.17 UMI handles energy simulation for large projects better. Energy simulation respects cancellation at more points in the process. 2.6.16 Building templates can now have default WWR values assigned in the template editor, and UMI will use these values when new buildings are created. 2.6.14 A rare Rhino crash caused by the splash screen has been eliminated. 2.6.13 UMI will show the building settings controls even when the selected buildings do not share a template. The skylight WWR can be adjusted in 1% increments by the arrow keys when selected. 2.6.12 UMI's template library editor provides better error messages when a library fails to load. When an UMI project is open, moving lots of buildings should not cause a substantial Rhino pause anymore. 2.6.11 UMI now requires .NET Framework 4.6.2 (it used to requre 4.5). Modules can now define custom defaults for custom settings types they use. The mobility network debugging preview now highlights departure points that were not added to the network. UMI now allows skylight definitions, although no first-party modules use them. 2.6.10 The energy simulation's performance on large models has been improved: More cancellation checkpoints have been added, making cancellation more responsive. More steps are run in parallel. Launching the simulation via the panel causes less initial Rhino input lag. The energy simulation has had some more specific error messages added to the post-simulation stage. 2.6.9 The Grasshopper component for retrieving series data will return building series in the same order that the input buildings were in. 2.6.8 Building names will refresh in the summary view shown by UmiListObjects when changed. 2.6.6 The energy simulation will run even if a building's WWR is set to 0. 2.6.5 The site analysis module now falsecolors buildings based on their template name. 2.6.4 The site analysis module now presents more site statistics, including template group-level statistics. 2.6.3 Template library CSV import is now more flexible about the date format it accepts. 2.6.2 UMI now ships and uses EnergyPlus 8.4. 2.6.1 Module authors can now define a falsecolor function from an entire building, not just a Rhino object ID. 2.6.0 UmiCommand now has properties and a method that can be used to detect the current energy simulation status and launch a new one, allowing modules to trigger energy simulations and use their results. 2.5.16 UmiModule now has an OnEnergySimulationCompleted for more easily capturing energy simulation results. (This functionality was already available in UmiEventSource, but now it's also in this more convenient location.) 2.5.15 Two new Rhino commands have been added: UmiImportTemplateLibraryCsvs and UmiExportTemplateLibraryCsvs. These import and export the loaded template library as a set of CSV files for easier bulk editing. updates in 2.1.21: -the buggy ASHRAE-inspired template libraries have been removed; Boston is now the default -winter heating is no longer disabled in the default Boston and Lisbon template libraries -the recent projects list should no longer have any empty entries -invoking the mobility simulation via the button with nothing selected will no longer require another prompt updates in 2.1.20: -when buildings are hidden, their data in the database are not deleted -the building settings panel now restricts WWR to 90% (higher values can cause simulation errors) -if an umi plugin is loaded by the user, its simulation tab will now appear in the simulations tab control without restarting rhino -lifecycle simulation no longer restricts buildings to having a single downward-facing face updates in 2.1.19: -fix a bug in the template editor that would cause a crash when changing a component's category name to a non-existent category updates in 2.1.18: -FAR calculations can now accept trimmed surfaces -the units in the default dashboard header have been properly set updates in 2.1.17: -a FAR calculation run with invalid site boundary objects will produce a more helpful error message -data imported via UmiImportUDX is now properly written to the dashboard output file updates in 2.1.16: -perform selection calculations on a background thread, so umi does not lock up Rhino when large selections are performed -fixed bug that would move selected objects to the buildings layer whenever the buildings settings tab lost focus updates in 2.1.15: -added dynamic dashboard header import and export commands updates in umi 2.1.14: -fixed a bug that prevented the import of new amenities profiles updates in umi 2.1.13: -more cases in mobility simulation are handled, including curved streets and intersections of more than two street curves -improved operation of UmiRebuildDatabase command - use this (nondestructive) command if you encounter any "foreign key constraint" errors -bug fix for internal umi file handling operations updates in umi 2.1.12: -a rounding bug that caused building floor counts to be miscalculated has been fixed -UmiSimulateEnergySynchronous has been added, to facilitate scripted simulation runs -importing a new template library in scripted mode will no longer cause a modal pop-up if there are missing templates\ -umi will no longer mistakenly use core CoPs to calculate the site energy of perimeter zones updates in umi 2.1.11: -overheating calculation now uses operative temperature -overheating calculation now only considers occupied hours (defined by the average occupancy of the building's zone and perimeter being >= 0.2) updates in umi 2.1.10: -increased speed and stability of energy simulation -layered constructions can now be constructed in the template editor without crashing it -domestic hot water is now part of total energy consumption -a few scenarios in which old data got left in the database should no longer be possible -the usability of the thermal comfort facility has been improved -umi is now snappier and more efficient when working with hourly simulation results -old temporary files left around by crashed Rhino processes are now cleaned up updates in umi 2.1.7: -a thermal comfort calculation has been added -some missing units have been added to the template editor updates in umi 2.1.6: -non-dot decimal separators are now supported -buildings are now properly grouped by all their settings, not just their template name -the zero-cost materials check has been disabled because it was generating false positives for air materials -temporary files are now cleaned up even if they contain read-only files updates in umi 2.1.5: -updated Boston, Kuwait, and Lisbon default template libraries -fixed bug where energy simulations couldn't be run for new projects (only loaded ones) -fixed bug that was preventing projects from being viewed in the dashboard updates in umi 2.1.4: -weather files and Windows usernames with spaces now work -Grasshopper project reader component now exposes project settings -there is now a Grasshopper component to list the series stored in an umi database -template library export dialog now correctly uses *.json filter instead of *.xml -mixed-used buildings can be modeled by assigning the same name to two umi buildings -heating and cooling energy demand is now site energy and not loads -other miscellaneous bug fixes and interface improvements