Crashy IES 2017.2.0.0

[bootsam]

Dancing grips, snaps that jump and a crashy habit. This iteration sucks. C'mon IES, spend some of that enormous subscription fee on fixing your software please. Thanks.

Oh and while your at it, make sure it writes a temp file to backup too. Or at least one thats more recent than 2 hrs ago. Yes I have autosave at 15mins.

[bootsam]

I'll add 2017.3.0.0 to that list too. 'resource not available' then pow gone. This version is so unstable I have to manually save every 5mins. Autosave is irrelevant unless you close the place windows dialogue. If you do not all work whilst 'place window' dialogue is open is lost. Forever.

DXF has no labels on everything, please IES post something to resolve these. Thanks.

[bootsam]

[Terence]

Hi Boots,

Sorry to read that you are having problems. Have you contacted the support team directly regarding the crashing? Looking through our systems (support & development) we haven't had reports of this kind coming into support, and I'm afraid we can only deal with problems that get reported. If you have a recipe/list of steps (example below) that produces a crash then please send them across to support@iesve.com and we will confirm the issue and log it with our developers for further investigation.

I will pass on your request for more flexible autosave options but please feel free to go directly to feedback@iesve.com, you can add the reasons why this would help you if you wish.

Example recipe

- Using VE 2017 Feature Pack 3
- Select File>New Project, give it the name Training1
- Save to C:\VEProjects
- In ModelIT create 6 rooms
- Go into Building Template Manager, copy the default template, rename as “Open Office”
- For Open Office select NCM Building Type Office and activity Open Office
- Save model
- Assign Open Office template to your room
- Run compliance simulation
- Actual Building simulation completes, Notional Building is generated
- VE crashes and exits

[bootsam]

Thats the thing Terence, there is no recipe for disaster. I can be drawing rooms, one after the other and then all modelit graphics disappear leaving a blank workscreen (all other parts of ies still visible, ie menus etc) and a dialogue box pops up that states 'Resource Not Available'. Or I could be placing windows, one after the other and same happens. I'm perturbed that youve not had any other reports. As this alludes to me being the problem, or my PC. Ive never encountered these issues previously to .2.0.0. My IES PC is a standalone unit thats bang up to date and fault free.

I can work around it manually saving, I am wondering if the autosave is the issue as it is periodic and I may time the intervals to check this. I'll report back here.

The dxf label thing, well I'd love to know what exactly this means as I may be able to remedy this, as I myself create the dxf's from the architects 'GAs'. Which are themselves produced from a Revit model. Albeit a very poor one with more holes than Chedder Gorge and misalignments everywhere. Which I'd have thought was more difficult in a 3d model than doing it right, but heyho. However it is their GA which forms the dxf, so if it was something intrinsic to the GA, this would not surprise me. As their cad skills are frankly appalling. Ive cut my tracing from their GA and created a dxf which cannot inherit any of their shenanigans for my next floor. If this floor completes without issue, then we can blame the architects and I shall retract my complaint sheepishly.

[JLuckett]

Hey guys, thought I would drop my perspective on here dealing with this issue.
I have experienced this error to and sent an inqueiry into support about 1-2 weeks ago and they reported they are looking into the resource error trying to figure out the exact functionality that causing it and trying to debug it. I believe it has to do with modelIT interface while a dxf file is attached from my experience (some report its 12 mins after attaching but for me it has been more random) so when I am using an attached dxf I make sure to manually save periodically to minimize losses.
I found a workaround for the labels not appearing when attaching dxf file: open the dxf in autocad, then right click room label text to select all instances, and use the EXPLODE function, resave file as dxf, attach in IES and you should have the text. Its been working for me so let me know if you can get it to work also.
cheers,
Jackson

[Terence]

Thanks for the info Jackson.

Is it always a resource error before the software shuts down? Would be interested to test this out if you can send a CAB file and a DXF through http://upload.iesve.com
?

For the labels i've heard you can lose them if the rendering (ModelIT drop down > Rendering) is intermediate or advanced. I will get the Known issues thread updated with this.

[bootsam]

Thanks for that JL. That has helped me out.

I notice it a lot when panning with mouse, ie using wheel pressed to hold and pan, and when zooming into areas. Fortunately if you save often, you will not lose much. Using the bottom scroll bar helps but that too has caused some crashes.

[Terence]

We've updated the VE 2017 known issues thread for the DXF labels and also the random crashing in ModelIT. In both cases the workaround is to set rendering option found in the ModelIT drop down menu from Intermediate to Basic. This will be fixed in VE 2018.

[jerry]

Crashing is a normal part of daily life for VE users, no matter what the version. Yes, it sucks, and after decades of continuous development, it really shouldn't still be happening.
Come on IES, sort it out.