Early days for the new software. Perhaps we could note any problems/solutions/resolution here
Ui-calc is not picking up rooflights
I have a simple box with a window (U1.6) and a skylight(U2.3) Ui-calc reports 1.8 where is that coming from?
Similarly the Ui-min under key features at the bottom of the BRUKL is reporting unexpected values i.e lower than assigned values.
No local vent displayed on BRUKL for 2013 when using ApacheSim
Air Permeability not returning the entered value on BRUKL.
i.e 5.0m3/(h.m2) entered for both side-lit and top-lit returned value 5.2?
Are all ApacheSim models level 5?
Not found anwsers to these questions in the User Guide here: http://www.iesve.com/content/downloadasset_5689
or release notes here: http://www.iesve.com/software/download/ ... -notes.pdf
Issues with VE Compliance 2014
Re: Issues with VE Compliance 2014
All DSM models are level 5: viewtopic.php?f=244&t=5703&sid=04cadf93 ... 6f4#p13401
-
RossThompson87
- VE Professor
- Posts: 202
- Joined: Mon Feb 13, 2012 8:56 am
Re: Issues with VE Compliance 2014
Hi,
I think I've noticed another issue.
With 2013 regs there are a few new variables regarding lighting e.g. entering the luminance (lux) yourself.
Tabular view lets you add these as a column, but doesn't actually display the value or let you edit it.
This seems to be the same for LOR too.
Ross
I think I've noticed another issue.
With 2013 regs there are a few new variables regarding lighting e.g. entering the luminance (lux) yourself.
Tabular view lets you add these as a column, but doesn't actually display the value or let you edit it.
This seems to be the same for LOR too.
Ross
Re: Issues with VE Compliance 2014
I have started a known issues thread where we will report known problems in VE 2014 when they are confirmed.
The roof-light U-value reporting is not an issue. It is just a correction that was made in VE 2014 to ensure we comply with the NCM Modelling Guide.
The assumption that Apache makes for roof-lights is that the u-value you enter is calculated in the horizontal plane and the value you enter/define is what is used in the simulation but for the purposes of the BRUKL Criterion 2 u-value check the limiting u-values are supplied and assessed in the vertical plane so we have to convert roof-light u-values. This conversion is done in accordance with BR 443 and makes the assumption that the conversion is from the horizontal plane to the vertical plane i.e. the u-value is reduced by 0.5 W/m2K.
The roof-light U-value reporting is not an issue. It is just a correction that was made in VE 2014 to ensure we comply with the NCM Modelling Guide.
The assumption that Apache makes for roof-lights is that the u-value you enter is calculated in the horizontal plane and the value you enter/define is what is used in the simulation but for the purposes of the BRUKL Criterion 2 u-value check the limiting u-values are supplied and assessed in the vertical plane so we have to convert roof-light u-values. This conversion is done in accordance with BR 443 and makes the assumption that the conversion is from the horizontal plane to the vertical plane i.e. the u-value is reduced by 0.5 W/m2K.