ARCHICAD 20 Update 6005 Released

[Csaba Kezer]

Hi All,


Today we have started to publicly release the next Update of ARCHICAD 20. This Update has been available as a preview version already and based on the feedback of the preview period we have slightly modified the Manager component of the server update packages.

The Update is already available for the AUS, AUT, GER, INT, NZE, UKI and USA versions, and will be followed by the rest of the language versions as soon as they pass our Quality Control. You can read the Release Notes and download the packages from our download sites:
- ARCHICAD 20 Update 6005 & BIM Server 20 Update 6022
- BIMcloud Manager 20 Update 6022 & BIMcloud Server/Delta Cache 20 Update 6006

BIMcloud Multiversion compatibility
This ARCHICAD 20 6005 Update along with the ARCHICAD 19 9001 Update enables ARCHICAD 19 and 20 to be compatible with the Multiversion BIMcloud, introduced with version 21.

Grasshopper Connection Add-On compatibility
With this new Update of ARCHICAD 20 we are introducing changes that needs a new, compatible Grasshopper-ARCHICAD 20 Live Connection as well. You can download this new Add-On from our
Rhino-Grasshopper download site. Beware that this new Grasshopper Add-On is only compatible with the new 6005 ARCHICAD Update and not with the previous ones.

Best regards,

[Barry Kelly]

garimdias wrote:
Any idea why this is happening?? [/img]

Why what is happening?

Barry.

[Ben Cohen]

Hi Csaba

Barry has hit the nail on the head with both points

1. Yes, as Barry said, Hotfix 5 is not the time to introduce this sort of stuff!! Why now? This change had a big impact on our 60+ users and we have had to roll back to 5025 - hours of wasted time. There was no indication in the release notes that this change was included in 6005. I can't remember a previous hotfix in the 10 years I have been a BIM manager, where a hotfix has made a significant change like this........... Because it should not happen!!
2. The 5025 behaviour is perfect. If an element continues through the extent of the section - no line. If an element starts or finishes on the extent, you get a line.

Csaba wrote:
"So from this point the software works in a more logical way than before"

how so?
What would be logical, would be for migrated projects to continue to display as per previous versions. If this can only be done when upgrading to v21, then so be it.

[Ben Cohen]

Barry wrote:
Fortunately for me it looks as if my template is set to use 'Uncut, contours, so I should see no change.
I don't particularly like using that as it forces lines to all boundaries, but I think it is because we had problems with it many years ago, or maybe it is because this option never existed in the early days and it is the default that just crept in.
I can't really remember now.
I know we have had trouble with the cut surface of the slab disappearing a few versions ago that got fixed.
If we really don’t want a line on the boundary then we will go over it with a white line.
Barry.

This is exactly why we have always used this option. It prevents the user having to place white lines on the boundaries.
It had been working perfectly for years

[Erwin Edel]

Before I go ahead and install this: do I understand correctly that if I have an elevation that displays down to -100 mm below project zero and I have a terrain slab on -100 mm, it will not show any lines unless I use the Boundary Display option or extend my elevation down to -101 mm (which is stupid)?

[Barry Kelly]

Erwin wrote:
Before I go ahead and install this: do I understand correctly that if I have an elevation that displays down to -100 mm below project zero and I have a terrain slab on -100 mm, it will not show any lines unless I use the Boundary Display option or extend my elevation down to -101 mm (which is stupid)?

Correct.
Although it may be a bit hit and miss.
I have discovered an existing file where the elevations are fine (with the boundary contour set to 'No contours'), but if I copy and paste the model and elevation to a new file (based on exactly the same template) then the contours disappear.

Just discovered that it is because the 'Legacy' for intersection and surface methods was on in the old file and not my new template.

Barry.

[Erwin Edel]

Thanks for clearing that up Barry. I do not use legacy settings.

I've already been struggling with my terrain composite, as it uses the cutline pen that is set for the building material (non composite) setting currently, which I would say is also a bug, but at least it can be fixed to behave.

I have tried the boundary settings in the past, but this leads to unwanted behaviour when you want to partially show existing neighbouring buildings, where they also get a thick line where I cut them off.

This 'fix' is something I do not understand. As pointed out, it was working, now it is broken.

Please unfix it.

[Erwin Edel]

Just tested this on a workstation we don't use as often. Upgraded there and indeed if you use the option no boundary, any elements that are on the edge of the section/elevation do no get a line. So my example of having terrain show as a single line no longer works.

To be clear, this is a slab that is 'cut' by the elevation marker, so in my opinion, it is valid to see this cutline. If it were uncut, I would indeed not wish to see it, which is what the option suggests: no uncut contours. Just because I do not cut the whole element, but only the very boundary, doesn't mean it shouldn't display.

After reading the patch notes, I do think I will update and just live with either 2D line work for the terrain and such or masking out unwanted uncut lines with the option to show uncut line boundaries. There are some bugfixes that would benefit me.

But please, please and I've set this out through our reseller too, allow for cut element lines that are on the boundary to show somehow.

[Anonymous]

I'm sure there are lots of additional users out there who are equally irrate.

GS should NEVER make such a global change without. Lots of people are now trying to figure out a work around.

So, how do I roll back to Hotfix 5025?

[Ben Cohen]

Csaba wrote:
I will discuss this with our Product Development team and get back to you when I have some news.
Csaba

Hi Csaba

Any news on this?
We currently have our BIM server on 6005 and our clients rolled back to 5025. Which we would rather not do.
Wondering what to do next.....

[Anonymous]

Like Erwin said, "...allow for cut element lines that are on the boundary to show somehow."

I don't have a project with a stair right now, so I'm not going to update to 21.

We've worked hard in our firm to eliminate 2d line work, but I'm not sure how Graphisoft suggests we proceed.

I've attached two images from a layout book. The version in 20 shows the floor line. 21 doesnot. But this seems so basic, how do I get the perimeter surfaces to display AS SINGLE LINES with the current software?