Wishlist

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.

Hello , 

Instead of the buggy " zone linked elements " function inside ArchiCAD, which automatically detects elements placed inside or at the zone boundaries, it would be very nice to have manual link possibilities , 

a big slab that covers multiple zones could be linked to them all, 

i can choose to which zone i want to link a wall , or a dorr, manually , 

When dimensioning sections for formwork drawings, dimensions for wallholes do not associate and any change in doors / windows will not update dimensions, which leads to errors if sections are not monitored constantly. For a small three apartment building I have more than 20 sections per floor and it's really hard to keep up with all the dimensions that are not updating automatically.

This is a section that goes through a garage door. The 12,5 cm dimension and -0,625 elevation dimension will not update if I change height of the door. Wallholes should have automatic hotspots - when you place dimensions, it should be a circle on the hotspot, not a square.

a way to batch convert 2D fills to 3D objects (like slabs, terrain or morphs) to make the creation of the surrounding area quick and easy.

ways this could be done;

multiple elements to be converted through favorites

batch selection with magic wand tool

extrude fills to morphs

Sunshades should be hidden in some views, this should be achived by mvo like other window components, for consistency and efficiency 

Currently in Archicad, Expression based properties are unavailable to elements contained in hotlinks (they show up as "---" values in schedules and are unavailable for evaluation in the Property Manager. This is a serious flaw and undermines many of the recommended workflows in housing projects, for example. We need to be able to consistently use expression based properties on all elements.

In our office, we make modules out of recurring apartment types, to streamline modelling and ensure consistency across the project. To not be able to use expression based properties in schedules for any of these apartments makes either modules or properties completely useless. 

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.

When attempting to select one from amongst a number of overlapping elements in plan view (such as fills, slabs, roofs, library objects etc), hitting the <Tab> key while the pointer hovers above them, will normally cycle between and highlight each element in turn beneath the pointer, without the need to chance exactly on a node or hotspot, and the user can just keep hitting <tab> until the correct element is selected. 

However when the overlapping elements are large enough to extend beyond the current zoom in the plan view window, especially when there are complex elements (such as site meshes) in the mix, ArchiCAD often takes a longer time to identify the overlapping elements, and the Tab-between-elements behaviour appears to time out, leaving the fallback MS Windows OS Tab-between-fields behavior to kick in (apparently this issue does not arise on Mac) 

So, instead of tabbing between elements in the normal way, when any of the overlapping elements are too complex or large to be detected in time, suddenly, hitting Tab causes the focus to switch away from the elements under the mouse pointer, to the feilds in the Tracker dialog nearby.  

Currently, the onlywork around I have found is to ensure Tracker is not enabled.

I reported this to Central Innovation, my local reseller, but they are adament that Graphisoft has told them that this irritating and intermittent behaviour is intended, or 'by design'. 

In other words, 'by design', it affects only Windows computers, and 'by design' it affects only views where the overlapping elements are large or complex, and 'by design' it only occurs when Tracker is enabled.

My only scope for having the bug corrected, they told me, is to post it as a 'wish'.

To me, demoting bugs to 'wishes' rather than owning up to and addressing them, is just more evidence of the Graphisoft corporate cash-grab decline - however I am now posting it here.

It would be nice if the context menu would be extended with an option to make a design option the default with 1 click. In the picture below all red elements are in an other design option then what is the default. Adding this functionality would make it faster to add new elements to the right option instantly.

Polylines and Fills are simple but powerful drafting tools in Archicad. However, they remain limited in how they can contribute to data workflows. With a few small improvements, they could become valuable tools for quantity takeoffs, annotations, and integration into BIM data reports.

Proposed improvements:

• Allow user-defined IDs for Polylines (like Fills already have), to make them listable in schedules.

• Enable assignment of custom Properties (from Property Manager) to both Polylines and Fills.

• Include basic dimensional data (length, perimeter, area) directly as native schedule fields.

• Allow Polylines and Fills to be read from Section and Elevation views, not just Floor Plans,
  with a “source view” parameter to identify where they were drawn from and make them filterable.

Why this is useful:

• Boosts modeling speed with simple 2D tools that feed into data and quantity workflows.

• Enables “hybrid” workflows where schematic elements can still be tracked and quantified.

• Great for compiling supplementary data for construction estimates, where not every element needs to be modeled in 3D.

• Gives more control and traceability for annotations, graphical conventions, and custom visual logic.

Bonus benefit:
Sometimes the simplest tools are the fastest. Enhancing these basic elements would empower users to speed up many parts of the process—without relying on heavier modeling just to get quantities out.

Hi all,

When you change the Home Storey of a wall, the doors and windows associated with it should adjust their Anchor too if set to a reference a Storey.

eg. You have a wall linked GF-FF with a door / window in it anchored to GF. Changing the Home Storey of the wall to FF-SF, the door / window remains anchored to GF and hence is now floating in space. Unintuitive. If you so happen to have duplicated an existing wall before changing the Home Storey, you now have identical overlapping doors / windows which you might not even notice.

The current Workaround it to copy / cut and paste the wall in the Floorplan.

Ling.

At present, a demolished window or door leaves no trace in the proposed view, but in reality it needs to be infilled with new construction (which may differ from the make up of the original wall).

Using a renovation filter to 'show' the removed windows would mean showing everything else too, and perhaps in an undesirable representation.

At present we insert a 'New' empty opening in place of the Demolished element, in order to have a hole that can be filled with a new wall.  This works ok, but seems like a workaround rather than a reflection of reality, more steps than should be necessary, requires workarounds in schedules so the 'new' openings don't show, and is non-associative to the dimensions and position of the original window, should they need to be amended.

Please could there be a setting to allow demolished opening objects to remain 'visible' but replaced with the Empty Opening? 

Because drawings supplied by most manufactures and surveyors depict curves using hundreds of short line segments, we need a way to convert these back into simple curved line segments for much easier & cleaner manipulation / translation 

To this end, we need a curve-fitting algorithm that can detect and convert line segments back into original circles & ellipses wherever applicable, or otherwise to polylines with user defined-segmentation/resolution (essential for managing mesh contour complexity), or to smooth splines

Small gaps between line segments (e.g. from export translation rounding errors) that would prevent successful space clicking of lines (for area fills etc) should be detected and filled by extending curved or straight-line segments, depending on the best fit   

For example, manufacturers imported detailed window profiles currently often cannot be space-clicked successfully due to tiny misalignments between imported line segments.  Space clicking is needed if you want to replace lines with fills.  And segmentation removal is necessary to find the origins of imported circles - etc

Because site meshes are typically the most complex entities in an ArchiCAD project, by a very large margin (unless you live in Holland of course), SEO operations on them are quite expensive computationally, and successive operations rapidly slow regeneration of cross sections and elevations while editing, on even the fastest machines.

Bewilderingly, meshes STILL don't support materials priority intersections despite this fact, and despite the fact that every single project has foundations that need to cut into the site mesh. So this is not an edge case.

On sloping sites, foundations and siteworks are inherently very complex, and site meshes are inherently very complex even before SEOs are applied, meaning a project of any scale rapidly becomes unworkable, even on top end hardware, as the number of SEOs required keeps expanding to follow the progression of design & documentation processes. Hundreds of objects typically need to interact with the ground.

Highly embarrassing spending $10K on the best PC that money will buy, and half that again on (increasingly) the second-best BIM software that money will buy, to have even the normal requirements and complexities of depicting the actual construction of buildings on actual sites exceed the capabilities of the system, without time wasting and laborious manual workarounds. 

PLEASE give some serious love to meshes, as the highest priority. The current functionality is literally decades old, and is so limited that it is completely beyond justification.

Unless and until there is some way found to massively speed up SEO calculations, please at the very least enable materials priority for meshes

When selecting an object that has been involved in SEO, there is a small useful dynamic feedback icon allowing the user to trace exactly what interactions the object is involved in. 

Because interaction by means other than SEO can also cause unexpected alterations to object shapes, those things should also be listed when the icon is clicked, to help with model troubleshooting.

For example, the trimmed off portion of a wall may not be visible, but that trimmed off portion can still cut chunks our of things with lower materials priority.  Objects on hidden layers (even on other stories) but with the same intersection priority can cause weird unintended 'clean up effects', etc.

When an interacting item in the list is selected, a ghost representation of that object should appear, to help with identification and location, even if not otherwise visible in the current view.  In fact, this behavior should apply to objects involved in SEO interactions as well. 

Where there are many interacting objects in the list, it may even be helpful to allow the user to toggle individual ghosts on and off, so that an exact visual match for the shape of the unexpected distortion can be found - which is easier with less visual clutter from displaying the outlines of too many other objects at a time

In particular 

• Materials priority interaction with other elements
• Intersection priority interaction with other elements in currently displayed layer combination
• Openings (these can sometimes do seemingly weird things when the opening's nodes are not in view)

This feature could save many wasted troubleshooting hours.  It could be toggled on or off if there is a performance impact.

Often when you start a project you don't know what elevation (level) you will want project zero to be at.  So you build your mesh to AHD & set your stories at what may be close to their final height, but the time often comes where you need to adjust the stories relative to the mesh.  To keep the project zero story at zero you need to raise or lower the mesh.  This however throws out the heights of the mesh relative to AHD.  It would be great if you could just drag the stories up or down relative to the mesh, without losing project zero.

Currently, when creating contours in a mesh from the linework on a surveyor's supplied dwg file, under certain circumstances space clicking the surveyor's line can create duplicate nodes or entire duplicate contours, that co-exist exactly in 3D space but are otherwise undetectable to the eye but that trigger otherwise inexplicable behaviours.

I have reported this as a bug, but was told this is just a 'limitation of the tool' (which I think is semantics), and that any fix needed to be submitted as a wish.

Symptoms of duplicate mesh nodes can include:

• Manually dragging a node on a mesh contour line reveals another contour line beneath.
• Space clicking a 2D line with mesh selected and mesh tool active may appear initially fail to create a contour, but trying again causes a mesh contour line to appear that extends only part way along before looping back to the start.

These issues can arise even after confirming there are no duplicate lines or gaps in the source linework.  Possibly as a function of mesh complexity or multiple SEOs in the mesh, possibly as a result of rounding errors if the project contains far distant objects, and possibly exacerbated by lagging dynamic feedback resulting in the user clicking based on out of date information displaying for current mouse position for a second too long.

Until meshes are upgraded to allow for concavities or genuinely vertical surfaces, where contours that are coincident in plan would make sense (vertical banks etc), it should not be possible for more than one node or contour line to occupy a given plan position.

Perhaps a mesh clean-up tool or function could be added to remove duplicate mesh nodes?

Please fix the issue of JPEG exporting. 

It would be useful to manage image resolution. Although there is option "Maximum quality" the final image resolution depends on the actual zoom on the layout while exporting.

Also JPEG export isn't related to the Layout but to the entire screen. For example when I have other images and objects outside (beside) the Layout, they are exported as well into the final image. Is it possible to limit the export only on the Layout and not its surroundings?

Thank you.

Jakub

Hi everyone again,

I've posted a tread but community suggests me to repost it with a referal at only one wish.

So here i am again, I’ve seen a lot of wishes here—some are totally useful, others maybe less so— I’m wondering : aren’t you tired of modeling plinths with beams or finishes with other walls, just because Graphisoft left wall accessories behind? And if you try to take off surfaces or measure lengths from accessories, it’s absolutely impossible to get the right informations. We supposed to work bim right? Wouldn’t it be great to have a finish tool, like the railing tool, but maybe with advanced features—directly linked to walls and their openings?

A tool like that could be more greatful then other new features that are now implemented.

Lets make Archicad great again!

Victor,