Giacomo Devoto

Totally agree with Tom. Consolidating rectangles into polygons would simplify reports too. In many cases I need to quickly calculate the surface using rectangles and polygons. Also selecting with magic wand in some cases I forget to select either the poligons or the rectangles when I usually need to select both types...

Grouping messy. When you create it you have to make sure to put it in the class of the objects you are grouping... I might put it in the None class too. When I'm in a hurry I screw it up because it ends up in an unexpected class and it screws up the visibility on viewports. Can't groups just exist without a class? I feel like the only function of groups is keeping stuff together and to isolate it when editing it... and I don't think it needs to have a particular class

Yes you could put slabs in dedicated design layers, which complicates things... But if you do the same for every element it quickly becomes chaotic. As a "power user" I could navigate it using filters but others in my firm will struggle

I spend a lot of time sending objects to front and to back. For example slab class should always be to the bottom, text and labels always on top, furniture somewhere in between. You could implement it simply by assigning a priority number to each class.

In my case what solved the issue was creating a new renderworks style resource from scratch instead of using the default one.

I would like to see energos parameters in data visualization such as include in calculations and boundary type. Right now it is tedious to verify which objects are calculated and which are not, you have to manually select objects and check the OIP.

bump. any news or other workarounds yet?