[Frage] Question - Intersection Points node and surfaces/places/breps [Gelöst]

Schlagworte:
DGeorgiev
DGeorgiev
07.06.2022 - 11:46 *

Greetings everyone,

I have a question regarding how the “IntersectionPoint” node works. Does is work with planes and surfaces? If not, are there any alternatives?
Also is there a way to reduce the number of points when intersecting with sphere/oval objects, as it would probably generate numerous points, causing the script to crash?

Scenario:
I am trying to make a script that generates a terrain model using slabs using the sloped-surface terrain from allplan. So as a starting point I have a random shaped surface, which then is sliced using planes and finally take out their intersection points. Using the points slabs are created, starting from the highest point, whose shape/area is afterwards substracted from the one below (making the terrain easier to model).
I have tried with different combination of nodes, but the “IntersectionPoints” node seems to only work with linear objects (polyline, lines, spline etc.). I have attached below a basic script just as a reference point.

Bonus question:
I am still at the planning phase of the script and I am not even sure if there are the required tools in VS. What do you think, is it possible?

Thank You in advance,
Dobromir

Anhänge (2)

Terrain 4.pyp
Typ: text/xml
657-mal heruntergeladen
Größe: 11,69 KiB
img
Targeted output.jpg
Typ: image/jpeg
95-mal heruntergeladen
Größe: 383,51 KiB

Lösung anzeigen Lösung verbergen

Xinling
Xinling
10.06.2022 - 12:12 *

Zitiert von: DGeorgiev
I am trying to make a script that generates a terrain model using slabs using the sloped-surface terrain from allplan. So as a starting point I have a random shaped surface, which then is sliced using planes and finally take out their intersection points. Using the points slabs are created, starting from the highest point, whose shape/area is afterwards substracted from the one below (making the terrain easier to model).

The node IntersectionPoints currently only works between curves. It doesn't support to calculate intersections between curves with surfaces or solids.

Although VS has some limitation, but it should still be able to accomplish something similar to what you shown in your target picture, if the terrain isn't very complicated. Please check the screenshot attached for details.

The basic idea is to generate the contours from a terrain surface based on planes. Luckily the node SectionCurves will help you there. After that, you just need to use them generate the base surfaces and then extrude those base surfaces (try Node ExtrudeAlongVector or ShellFromFace) to get the solid you need.

Product Owner API, Allplan GmbH

Anhänge (1)

img
Terrain.png
Typ: image/png
158-mal heruntergeladen
Größe: 191,92 KiB
11 - 13 (13)
Xinling
Xinling
20.06.2022 - 09:22 *

Zitiert von: DGeorgiev
Some of the nodes seems to also have been deleted when changing the version. This is what the file looks for me.

Which Allplan version do you use? I tried Nemo's script with Allplan 2022-1-3 and it works just fine.

If your Allplan is also 2022-1-3, could you please try to delete the folder VisualScripts in ETC and reinstall the latest Allplan to check if it works?

Product Owner API, Allplan GmbH

DGeorgiev
DGeorgiev
21.06.2022 - 11:05

Which Allplan version do you use? I tried Nemo's script with Allplan 2022-1-3 and it works just fine.If your Allplan is also 2022-1-3, could you please try to delete the folder VisualScripts in ETC and reinstall the latest Allplan to check if it works?

I am running at 2022-0-3, I think the office updates the software several months after the release of a new update just to make sure they are first tested.

I know I am running a little out of the thread topic, but its regarding the same script. Is there a node that allows multiple planes (with different heights) to be fed into "Slab" node? All of them seems to only work only with "ReferencePlane" inputs, and not "Plane". The problem with "ReferencePlane" it it produces only 1 output?

Nemo
Nemo
21.06.2022 - 11:40 *

Another case where Allplan tries to "reinvent" visual scripting:
Each node needs an option to set the combination mode that "produces" the output data from the input data.
All other visual scripting competitors (e.g. Grasshopper, Dynamo) have this since the beginning:
-Shortest List
-Longest List
-Cross Connection

In this special example "Longest List" would be the one you need!

With Cross-Connection, it's easy to imagine that this only really makes sense with 2-3 inputs.
And above all: There is only one output!

Anhänge (2)

img
node_combine_inputs.png
Typ: image/png
64-mal heruntergeladen
Größe: 86,62 KiB
img
lacing_modes.png
Typ: image/png
54-mal heruntergeladen
Größe: 246,50 KiB
11 - 13 (13)