External files optimization: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:windPRO 3.0 Service Pack 2 Category:windPRO Known Issues-3.0 Category:windPRO Known Issues '''Status:''' Open - will be part of windPRO 3.0 Service Pack...") |
No edit summary |
||
| Line 3: | Line 3: | ||
[[Category:windPRO Known Issues]] | [[Category:windPRO Known Issues]] | ||
'''Status:''' | '''Status:''' Closed - part of windPRO 3.0 Service Pack 2 | ||
'''Fixed in build:''' 621 | '''Fixed in build:''' 621 | ||
When importing a project- or an object-export the paths to external data files must be updated. Certain meteo logger formats, such as Ammonit, can generate very large number of external files which meant that it could take hours to load a project export. This has been fixed in build 621. | When importing a project- or an object-export the paths to external data files must be updated. Certain meteo logger formats, such as Ammonit, can generate very large number of external files which meant that it could take hours to load a project export. This has been fixed in build 621. | ||
Latest revision as of 13:50, 13 August 2015
Status: Closed - part of windPRO 3.0 Service Pack 2
Fixed in build: 621
When importing a project- or an object-export the paths to external data files must be updated. Certain meteo logger formats, such as Ammonit, can generate very large number of external files which meant that it could take hours to load a project export. This has been fixed in build 621.