EN
For the Norwegian (and other scandinavian/cold countries) it would be handy to have the ability to assign outside and inside areas of a roof.
We tend to have a lot of insulation, but there is no need for insulation on the outside. If the roof tool had an extra feature where you could draw a fill/area to designate a separate zone for a separate composite, the roof tool would be much more useful. As it is, using two separate roof objects is suboptimal.
It would be useful if element surfaces were linked to design options. This would be especially helpful for apartment block designs, as the Hotlinked units are the same across the various floors, expect the exterior cladding typically changes.
Currently you have to create whole new walls and assign these to different options. This becomes cumbersome when changing windows and doors, and is confusing for less experienced users.
Please allow the creation of full bullnose or fillet edges for slabs. Currently, the Morph tool is very limited for oval or rounded shapes — it is extremely time-consuming to adjust and often impractical for precise tabletop forms. Custom profiles do not even work with slabs, which removes another potential solution.
The Slab tool already offers edge types, but only straight or angled edges. It is unclear why a simple bullnose option is unavailable, while Morphs can achieve it.
This feature would greatly improve workflow efficiency and modeling accuracy for architects. For reference, I have attached an inspiration photo showing the desired edge types. As you can see, there is many.. all we want is simple bullnose option the least.
Thank you for your time and considerations and helping us!
Is there an option to change text in the text tool from lowercase to uppercase and vv. Perhaps as an option in the "Favorites" menu.
I am attaching an idea for a simple Point Clouds palette, which aims to streamline and improve work with point clouds. I think it is such a basis for the work to be meaningful. I am submitting a proposal for the entire palette, because adding functions one by one does not make sense in this case. You can find the description of the functions directly in the image.
Of course, this is a rough idea that does not have all the connections to the AC environment, and it would certainly be modified by the developers, but it will hopefully serve to give an idea of what is missing when working with clouds in AC.
I know there is BIMmTool, but it is only a third-party plugin, which, moreover, in the Lite version, is not useful for professional work.
BIMcloud SaaS tenants are assigned to a Google Cloud Platform region based on country of purchase, with no option to select or request a different region. Graphisoft's own documentation acknowledges that latency directly impacts Teamwork performance, particularly Send & Receive operations, and directs users to verify their latency using GCPing.com before committing to SaaS. Reference:
We followed that recommendation. The results, measured from Costa Rica using GCPing.com, show the following:
São Paulo (southamerica-east1), which is the assigned region for Costa Rica: 180ms South Carolina (us-east1), the best performing region from our location: 85ms North Virginia (us-east4): 93ms Dallas (us-south1): 108ms
São Paulo is not only the worst performing region in the Americas from Costa Rica, it ranks on par with European cities including London, Madrid, Paris, and Belgium. It performs worse than every US region by a significant margin, and it is geographically further from Costa Rica than multiple US options.
Graphisoft's own network requirements documentation states that slow round-trips significantly affect operations requiring multiple packet exchanges between client and server, specifically naming Send & Receive. At 180ms base latency, every Teamwork operation accumulates this penalty across multiple round-trips, making daily Teamwork use genuinely impractical.
Notably, Graphisoft does not publish a maximum acceptable latency threshold anywhere in the connection test documentation. Users are directed to check their latency without being given a pass or fail benchmark. This means firms in affected regions can unknowingly purchase Collaborate subscriptions, complete the recommended connection test, and still have no basis to evaluate whether their assigned region is acceptable.
The request has two parts.
First, publish a clear maximum acceptable latency threshold in the connection test documentation so that firms can make an informed purchasing decision before committing to a subscription.
Second, allow tenant region selection at purchase, or at minimum allow firms to request reassignment to the lowest-latency available region. Locking tenant assignment to country of purchase without any recourse is not acceptable when the assigned region demonstrably fails to support the product's core workflow.
This affects all of Central America and likely other Latin American countries facing similar routing. It is a verifiable, measurable infrastructure gap that makes a paid feature non-functional for an entire region, and it directly contradicts the product promise of seamless cloud collaboration regardless of location.
The Edit Color window is very dated. It needs the ability to input hex color codes and should probably have an eyedropper as well.
If I currently want to colour match something, I have to use the eyedropper in Photoshop and then break down the RGB values to input into Archicad.
I would suggest copying something like the Unreal Engine color picker which works well:
Rhino's Select Color window can also be used for reference:
Many firms use the curtain wall tool to model storefronts. These generally have a corner post rather than a diagonal frame.
When using the polygon method to create a Curtain Wall which turns a corner, graphically in 2D and the 3D the representation is not what you expect. This occurs at both the top and bottom where the boundary frame meets the corner frame and by default cuts at 45 degrees. The workaround is extensive.
You have to do this one by one in Edit mode: Select one of the affected boundary frames and navigate to Cutting Planes and change the Cutting Plane from Automatic to Manual. This will change the cut end to 90 degrees. If it changes the wrong end, you have to undo and change Cutting at Top to Cutting at Bottom or vice versa. After this you still have to stretch the elements to the edge of the post - which only has a node in the center, so guidelines are needed to do this accurately.
You should be given the option kn the Scheme Settings to make the default cut 90 degrees - or even better - have a "post" option instead of a corner frame, with an associated 90 degree cut.
Nothing here yet. Try changing your filter criteria!
