A quick fix (tested in W7 64-bit) : 'Control Panel' > 'Clock, Language, and Region' > 'Formats Tab' and change comma separator into point.
My first guess is that you are entering an invalid value for a field, such as a number greater than 1.0 for Thermal Absorptance which expects a fractional value. We generally follow the EnergyPlus IDD for what values are acceptable.
Validation doesn't happen right away, so a bad value may appear to stick, but then will revert to old value if you leave the object and come back. We have an issue filed for this. Ideally it will never let you type an out of range value.
I tried this same value on Windows 7, Windows 8.1 and Windows 10.
In Windows 7 everything is ok. It means, that after saving project the values are changed in material. In Windows 10 (or 8.1) after saving (after saving and restarting software also) material has default values.
I tried also on thickness - default value is 0.003 m. I tried to change to 0.005. And it's working only at Windows 7 (but it's not my computer to normal work, i must solve this problem in Windows 10 or 8.1)
With Openstudio 1.10.3 Windows 10 I can't edit the properties of the materials. I can't put the dot. If I try to put a integer value it assumes that value.
@J Monteiro, Did you look at @Urado's answer? seems like what you are seeing.
David Goldwasser it works like @Urado's answer. But is not so comfortable to always changing the 'Formats Tab'.
Asked: 2015-10-27 09:02:32 -0500
Seen: 681 times
Last updated: Jan 18 '16
anyone, something?
I have a similar problem on my computer ( OS 1.9.0, Windows 10) I can't change the thickness of a given material using the openstudio app. I can enter the value using a comma but it is not stored when I change materials. The field doesn't accept a dot (ie 1.2) but only comma (ie 1,2) I can change the thickness manually in a text editor but it is time consuming
Just for some extra information for anyone seeing this, are you on a US version of Windows 10 vs. a non US version.
Windows 10 Entreprise 64-bit (10.0, Build 10240) (10240.th1.150930-1750) I'm in canada so I'd say non-US. The decimal symbol in regional settings was changed to a comma somehow. Resetting the decimal symbol to a dot fixed the issue
Non US version.