IES-VE User Forum

There is a bug in IESVE 6.1.0 in modelIT. This one is quite extreme and hope IES issues a hotfix ASAP.

In ModelIT, if you try to save your project by clicking on the toolbar button "Save Project" and instead mistakenly click on "Import gbXML file" which is right next to it, no matter what you press next (including "Cancel") it will DELETE your entire model geometry, SAVE the changes, and remove any possibility for undo. It's basically a kill switch on your model with no possibility of recovery!

A look at the filesize of the *.mit file confirms this.

Again, this will happen even if you press "cancel" once the "Import gbXML file" window opens. This is particularly dangerous as the "Import gbXML file" is located right next to the "Save project" button and you might (as I did) hit it by mistake while actually just trying to save. IESVE 6.0.6 didn't do this, if you hit "cancel" in 6.0.6 it just updates the adjacencies, so this is just in IESVE 6.1.0.

At least I found a quick way of deleting all my zones, might this be a "new feature" ?

Hi Joseph,

We picked up on this behaviour this week as well. Sorry if you lost a lot of work!

We will definitely have this one fixed for the next release of <VE> (ref number is 0032483 if you have any further queries related to this).

Phil

The same thing happened to me last week. I had already completed my Part L calculation and was just altering a rooflight in modelIt. I clicked the import gbXML button by mistake, chose cancel and lost my model. It also removed all my templates, so I lost all my constructions and systems info. Luckily I had backed up a copy earlier in the week, so only lost a days work, but still a pain when working to a deadline.

Glad to hear you had a backup copy, I know it's pessimistic but I ensure I keep backups of all my work because you never know when something like this could happen (and not just when using <VE>!).

The <VE> 6.1.0.1 hotfix is now released on our website and links to the patch (to update existing 6.1.0 installations) will be posted shortly. This is one of the issues fixed in the hotfix.

Phil