I upgraded OS 1.10 today. However, I am not able to modify/add many objects like compact schedule anymore. It is like the functions for flexibility is worsen in new OS. Have any other way to access the same objects like before?
Which font should I encode .idf text for OS import ? Many times when i try to import/export idf file - the object name are groups of unknown characters.
The ability to create and edit many objects in the plugin inspector was removed in version 1.10.0 with this commit in order to fix this issue with those objects being created without required default values, causing the application to crash when it tries to translate the osm to idf. I believe most of them can still be created/edited in the application, or using the SDK.
Wow Eric, thanks, that was pretty much exactly what I was going to post. Most functionality removed from the inspector is available in the OpenStudio Application. Editing ScheduleCompacts is one feature that is not available, I added this item on uservoice to fix that. We do apologize for any loss of functionality, the hope is that it will be replaced in the app soon.
Thank for your reply. In my case, i have question about how to create constant and compact schedule in OS by SDK or something etc ? the ruleset schedule is schedule:day object which is unnecessarily complex for checking if i export to idf. i have font problem with Import/export idf to/from OS as described upward. Have any more newer for This measure https://bcl.nrel.gov/node/37882 still works ? Which is best approach for IDF - OSM file integrated process ? legacy plug-in have only old modifying geometry tools and user scripts which are strongest function of sketchup and OS.
ScheduleCompact is still available in the OpenStudio API. The model object does not have much functionality, so you would have to use Workspace methods like getString, setString, etc. That object is a likely candidate for deprecation in a future release.
I tried to import idf compact schedule in Sketchup: after IDF schedule importhow to make Always Off Discrete label name shown in OS ?and when i try to import OSM schedule from an OSM in OS 1.10 the result is even worsen [after OSM schedule import] https://www.dropbox.com/s/8dan2xn3bs3...). Maybe it's strange but i have not ever met this fault when i did the above tasks in 1.9.5.
I did find one way to still edit compact schedules in OpenStudio 1.10.0 without having to use the SDK. In the OpenStudio application if you are using a compact schedule within GridView you can select that schedule in the main body of the GridView, and the fields to edit it will be exposed in the inspector. This is demonstrated in the screenshot below.
Yes but in this case you can not créate or delete compact schedules Clearlly Version 1.10 is worse than 1.9!!
Asked: 2015-12-17 07:45:25 -0600
Seen: 265 times
Last updated: Jan 30 '17
As for the encoding, what is your systems default location and language? OSM files are written in UTF-8 without BOM. Using this encoding should work for both OSM and IDF.
Hello, i set all seting system regional setting to US. Follow is what i get when i try open .osm file by notepad++ with UTF encoding:
if i create an idf file and try to import idf schedule. The name of imported schedule is also unreadable. How to fix problem ?
Those fields with braces and numbers are not due to font problems, that is the actual content of the file. The OSM format gives every object a handle which is a GUID. When objects refer to each other they do so by referencing the handle instead of the name as in IDF. This makes the OSM format less human readable but the OSM file is not really meant to be modified manually in text editor, it is meant to be modified using the OpenStudio API.
The rest of the ScheduleCompact fields in OSM should be human readable