How do I set up obstacles in VASA?

I am currently studying with the VASA sample package.
I am using VASA-Pathfinding-in-2D.dyn.
Can I set up obstacles in VASA?
In Space Analysis, I was setting obstacles with BARRIERS as shown in the image.


03-VASA-Pathfinding-in-2D.dyn (96.2 KB)

In VASA every object becomes a voxel. Each voxel is True or False - meaning Solid, or filled. Any solid voxel cannot be passed through.

Thanks for the reply.
I did not know that if you made it solid it would not pass.
Thank you for letting us know.
If you could do me a favor and share a specific simple example, that would be great. (dyn files would be appreciated).
I would like to learn from it.

VASA Examples.dyn (76.2 KB)
This contains examples for:
Distance Field: What you can walk to from a given point.
Path: Shortest route from point A to point B.
Direct Lighting: Find the space which is directly lit from an emitting point.
Viewed Space: Find the space which can be seen from a point.

Note that lighting and viewed space both highlight the void space. If you want to see ‘which of the solid voxels’ is visible, expand the filled voxels using the VASA-Operations-SurfaceOperations-ExpandByOneVoxel and ExpandAlongZ nodes, and intersect those with the original voxel model with a VASA-Operations-SolidOperations-Intersect node.

2 Likes

I am very sorry, but an error occurred.
I just ran the sample file you gave me.
I do not know how to solve this error.


@jacob.small
Explain what you want to do with the attached data.
I would like to have the site boundary recognized and find the shortest path to avoid buildings and other obstacles within it.
However, I do not know where to recognize the obstacles.
Please check the attached file and give me your advice.
It would be great if you could indicate how the nodes should be connected.
VASA-test.rvt (5.2 MB)
VASA-Pathfinding-in-2D-test.dyn (110.7 KB)

“Not set to an instance of an object” usually means there is a null value in your dataset coming into the node. So likely something is causing an issue in the proceeding group which generated the solid. Expand that and address the warning, or provide your own solids and points though the graph.