PanoFlow360° Virtual Tour Frameworkby MindOceanDocs
360° Virtual Tour Framework · Unreal Engine

PanoFlow documentation.

Turn your 360° renders into a complete, branded real-estate sales tour: units, floors, live finish options, minimap and measuring. Set it up in the Details panel. No code, no Blueprints.

UE 5.5 – 5.8Windows · Android (touch)C++ plugin, full sourceDemo: Aurora Heights

What your client gets

PanoFlow wraps your renders in a sales app the developer can put on a showroom screen or an Android tablet.

Project browser

Landing page with the project, developer panel and a card for every unit.

Room-to-room walk

Hotspots between rooms with smooth transitions, placed on your floor plan.

Live finish options

Furnishing, interior style, flooring, day / night. Switch in one tap.

Floors & stairs

Multi-floor units with staircases or elevators and a live minimap.

Room facts

Area, dimensions, ceiling height and a measure tool for distance and area.

Sales material

Gallery, balcony and exterior views, payment plans and documents per unit.

Read this first

The three actors and how they fit

A PanoFlow level is built from three actors. Each has one job, and none of them repeats another's settings.

One per level

MO_Project

The building or compound. It answers "what is this project and what's for sale?"

  • Landing page: name, hero photo, tagline, location
  • Developer card and stats strip
  • List of units (one card each)
  • UI Theme and branding
One per unit

MO_Unit

One apartment, villa or office. It holds everything inside that unit.

  • Floors, floor plans and rooms (360° renders)
  • Links between rooms, doorways, stairs and landings
  • Finish options (variants)
  • Unit card, gallery, payment plans, documents
One per level

MO_Viewer

The camera and the player. It holds no content: it plays whichever unit the buyer opens.

  • Zoom limits, mouse and touch speed
  • Room-to-room transition feel
  • Hotspot size, idle auto-rotate
  • Minimap / transition calibration
MO_Project (Aurora Heights) ├─ MO_Unit Villa A → Floors → Rooms (nodes) → Links / Doorways │ → Stairs (connectors) → Landing room per floor └─ MO_Unit Apartment A → Floors → Rooms … MO_Viewer plays the unit the buyer picks on the landing page

What happens at Play: the landing page is built from MO_Project and its list of units. When the buyer taps Enter Virtual Tour on a card, MO_Viewer loads that MO_Unit and opens its start room. Tapping the project name in the header goes back to the landing page.

Quick rule: project-wide text and branding → MO_Project. Anything about rooms, floors or the unit's sales material → MO_Unit. How the tour feels to navigate → MO_Viewer.

About 15 minutes

Quick start

You need: equirectangular 360° renders (2:1, e.g. 4096×2048), one floor plan image per floor, and Unreal Engine 5.5 or newer.

