Pages in Documentation
Settings
UI3 Overview
[old] Doors UE5
Quick Guide 2026
Quick Start
Swap Actor
Custom Assets
System Drawings
Guide 2022
Tips & FAQ
Guide 2024
Fix Bugs
FAQ
Cost Tracking
Modes
Other Features
Designer
Edit Scene
Var Actor
UI Layout
New in 2026
Multi-Unit-Prj
Google Sheets
Data Tables
Video Guides
Quick Videos
Designer
Cost Tracking
Widget Panels
Quick Guide
Scene Settings
Connect BP
VR projects
Version History
F. w. Preview
Fix Known Bugs
UI Settings
UI Layout
Gamemode
FAQ + TIPS
Quick Guide
V4 Functions 2
V4 Functions P1
V4 Quick Guide
Ver History
V3 Placements
V3 Mesh Def.
V3 Segments
V3 Quick Start
Books V2
Books V1
Customize
Quick Guide
Swap Actor
FAQ + TIPS
Doors UE4 (V1)
3.1 Bugs Fixes
Ver History
V2 Generic BP
V2 Examples
V1 Railings Fences
UI 1 - Part 1
UI 1
Ui 1 - Part 2
1 Overview
UI2 Features
UI2 Get Started
UI2 Info Map
UI2 BP Actors
UI2 User Manager
UI2 FAQ
UI2 Tutorials
UI3 Overview
Getting Started
3.1 Info Map
Variation Actor
Blueprints
Multi-Unit Projects (Part 1)
Setting up a multi unit project, like an appartement building. The project runs locally and uses datatables to store data defining the units.
It could be used in a showroom on site or in the real estate office.
Content:
Setting a User
The User is set in the overview level and gets passed on to the unit levels.
- The app looks at the Server Name set in the Info Map
- The User ID is taken from the servers data table row with the Server ID row name
- The User Name and data is then taken from the users data table with the User ID row name
This may look overly complicated. But it avoids accidental or unauthorized changes to other users' data. A user can't be allowed to change the user within the app to someone else's when cost tracking is involved.
Data Table Units
This data table contains the specific data for each unit. It will override the Unit Type Data when specified.
- Unit Type Name - Row Name of the Unit Type
- Floor - Floor number starting with 0 for ground level
- Size, ... - Override specifications for the unit
- Availability - 0=available, 1=under contract, 2=not available
- North Offset - Offset (degrees) for units located on the side or back of the building
Editor Data Table Units
This data table contains the data used within the editor.
- Unit Specific Level - A level can be loaded for assets only visible in this specific unit. Example: Courtyard areas for ground floor units.
- Unit Offset / Rotation - Offset position for the unit relative to default unit position within the building
Unit Info Widget
The Unit Picker will display the information for the selected unit taken from the data tables (source).
Discription text can be translated in the UI Text datatable assigned in the info map.
- Availability is the current state of the unit
- Floor shows the location within the building in a friendly way.
- Specs is the text on the left side of the widget
Visiting a Unit
The unit can be visited by clicking the button at the bottom. This will exit this scene and open another scene for the selected unit type.
Unit Type Level in the Editor
User Data Management
Previous Session or Level - The level will take the user (and unit) from the MUP Save Game.
Streaming Levels
There are 2 types of streaming levels
- Streaming Levels are the usual sub levels containing assets as in standard single unit scenes.
- Levels with Transform are the environment (surrounding) levels that are streamed with an offset/rotation.
The surrounding buildings and environment will look different depending on the location of the selected unit. The Levels with Transform are transformed to simulate how they would look from the selected unit.
Main Menu Layout Data
The 3 unit type scene share the datatable for the menu layout.
Editor Data Table Units
The level offset for the surrounding buildings as well as the name of any additional levels are stored in the editor data table for units.
The level has to be loaded from the overview level. The offset is not applied if the unit type level is played directly while editing. The level will look as if located at ground level instead.
Save Slots
User Choices can be saved per user name in the 5 available save slots. The last used save slot is loaded with the user name from the MUP Save Game. Choices can be re-applied in another unit under these conditions:
- The Save Set ID set in the Info Map of all levels is the same
- A Designer is used. Designers use Tags to link objects
- Features with Preview can be used if they use the same data table in the Info Map
Edit Mode does not work. The actors are linked directly and are not the same in another level.
Top of page