A holistic microclimate model

Release Notes

Moving on from V3.1

The development of ENVI-met V4 took about 8 years, which gives you an impression on how much has been changed. Moreover, the very deep roots of ENVI-met are at the beginning of the 1990ies with the shadow casting software SHADOW and in 1996 with the first 1D version ENVI-met-1. Needlessly to say, that not only the computing possibilities have changed a lot, but also a the way programs are coded and data is handled have experience some fundamental changes. So, ENVI-met V4 is not only a new version with new features, it also got updated in almost all aspects of computer programming deep in its roots.

ENVI-met is used in over 130 countries, from Europe to the tropics down to Australia and back up to Russia. Can you image how many never-though-of constellations of model analysis appear in all this different zones of the world? It is our aim to make ENVI-met available to any user from wherever she or he comes and whatever issue (within the scope of ENVI-met) is addressed. And, still let it run on a standard computer from your local hardware dealer. For us, that makes the heart of an holistic model such as ENVI-met and the thrill to make it actually happen keeps us running.

Of course, we need your feedback on issues occuring when using ENVI-met. We do not talk about the little ones that are scary, but often can be solved quickly. For now, we ask for input on fundamental flaws that appear. To do so, please use our forum at http://www.envi-met.info/envibbv3/ and don't write e-mails to us. The forum is the only option for you and us to handle issues in a consistent way and to avoid asking the same questions over and over again.

As the documentation system is not ready yet, in the next sections you will find some short comments on different aspect of moving from V3.1 to V4.

General Software Issues and Pending items (Version V4.0 Summer16)

  • When opening an old .IN file in SPACES, check if ALL settings, especially Latitude and Longitude of location are converted properly. There are different .IN files out there and it is not possible to identify which one is which.
  • .SIM files are going to be re-worked
  • Using a DEM is still experimental and can lead to problems depending on the complexity of the model domain

Using V3.1 Area Input files

You cannot use V3.1 .IN files in ENVI-met V4. You need to open them in SPACES (the Editor) before, check them and save them in the new .INX format. No items should be lost in this operation. Users of early ENVI-met V4 Beta versions can transform their .IN/.IN3 files in the same way.

Using V3.1 Configuration files

No way. You need to create new ones, too much have been changed. With the new ConfigWizard, that should be quick and easy.

Using V3.1 User Database files

If you have added user defined items in V3.1 database, you need to transfer them by hand into the V4 User database. As there were not too many databases in V3, this should be quick.

Using [ALIAS]

The concept of alias has been dropped and was replaced by a proper project management system.

Using Batch files

V4 does not support batch files. There will be a new replacement later considering also recent aspects of Cloud Computing, but not for now.

3D Graphics

ENVI-met V4 uses 3D in many applications from SPACES over ALBERO to LEONARDO. If you find the graphics performance bad or your display is destroyed or corrupted, you should check if you have installed the latest graphics card driver and that it supports OpenGL. The rendering of the 3D environment in ENVI-met is not done by the application, but by your graphics card.

This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information