Fastest way to learn: open the included demo map DEMO_ALL and press Play. Every setting below is filled in there.

  1. Enable the plugin

    Copy MindOcean into your project's Plugins folder (or install from Fab), then Edit → Plugins, search PanoFlow, enable, restart.

    Plugins window with PanoFlow enabled
    01_plugin.jpg
    Search PanoFlow in Edit → Plugins, tick Enabled, then restart the editor.
  2. Set the Game Mode

    Open World Settings and set GameMode Override to MindOceanGameMode. It sets up the browser, input and HUD.

    World Settings GameMode Override
    02_gamemode.jpg
    World Settings → GameMode Override = MindOceanGameMode. Without it the landing page and the tour UI won't appear.
  3. Place the three actors

    In Place Actors search MindOcean and drag into the level: MO_Project (one per project), MO_Unit (one per unit, e.g. an apartment or a villa), and MO_Viewer (one per level). The default theme is assigned automatically.

    Place Actors panel filtered to MindOcean
    03_place_actors_n.jpg
    MO_PopupPanoramaViewer is optional: it shows 360° gallery items in a popup.
    1. MO_Project: the project (building / compound). One per level.
    2. MO_Unit: one apartment, villa or office. Add one per unit.
    3. MO_Viewer: the camera that plays the tour. One per level.
    4. MO_PopupPanoramaViewer: optional, opens 360° gallery shots in a popup.
  4. Describe the project

    Select MO_Project. In Mind Ocean → Project fill Project Name, Project Logo and Company. UI Theme is already set.

    MO_Project Details: Project and Browser Display
    04_project_details_n.jpg
    1. Project Name: title on the landing page and in the tour header.
    2. Project Logo: shown next to the name in the tour header.
    3. UI Theme: colours, fonts, icons and branding (see Theme).
    4. Portal Transition Mode: how the camera moves between rooms. Keep Straight.
    5. Company: developer name in the stats strip.
    6. Default / Supported Languages: reserved for a future update.

    Under Browser Display set the landing page: hero image, tagline, location, description, completion and the developer panel. Under Units add every MO_Unit and keep Start With Browser on.

    MO_Project Browser Display
    04c_browser_display_n.jpg
    1. Hero Image: the big background photo of the landing page.
    2. Hero Image Vertical Offset: moves the photo crop up or down.
    3. Hero Image Brightness: darkens the photo so text stays readable.
    4. Tagline: line under the project name.
    5. Location: city / area under the tagline.
    6. Description: longer project text.
    7. Completion: e.g. Q4 2027, shown in the stats strip.
    8. Total Floors: building floors, shown in the stats strip.
    Developer panel and Units
    04b_project_browser_n.jpg
    1. Developer Logo: logo on the developer card.
    2. Developer Description: text on the developer card.
    3. Developer Website: link on the developer card.
    4. Developer Brochure: optional PDF / image for the brochure button.
    5. Developer Contact: email and phone on the card.
    6. Units: every MO_Unit in the project, in card order.
    7. Startup Unit: unit opened directly when the landing page is skipped.
    8. Start With Browser: on = open on the landing page; off = jump straight into Startup Unit.
    The landing page those settings produce
    08_browser_n.jpg
    What those fields produce: the project landing page.
    1. Brand logo (from the UI Theme).
    2. Project Name (MO_Project).
    3. Tagline and Location (MO_Project).
    4. Developer card: Developer Logo / Description (MO_Project).
    5. Stats strip: units, Total Floors, unit types, Completion, Company.
    6. Unit card: built from each MO_Unit's Browser Card (cover, type, area, view, price, status).
    7. Enter Virtual Tour: opens that unit at its Default Start Node.
    8. Hero Image (MO_Project → Browser Display).
  5. Add a floor and its plan

    Select the MO_Unit. All its settings sit in five groups: Data Info (unit card, floors, rooms), Connectors (stairs), Variants, Settings and Preview (what the viewport shows while you edit).

    MO_Unit categories
    05_unit_overview_n.jpg
    1. Data Info: unit card, sales material, floors and rooms.
    2. Connectors: stairs and elevators between floors.
    3. Variants: finish options (furnishing, style, day/night).
    4. Settings: start room, north, calibration, camera height.
    5. Preview: what the editor viewport shows (plan, rooms, links).
    6. Fix Node IDs: repairs duplicate or empty room IDs after copying.

    In Data Info → Floors add a floor: name, short code (GF / 01 / RF), elevation in cm, and Floor Plan Texture. The plan appears in the viewport. Scale the actor so the plan matches real size.

    A floor entry
    07_floor_n.jpg
    Landing Node ID is the room where the buyer arrives when they take the stairs to this floor.
    1. Floor Name: shown in the floor selector.
    2. Floor Short Code: short label, e.g. GF / 01 / RF.
    3. Elevation: floor height in cm (0, 300, 600…).
    4. Floor Plan Texture: plan image for the editor and the minimap.
    5. Landing Node ID: room where buyers arrive by stairs / elevator (see Landing node).
    6. Nodes: the rooms of this floor.
    7. Connections: which rooms are walkable to each other.
  6. Add rooms (nodes)

    In the floor's Nodes add one entry per 360° render. Give it a Node Name and Panorama Texture, then place it on the plan with Position 2D. Area, room type and the rest fill the room card (see below).

    A node entry
    08_node_n.jpg
    1. Node ID: unique room ID. Links and landings point to it.
    2. Node Name: room name on hotspots, header and card.
    3. Node Role: Normal Room, or Landing for the stairs room.
    4. Panorama Type: Standard (one render) or Multi-Variant.
    5. Panorama Texture: the 360° render.
    6. North Offset: turns this one panorama (or use the calibration tool).
    7. Position 2D: room position on the plan.
    8. Camera Height (m): render camera height, for the measure tool.
    9. Area Sq M: shown on hotspot and card.
    10. Description: text on the room card.
    Floor plan in the viewport with room nodes and links
    plan_nodes.jpg
    Each coloured dot is a room. White lines are walkable links; yellow dots are doorways.
  7. Link the rooms

    In the floor's Connections, tick Connected for every pair of rooms you can walk between. A line appears on the plan, and a hotspot appears in the tour.

    Connections list
    07_connections_n.jpg
    Every pair of rooms is listed once. Tick the ones you can walk between.
    1. Connected: tick to make the two rooms walkable (both ways).
    2. Reset to Midpoint: puts the doorway back halfway between the rooms.
    3. Override Portal Anchor: tick to place the doorway yourself.
    4. Portal Anchor Position: the doorway point on the plan, so the hotspot sits on the real door.
  8. Press Play

    The browser opens with your unit card. Enter Virtual Tour starts at Default Start Node ID.

    Tour view with rail, hotspot, minimap and room card
    09_tour_n.jpg
    Inside the tour: the tools rail on the left, the header with project and room, a hotspot to the next room, the minimap and the room card.
    1. Header: project › unit › room. Tap the project name to go back to the landing page.
    2. Tools rail: Tours, Measure, Minimap, Variants.
    3. Hotspot: next room with its area. Tap to walk there.
    4. Minimap: the floor plan with every room. Tap a room to jump.
    5. Floor selector: switch floors.
    6. You are here, with the view cone showing where you look.
    7. Room card: area, size, finish, description, related rooms.
    8. Unit buttons: Unit, Gallery, Balcony, Docs.

