Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Learn how to create egress routes for site logicistics presentations

Site Egress Routes are a special type of path that can be used to demonstrate routing logistics. Site Egress Routes are not created or shown in the Path App. The Site Egress App is located in the Analysis Tab of the Fuzor App Menu. The Site Egress App can be dragged around the workspace for more information see Workspace Management.

Site Egress Routes are only visible when the path is open. Auxiliary apps can be opened from this menu.

The Create button creates a new path allowing you to place subsequent nodes.

The Vehicle Library button opens the Vehicle Library app to place vehicles on the path

The 2D Map button opens the 2D Map app showing the Egress route on the 2D Map.

Egress routes have a light error checking system to help users evaluate whether a specific egress route is a practical choice for their project. Obstructions are displayed in the egress route for each path in the project.

Denotes that there is an obstruction in the Site Egress Route

Denotes that there are no obstructions in the Site Egress Route.

Obstructions can be caused by objects in the way or a turn that is too tight with respect to the turning radius of the vehicle on the path.

When a Vehicle is placed on the path the turning radius is set based on the placed vehicle. If the turning radius is too small the turn will not be articulated and an obstruction appears in the Egress Route App.

Slight curbs may be read as obstructions if the tolerance of the path is too low for the situation at hand.

The Tolerance slider and checkbox allow the user to control the Tolerance. Similar to other path when an egress route path node is selected you have access to more settings to control the path. The tolerance Slider is located at the bottom of the Egress Route Settings Tab.

The Egress Route Settings contain additional settings the allow the user to customize the path even more.

The 2D Line Style controls the type of line that displays the edges of the path in the 2D Map.

Solid 2D Line Style

Dashed 2D Lines Style

Dotted 2D Line Style

Egress routes 3D Scene render is not affected by 2D Line Style.

Dot-Dashed Lines Style

Arrow Line Style

The Line Color pallet allows the user to select a color for the line in both the 3D Scene and the 2D map.

The Arrow Style drop down menu allows the user to control the arrows that animate on the path.

Triple Arrow Style

Basic Arrow Style

Arrows on the Site Egress Path animate along the path showing the route a vehicle would take.

The Arrow Color pallet changes the color of the arrows on the path

The Arrow Size textbox and slider control the size of the arrows on the path

The Arrow Height textbox and slider control the height of the arrow on the path. This setting is only available for Triple Arrow Style.

The Show Pins and Lines checkbox toggles whether The Pins and Lines on the path are visibly allowing the user to display just the arrows and the vehicle on the path.

The Ignore Collision checkbox toggles whether vehicle collisions are detected while the app is open.

Site Egress Routes can be visible in Flythrough. Use the Show Egress Routes checkbox in the construction tab to enable them.

Adding Site Egress Routes to Tasks

Learn how to add the different types of paths to the 4D Schedule

Site Egress Paths can be added to Temporary Tasks. If added the associated egress path will be visible during the duration of the task regardless of whether the Site Egress Menu is open.

The best way to assign an egress path to a task is to drag the egress path menu into the workspace so that the egress route is visible while 4D is open. See Workspace Managment to learn how to pop out a menu.

With the Egress route selected in the Site Egress App use the add to task button in the 4D Toolbar.

For more general information about how to create tasks and their functionality see Object Assignment.

  • No labels