there is no image attached unfortunately. However, from your private message I get the error you're receiving is "Yp2 ist kein gultiges datum" what translates to "Yp2 is not a valid date". I'd therefore recommend to check the date format in the file as well as in the settings.
basically you can calculate most thermal indices (including UTCI) based on those parameters, yes (given you also know date and time of the readings).
The issue you might run in is, as you already noticed the wind input limitation of UTCI: As suggested in Broede et al. 2012, you could replace all wind speed lesser than 0.5 by 0.5 m/s (accepting some imprecision) or you should additionally calculate another thermal index to assess differences in this area.
The issue with the cloud cover is rather easy to solve. They are linear scales both, so simply do basic math: cc_8 = cc_10 / 10 * 8
ZitatRayMan Pro 2.3 beta
You are obviously not using a recent version. Please fill the form at the rayman main page and obtain a recent copy. If the error persists please delete all content from the air temperature, vapor pressure and relative humidity boxes and only type numbers there (without decimals for a start) to avoid conversion issues through strange characters (e.g. whitespaces that got there through copying some numbers).
I don't know what presumptions that page actually does or does not consider, but for the second row, with an air temp of 15°C and a mean radiant temperature of 18°C, -2.18 (class "cool") appears way too low to me. Also for the last row I'd expect something indicating some heat load. 0.79, however, only is in the lower range of the class "slightly warm"…
the error message indicates a conversion problem. The program fails to convert text to a decimal number. This could be caused by a problem with the characterset of the operating system. Please see the solution to this post: RE: "108?7 ist kein gültiger Gleitkommawert", location.
The RayMan version 20170310 is deprecated by the way. Please download the latest version.
thanks for providing this information. It appears like this combination of input parameters confuses the radiation calculations (they are all set to the fail value of -9999). This seems to be a bug. If you have a version of RayMan that works on this combination go on using that one until the latest version is fixed.
maybe you got some corrupted currentsession.ini file? In the same folder as the .exe, there must be a file "currensession.ini". It does store the previous settings and is safe to remove. Please delete that file and retry.
that sounds strange. Are you sure you are on the latest version available online? Could you maybe re-download and replace your copy with the downloaded one? Does the issue persist with that one?
RayMan does not consider water bodies, sorry. You could, however, reduce air temperature and increase humidity while running points close to water bodies manually.
if SkyHelios is throwing a System.NullReferenceException at startup with the source "ClimateSkyModel.MogreD.MogreRoot.InitRoot()", then your System might be lacking the Microsoft DirectX End-User Runtimes.
I was asked by a Chinese colleague if it was possible to run RayMan for different locations automatically, e.g. for some climate model grid.
The answer is: In the pro version you can, but with limitation. It is possible to specify not only date and time, but also latitude, longitude and height in your meteorological input file to calculate for a spatial grid. e.g.:
Please make sure, your coordinates are in decimal degrees and the elevation is an integer (without decimals).
The limitation is, that you won't be able to use different obstacle files or fisheye images for horizon limitation. If you are fine with that, go ahead!