Floor plan & rooms in detail

Doorways (Portal Anchor)

By default a hotspot points at the midpoint between two rooms. When the doorway is elsewhere, open the connection, tick Override Portal Anchor and set Portal Anchor Position, or press Reset to Midpoint. The yellow dot on the plan shows it.

Doorways on the plan
plan_nodes.jpg
Yellow dots are the doorways the hotspots point through.

Room card

Each node's Info and Card Display fields fill the card the buyer sees: area, room type (or a custom label), ceiling height, orientation and width × depth. Turn a Show … box off to hide that line. Set a Gallery Image to show a real photo instead of a crop of the 360°.

Card display fields
09_card_display_n.jpg
  1. Room Type: picks the hotspot icon.
  2. Show Ceiling Height / Ceiling Height M: card line.
  3. Show Orientation / Orientation: card line, e.g. South.
  4. Show Dimensions / Room Width / Depth: card line, width × depth in metres.
  5. Gallery Image: real photo for the card instead of a crop of the 360°.

Floors & stairs

Add a floor per level and set its Elevation and Floor Short Code (e.g. GF / 01 / RF). Under Connectors add a staircase or elevator, place it, and tick each floor in Floors Served. Set each floor's Landing Node ID: the room where the buyer arrives.

The Landing node: what, why, how

What: a normal room (node) at the top or bottom of the stairs or at the elevator door, marked as the arrival room of its floor.
Why it's needed: a staircase serves several floors, so PanoFlow must know which room to open when the buyer picks another floor. Without a landing, the stairs hotspot has nowhere to go on that floor.
How: 1) On each floor, add a node at the stairs (e.g. Stair Hall) with its panorama and set Node Role = Landing. 2) Connect it to the nearby rooms like any room. 3) In that floor, set Landing Node ID to its Node ID. 4) Make sure the connector's Floors Served ticks that floor.

One landing per floor served by stairs or elevator. Single-floor units don't need one.

Calibrating panoramas (fixing rotated 360° images)

If a render was exported facing a different direction, its room opens turned the wrong way, hotspots don't sit on their doors and the minimap cone doesn't match. You fix it visually, no numbers needed:

  1. Select the MO_Unit, tick Settings → Show North Calibration Tool, then press Play.
  2. A bar appears at the bottom of the screen with a TRUE NORTH ↑ marker. Pick a mode:
    • Calibrate North (All Images): when every render shares the same wrong rotation (common when the whole batch came from one camera setup). Saves to the unit's Global Panorama Yaw Offset.
    • This Image: when only the current room is off. Saves to that node's North Offset.
  3. Drag left/right: the panorama turns under the camera (up/down still looks normally). Turn it until the plan's north direction in the room lines up with the TRUE NORTH marker. The live value shows on the bar.
  4. Click Confirm to write the value to the level (or Cancel to drop it). Stop Play and save the level.

