Arch Viz User Interface - Features

A brief introduction to the features of the Arch Viz User Interface and Tools available on the Unreal 4 Marketplace.

• Create and swap single or multiple instances of the same mesh, like a group of chairs or a row of lights.
• Multiple material ids supported
• Auto generated preview thumbs or use custom images for previews
• Adjust position offsets per mesh choice
• Trigger other swap actors through tags (parent -> child)

• Maintains static lighting
• Swap mesh groups together
• Auto-generated previews or use custom images
• Trigger other swap actors through tags (parent -> child)

They can be a starting point or fixed choices for the client. Schemes change all assigned swap actors with a single click. Not much extra work to set them up.

Up to 5 Save Slots per client and unit can be used to save customized sets of choices for a later session.

Technical: In unreal baked scene lighting gives a far better look than dynamic scene lighting. Scenario levels store all lighting information for the entire scene in its level. This level can be swapped in run-time changing the lighting for the scene instantly.

You can place swap actors within any scenario and then use them as usual.

Technical: Design Scenarios and Lighting Scenarios cannot be combined with each other. It's either / or - or better said: every scenario is unique. If you wanted to have 2 Design Scenarios and also switch between day and night you would need 4 scenarios. (design 1 day, design 1 night, design 2 day, design 2 night)

• Rendered in real-time with all current changes applied.
• Can be saved with a screen recorder (many available for free)
• Can be pre-recorded as HD mp4 movie for a web page etc.

You can teleport to another preset location from a list. The list will show all locations of all floors. Or you can click on the target button inside the current floor plan.

The time to load another scene is very fast compared to having to quit the walk- through and load another application.

• Keyboard and mouse
• Game controller
• Mouse only controls where you click on a dynamic target on the floor to move around. Thought for pixel streaming projects or projects with touch screen control *)
• Target move with a controller for VR projects *)

*) A few changes to the blueprints may be needed to get this working depending on the project or type of controller used.

Technical: VIVE, Oculus and other headsets require a 3D object in the scene that displays the interface. This is to avoid player discomfort.

The phone mesh can be replaced with another mesh similar in size. It sits behind the 3d widgets.

Some features like 'Drone mode' or 'Sequence Player' are disabled in VR mode.

• Project data is saved in a blueprint actor that is placed in the scene. Multiple UIs can live in the same project. Each in its own persistent level. Travel between those levels is possible.
• Entirely build with blueprint actors.
• Knowledge about how to create blueprints not required but useful.
• No programming or compiling code needed. Runs almost on every platform if assets and materials allow it.

BP_SDotUIToolsInfoMap

Client management