I also glanced at the gauges and saw temp 16.2, windchill 17.1 and heat index 16.2 before the customclientraw refresh. So how is customclientraw (using %windch%) showing a different value of windchill to clientraw?
I also note that there is no “wchillTH”:“%maxwindchill%” in customclientraw, so the pop-up doesn’t show max and min values.
I wonder if you have one of the temperature substitution options set in WD? I’m thinking of areas like the humidex substitution on Control Panel/Units/Temperature setup.
Nothing obvious like that but, although I am aware that sometimes options can be set or modified in different places, I have never been interested in artificial indexes so it is unlikely. Anyway, windchill appears to be shown OK in clientraw: it’s just plain wrong in customclientraw.
Still wondering about the setting I mentioned above: “Use the new windchill formula”. Is customclientraw picking up on the old formula?
Think my comment about max windchill may be explained if %maxwindchill% was unavailable when customclientrawlocal was first designed. If it had been available it would surely be %maxwindch% to be consistent with %windch% and
%minwindch%.
The gauges use data that is - broadly - available across a range of software, some offer more or different data than others. The max value doesn’t mean much as it will equal the max temp much of the time, most people are interested in how low the chill went.
the next update of WD will have the code in place to check if the resulting windchill was higher than the temperature (and so its set as the temperature)
that 1 line of code was missing from the tag code
I have the same problem, Wind Chill is higher than Ambient.
Have updated WD to build 74 and problem is still there on both my sites.
See here:- http://monadh.com/nbwcl.php
Brian,
I agree the left one is not currently showing the problem, but it was earlier when i posted the comment. #-o
I have checked and both sites are set up identically.
Any ideas?
Regards
Ray