Final rotation of each image = Global Panorama Yaw Offset + its own North Offset, so fix the shared error first with All Images, then fine-tune single rooms with This Image. You can also type the values directly in the same fields. The tool is editor-only and never appears in packaged builds.

Different from North Angle (turns the compass / minimap north) and from MO_Viewer's Minimap Yaw Calibration (aligns the minimap view cone; 90 is correct for most projects).

Connectors settings
11_connectors_n.jpg
One staircase serving three floors. It appears as a hotspot on every floor it serves.
  1. Connector ID: unique ID.
  2. Connector Name: hotspot label, e.g. Staircase.
  3. Type: Staircase or Elevator (elevator opens a floor picker).
  4. Position 2D: where it sits on the plan, same spot on every floor.
  5. Floors Served: tick every floor it reaches.

Finish options (Variants)

  1. Turn on Enable Variant Authoring.
  2. In Variant Groups add a group (e.g. Furnishing) with an ID, display name and icon, then its options (Furnished, Unfurnished). Mark one option per group as Base.
  3. On a node, set Panorama Type to Multi-Variant and assign a render to each combination in the variant panel.
Variant groups
12_variants_n.jpg
A group with its ID, name and icon, and one option marked Base.
  1. Group ID: internal ID, don't rename after use.
  2. Display Name: tab name in the tour.
  3. Icon: tab icon.
  4. Options: the choices in this group.
  5. Option ID: internal ID.
  6. Display Name: option label.
  7. Icon: option icon.
  8. Is Base Option: the default look, uses the node's normal render. One per group. Below the groups, tick Enable Variant Authoring to show the variant panel on nodes.
Node variant panel
12b_node_variants_n.jpg
On a Multi-Variant node, each option gets its own render. The Base option uses the node's Panorama Texture.
  1. Group name (Furnishing).
  2. The Base option uses the node's Panorama Texture automatically.
  3. A slot per other option: pick its render.
  4. Next group (Interior Style) with its own slots.
Same room furnished and unfurnished
13_variants_runtime.jpg
The result in the tour: the same room, Furnished and Unfurnished, one tap apart.
Advanced

Reference: every setting

Tip: click any screenshot to open it full size.

Every setting lives in the Details panel under Mind Ocean. Hover any field in the editor for the same explanation. Fields marked optional can stay empty; the tour hides what has no data.

MO_Project: the project (one per level)

Project

FieldWhat it does · why you set it
Project NameShown in the tour header and on the landing page. Required.
Project LogoThe project's own logo in the tour header (top centre). Optional.
UI ThemeColours, fonts, icons, branding. Filled with the plugin default automatically; swap it to restyle everything.
Portal Transition ModeHow the camera moves between rooms. Straight is the safe default; the curved mode bends the move through the doorway.
CompanyDeveloper name shown in the stats strip.
Default Language · Supported LanguagesReserved for a future localisation update. Leave as is.

Browser Display (the landing page)

