Object 2D Projection - Cut in plan view

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 03:52 AM
Im trying to think of an 'easy' way to make a 2D plan projection of an object but with a controllable plan cut height ..
A simple example of the use would be to generate the correct plan view of an angled column on each storey as it rises through a building. I know how to control visibility by story but what i cannot work out is how to cut an object at a specific height rather than from an infinite point above to generate the plan view as PROJECT2 does
AFAIK there is no way of doing this as a projection of the 3D model? (such as PROJECT2)
The example of a column would be relatively simple to script in 2D using lines etc, but I am intending to use this to generate accurate plan views of some more complex elements (e.g a curved truss) spaning across multiple floors where we want the plan view to change as you move through it
I have been thinking about this on and off for a couple of days but at this point I really have no idea how to do it.
Any hints?


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 04:47 AM
This specific view could be pasted into the 2D view of your object....
The process involves placing the object into the plan, cutting it with the cutting planes and using the resultant view as the symbol....
Fragment views in the 2D script could refer to several different plane cuts for parametric variety.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 05:46 AM

my only problem with this is it is really restricted for use on 'static' objects ... if for example you changed the angle of the column the fragments for the 2D symbol would need to be regenerated manually?
whilst out to lunch i had an idea ... not sure if it will work but the principle is:
1. The object can ask if it is being viewed in plan, section/elevation or 3D
2. The object can request its height relative to project origin and storeys
3. An object parameter can be used to set the plan cut height above a nominal floor level
The object will determine if it is being viewed in plan and turn on a 3D CUTPLANE. The 3D script will use the objects height relative to the project orgin or storey, along with parameter 3 to determine the height to set a CUTPLANE to remove the part of the object above the floor cut level.
The 2D script then uses PROJECT2 to display the trimmed object in the floor plan. Another CUTPLANE could be used to remove elements below the floor level if needed .. just showing the 'slice' of the object from 0-1500mm above floor level for example.
If the object is being viewed in a Section/Elevation or 3D window the CUTPLANEs are turned off and you see the entire object
This could be done with a tiny subroutine dropped in at the start of any 3D script? Now that i think about it this sounds too straight forward. I wont have a chance to look at this for a few days ... anyone think of any flaws in this idea?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 05:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 06:35 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 07:42 AM
Attached is a quick test object using a cone which can be angled and a cut height above floor level set. I also threw in some text to show height of the current cut relative to the objects origin.
At first my 2D script was a basic PROJECT2 line and it was behaving the way you describe .. it would only update the plan view if you opened the object and resaved it.
I then added the text to check it was requesting the elevations correctly (requesting the objects Home Story Elevation, Current Story Elevation and objects elevation relative to its home story) ... and it started working?!
I assumed Archicad ran through all the objects scripts each time a view was rebuilt but this seems to indicate it wasnt? Not sure why these requests in the 2D script would trigger it either ..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 08:40 AM
There was a ArchiCAD version (4.55? 5.0?) which updated the zone stamps automatically, when you changed a wall. This was such a performance killer, that we had to hide them or to change to polygonal/manual. Awul. Then we got the manual update.
Back to your object: You should be aware, that your object will not work correct on ghost stories: The objects laying on a ghost story do get the same level informations as the current sory. AFAIR this should be fixed in any of the next versions. There is no work around for this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 09:39 AM
F. wrote:Hahah, I added
ArchiCAD tries to calculate the model most effective. It does not see, that it's necessary to calculate a new 2D-view, if there are not used some level relevated globals in the 2d-skript.
dummyvar = GLOB_CSTORY_ELEV
at the beginning of the 2D script and it works perfect. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-20 09:44 AM
Hu. Buenos Aires. 5:40 am. Earlybird or tons of work?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2018-10-05 11:18 AM
The issue here I think is that by using a cutplane to cut the object, then projecting that cut face, you are technically not cutting the object and you only see faces?
Ling.
AC22-28 AUS 3110 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win11 | R5 2600 | 16GB | GTX1660 |