FieldWhat it does · why you set it
Hero ImageBig background photo of the landing page. Use your best render.
Hero Image Vertical OffsetMoves the crop up or down when the important part of the photo is cut off.
Hero Image BrightnessDarkens the photo so white text stays readable (0.82 default).
Tagline · Location · DescriptionText under the project name.
CompletionFree text such as Q4 2027, shown in the stats strip.
Total FloorsBuilding floor count for the stats strip (not the unit's own floors).
Developer Logo / Description / Website / Contact / BrochureThe developer card on the right of the landing page. Optional.

Units

FieldWhat it does · why you set it
UnitsEvery MO_Unit in the project, in the order the cards appear. A unit not listed here has no card.
Startup UnitThe unit opened when the landing page is skipped.
Start With BrowserOn: open on the landing page. Off: go straight into Startup Unit (useful for a single-unit kiosk).
MO_Unit: a unit (one per apartment, villa, office…)
Unit details
06_unit_details_n.jpg
  1. Show Finish Type / Finish Type: badge on the room card.
  2. Floors: the unit's floors (next step).
  3. Unit Name: header and card title.
  4. Unit Stats: number + label grid in the Unit panel.
  5. Unit Amenities: feature pills.
  6. Payment Plans: plan name, down payment, instalments, years.
  7. Documents: brochure, price list, plans.
  8. Unit Gallery / Balcony Views / Exterior Photos: media behind the tour buttons.
  9. Browser Card: the unit's card on the landing page (below).
  10. Toolbar Visibility: hide any of the Unit / Gallery / Balcony / Exterior / Docs buttons.
Browser Card fields
06b_browser_card_n.jpg
  1. Cover Image: card photo.
  2. Unit Type: e.g. Standalone Villa.
  3. Area: shown on the card.
  4. Building Floor Label: e.g. G + 1 + Roof or Floor 7.
  5. View: e.g. Landscape & Pool View.
  6. Price Label: e.g. Starting EGP 28M.
  7. Show Status Badge / Status: Available, Reserved or Sold on the card.

Data Info · badges

FieldWhat it does · why you set it
Show Finish Type · Finish TypeBadge such as Luxury Finished or Core & Shell on the room card.

Data Info · Unit (the unit panel and card)

FieldWhat it does · why you set it
Unit NameName in the header and on the card.
Unit StatsGrid of number + label (e.g. 4 · Bedrooms) in the Unit panel.
Unit AmenitiesPills such as Private pool.
Payment PlansPlan name, down payment, number of instalments, years. Leave empty for cash-only.
DocumentsBrochure, price list, floor plans: display name, a size label (e.g. PDF · 2 MB) and the file.
Unit Gallery · Balcony Views · Exterior PhotosThree media sections behind the Gallery, Balcony and Exterior buttons. Each has categories of images, videos or 360° shots; turn Is 360 on for panoramas.
Browser CardCover image, unit type, area, building floor label, view, price label, status badge (Available / Reserved / Sold). Empty fields are hidden.
Toolbar VisibilityHide the Unit, Gallery, Balcony, Exterior or Docs button without deleting its content.

Data Info · Floors

FieldWhat it does · why you set it
Floor Name · Floor Short CodeShown in the floor selector, e.g. First Floor · 01.
ElevationHeight of the floor in cm (e.g. 0, 300, 600). Keeps floors apart in 3D and orders them.
Floor Plan TextureThe plan image: shown in the editor to place rooms, and in the tour minimap.
Landing Node IDWhere the buyer arrives on this floor when they take the stairs or elevator. Set it to the room next to the staircase (usually a landing or hall). Without it, changing floors has no arrival room.
NodesThe rooms on this floor (see Node below).
ConnectionsEvery pair of rooms on the floor. Tick Connected to make a walkable link and a hotspot. Expand one to place its doorway.

Connectors (stairs & elevators)

FieldWhat it does · why you set it
Connector ID · NameUnique ID and the label on its hotspot (e.g. Staircase).
TypeStaircase or Elevator. The elevator opens a floor picker.
Position 2DWhere it sits on the plan; the same spot on every floor.
Floors ServedTick each floor it stops at. On each served floor the buyer arrives at that floor's Landing Node ID.

Variants

FieldWhat it does · why you set it
Variant GroupsFinish categories (Furnishing, Interior Style, Floor Finish, Time of Day). Each has a Group ID (internal, don't rename later), a display name and an icon.
OptionsThe choices in a group: Option ID, display name, icon, and Is Base Option (the default look, which uses the node's normal Panorama Texture). Mark exactly one per group.
Enable Variant AuthoringShows the per-node variant panel in the editor. Leave off for projects without variants.

Settings

FieldWhat it does · why you set it
Default Start Node ID · Default Start Floor IndexThe room the tour opens in. Pick the entrance or the best room.
North AngleRotates the compass so N matches the real north of the plan.
Global Panorama Yaw OffsetTurns every panorama at once when your renders were exported with a different forward direction.
Show North Calibration ToolEditor-only button to align north while playing. Never shipped in packaged builds.
Default Node HeightCamera height in cm used to place rooms and hotspots in 3D (170 default).

Preview (editor only)

FieldWhat it does
Preview Floor IndexWhich floor's plan and rooms the viewport shows.
Show Floor Plan · Show Nodes · Show LinksToggle the plan, room dots and link lines in the viewport.
Show Tours (Nav Rail)Shows or hides the Tours button in the tour's tools rail.
Fix Node IDs (button)Renumbers duplicate or empty node IDs. Use it after copying rooms.
Node: a room
A node
08_node_n.jpg
  1. Node ID: unique room ID. Links and landings point to it.
  2. Node Name: room name on hotspots, header and card.
  3. Node Role: Normal Room, or Landing for the stairs room.
  4. Panorama Type: Standard (one render) or Multi-Variant.
  5. Panorama Texture: the 360° render.
  6. North Offset: turns this one panorama (or use the calibration tool).
  7. Position 2D: room position on the plan.
  8. Camera Height (m): render camera height, for the measure tool.
  9. Area Sq M: shown on hotspot and card.
  10. Description: text on the room card.
FieldWhat it does · why you set it
Node IDUnique ID (Node_01…). Links, landings and the start room point to it. Don't reuse one.
Node NameRoom name on hotspots, the card and the header.
Node RoleNormal Room for ordinary rooms. Landing for the room at the top or bottom of the stairs: it is where buyers arrive after changing floors, so the floor's Landing Node ID should point to it.
Panorama TypeStandard: one render. Multi-Variant: one render per finish option (variant panel appears below).
Panorama TextureThe 360° render (2:1). For Multi-Variant it is the Base look.
North OffsetTurns this one panorama so its north matches the plan. Easiest set with the calibration tool (see Calibrating panoramas).
Position 2DThe room's spot on the plan. Hotspots and the minimap use it.
Camera Height (m)Camera height at render time (1.5 m default). Makes the measure tool accurate.
Area Sq M · Description · Room Type / Custom Type TextRoom card text and the icon on the hotspot.
Show Ceiling Height · Show Orientation · Show DimensionsTurn each card line on and fill its value (height in m, e.g. South-West, width × depth in m).
Gallery ImageA real photo for the card instead of a crop of the 360°.
Variants panelMulti-Variant only: one render slot per non-base option.

Connection (doorway)

FieldWhat it does · why you set it
ConnectedMakes the two rooms walkable both ways.
Override Portal Anchor · Portal Anchor PositionPuts the doorway where it really is, so the hotspot and the transition go through the door, not the wall.
Reset to MidpointPuts the doorway back halfway between the rooms.
MO_Viewer: camera & feel (one per level)
FieldWhat it does · why you set it
Data ManagerThe unit shown when the level starts. Set automatically when entering from the landing page.
FOV · Min FOV · Max FOVStarting view width and how far buyers can zoom in and out.
Mouse Sensitivity · Touch Look / Zoom SensitivityMouse and touch tuned separately.
Transition DurationSeconds for the move between rooms (0.5 default).
Motion Blur · Blur Start / End · Ghost TrailThe feel of the move. Lower them for a calmer transition.
Hotspot Height · Hotspot FOV CompensationHeight of the room labels and whether they keep their size while zooming.
Idle Delay / Fade In / Spin SpeedSlow auto-rotate after no input, for showroom screens.
Minimap Yaw Calibration Deg · Mirror Minimap YawAligns the view cone on the minimap with where the camera looks. Change it only if the cone points the wrong way (try 90, -90, 180).
Transition Yaw Offset · Mirror Transition YAligns the direction of the room-to-room move if your plan is rotated.
Sphere Radius · Dist Factor · Min / Max OffsetInternal sizes of the panorama spheres. Leave as is.
Enhanced InputYour own input actions. Leave empty to use the plugin's.
In the tour: what the buyer sees and does
Tour UI
09_tour_n.jpg
  1. Header: project › unit › room. Tap the project name to go back to the landing page.
  2. Tools rail: Tours, Measure, Minimap, Variants.
  3. Hotspot: next room with its area. Tap to walk there.
  4. Minimap: the floor plan with every room. Tap a room to jump.
  5. Floor selector: switch floors.
  6. You are here, with the view cone showing where you look.
  7. Room card: area, size, finish, description, related rooms.
  8. Unit buttons: Unit, Gallery, Balcony, Docs.
ElementWhat it does
Look & zoomDrag to look around, mouse wheel or pinch to zoom. After a pause the view slowly auto-rotates.
HotspotsLabels in the room (name, area). Click or tap to walk to that room.
Header (top)Project › unit › room. Click it to go back to the landing page.
Tools rail (left)Tours, Measure (distance / area), Minimap and Variants.
Variants panelTabs per group (Furnishing, Style…). Swipe the tabs on touch screens; pick an option to switch the render instantly.
Minimap (top right)Plan with every room and a view cone. Click a room to jump there; switch floors from its menu; expand it for a bigger plan.
Room card (bottom right)Area, dimensions, finish, description and related rooms. Buttons: Unit, Gallery, Balcony, Exterior, Docs.
CompassShows north. Uses the unit's North Angle.

Theme & branding

All visuals come from one theme asset. Duplicate DT_MindOcean_Default, edit the copy, and assign it to UI Theme on the project. Each client can get their own look from the same plugin.

SectionWhat you change
BrandingBrand Logo (top-left of the browser), its height and offset, or a brand name and subtitle when there is no logo.
ColorsBackground, glass panels, borders, accent and selected colours, opacities.
TypographyFonts and sizes for titles, labels and body text.
IconsRail icons, room-type icons, info-card icons.
Navigation railWidth, margin, left or right side.
Node PreviewEditor-only look of the plan: Icon Scale, Label Size, colours, link colour and thickness.
Theme asset open in the editor
14_theme_n.jpg
The theme's Branding and Colors sections. Replace Brand Logo with your client's logo.
  1. Brand Logo: your logo on the landing page.
  2. Brand Logo Height: its size in pixels.
  3. Brand Logo Offset X / Y: nudges it.
  4. Brand Name: text used if there is no logo.
  5. Brand Subtitle: small line under the name.
  6. Colors: text, accent, selected and hover colours for the whole UI.
Look exactly like your render

Panorama quality

By default Unreal adds tone mapping, bloom and dynamic resolution, which make a finished render look softer and shifted in colour. PanoFlow switches these off for the tour so the buyer sees your render exactly as it left your renderer. You find the settings on MO_Viewer under Mind Ocean → Panorama Quality.

FieldWhat it does · why you set it
Exact Panorama ColorsOn by default. Passes your render's colours through untouched: no tone curve, no bloom, vignette or grain, fixed exposure.
Exact Colors Exposure BiasBrightens or darkens every panorama a little. Leave at 0 unless all your renders look too dark or too bright on the client's screen.
Sharp Panorama RenderingOn by default. Renders at full resolution with light anti-aliasing so fine detail like marble veins and fabric stays crisp.

Texture import settings

For each 360° render texture use Compression: BC7, Mip Gen Settings: NoMipmaps and Never Stream: on. The demo panoramas are already set this way.

If a panorama looks blurry in Play, check its texture settings first. A texture that streams or uses default compression is the usual cause.

Packaging for Windows & Android

Windows

Platforms → Windows → Package Project. Shipping is recommended for clients. Make sure your tour map is the Game Default Map in Project Settings → Maps & Modes.

Android

  1. Install Android Studio and set the SDK / NDK paths in Project Settings → Platforms → Android SDK.
  2. Set a package name and accept the SDK license in Platforms → Android.
  3. Package with Android (ASTC). Keep panoramas at 4096×2048 or smaller.
  4. Install with the generated Install_*.bat while the device is connected with USB debugging on.

Touch works out of the box: drag to look, pinch to zoom, tap hotspots and cards, swipe the variant tabs.

FAQ

Do I need to write code or Blueprints?

No. Everything is set in the Details panel. Full C++ source is included if you want to extend it.

What size should my renders be?

Equirectangular 2:1. 4096×2048 works on all platforms; 8192×4096 looks sharper on Windows but is too heavy for most Android devices.

Can I have several units in one project?

Yes. Add one MO_Unit per unit and list them in the project's Units. The demo has an apartment and a three-floor villa.

The plan labels are too big or small.

Change Node Preview → Icon Scale / Label Size in the theme. This only affects the editor.

Hotspots point at the wall instead of the door.

Use Override Portal Anchor on that connection.

Support

Questions, bugs or feature requests: email us and include your engine version and a screenshot.

support.mindocean@gmail.com