Quick starts

Customize the UI

Generate editable Widget Blueprints with one click, restyle the building blocks once, place buttons anywhere, and rename tabs per product. No event graph wiring needed.

The on-screen panel is UMG. Out of the box it is built by BAKRDesignerHUDWidget without any assets. One button gives you Widget Blueprint copies to restyle.

Quick start

  1. Select the configurator in the level, outside Play.

  2. Open 05 - UI, styles and motion (optional) and click Create / open editable UI.

    UI Widget Class, product tab names and Create or open editable UI button on the configurator
    Open the editable HUD and tailor its labels to the product.
  3. BAKR creates and saves the HUD and the building blocks it is assembled from in Content/BAKRUI/HUD, assigns UI Widget Class on the product and opens the HUD:

    AssetWhat it is
    WBP_BAKRHUDThe screen layout, assembled from the blocks below
    WBP_BAKRButtonA button that does one configurator Action. Reset, the panel toggles and the Configure pill use it.
    WBP_BAKRPrimaryButtonThe dark call-to-action variant, used for Summary
    WBP_BAKRTabA page tab with an underline that shows while its page is open
    WBP_BAKROptionOne choice: material swatch, variant, style, camera or motion command
    WBP_BAKRSectionA collapsible zone card holding its options
    WBP_BAKRSummaryRowOne summary card: zone, chosen option, swatch and Default/Customized badge
    WBP_BAKRProductEntryOne row of the product switcher menu
  4. Move, resize and restyle anything in the HUD's Designer: backgrounds, fonts, anchors, your logo.

  5. Compile and Save, save the level, press Play.

Materials, styles, variants, motion, cameras, summary, reset and hide/show are wired automatically. The Designer shows the structure; Play fills it with the product's catalog.

Restyle a block once

Every element of the HUD is its own Widget Blueprint, so a change to a block reaches every place it is used. Open WBP_BAKRButton to make every button square instead of round, WBP_BAKRTab for the page tabs, WBP_BAKROption for the choice buttons, WBP_BAKRSection for zone headings and spacing.

  • Normal and selected look. The style a block's Button has in its Designer is its normal look. Selected Style and Selected Label Color in Class Defaults → Style are its look while its action is on. A tab uses its SelectionIndicator underline instead. Options work the same way, so a square option stays square when chosen.
  • Summary rows. Badge colors and the Default/Customized wording are in the summary row's Class Defaults → Style.
  • A second look. Duplicate a block, restyle the copy and place it where you want that look, as WBP_BAKRPrimaryButton does for WBP_BAKRButton. For a repeated block (option, section, summary row, product entry), point the HUD's matching Widget Class in Class Defaults → BAKR → Designer at your copy.

In the Palette, these generated parts are listed under BAKR HUD parts (generated). Restyle them to change the generated HUD; for a UI of your own, use the buttons under Your own buttons.

Widget Designer palette showing BAKR command buttons and generated HUD parts
Reuse generated HUD parts and command buttons when building or restyling a layout.

Buttons inside the HUD

Drag a WBP_BAKRButton or WBP_BAKRTab into the HUD, or into any widget placed inside it, and set Action and Label in its Details. No names to match and no event graph: the button finds the HUD it sits in and keeps itself up to date.

ActionDoesHidden whileSelected while
ResetRestores the default configurationnevernever
Show Panel / Hide PanelSlides the panel in or outthe panel is already in / outnever
Toggle PanelSlides the panel in or outneverthe panel is in
SummaryOpens or closes the summary pagethe layout has no SummaryOptionsthe summary is open
Materials / Variants / Motion PageOpens that pagethe page has nothing on itthe page is open
Product MenuOpens or closes the product switcher's menuthe level has one productthe menu is open
NoneNothing by itself; bind On Clicked in your Blueprintnevernever

Turn off Collapse When Unavailable to keep a button in place instead of hiding it. From Blueprint, Press clicks it and State Changed fires whenever Selected or Available changes, for styling beyond the bound widgets. The HUD itself offers Run Action, Is Action Available and Is Action Active for the same actions; see Blueprint API.

Your own buttons

For a layout of your own, Tools → BAKR → Create UI building blocks creates three command buttons in Content/BAKRUI, without touching any configurator. They show in the Palette under BAKR. Each sends one command, by the IDs you gave things in the configurator:

BlockSetDoesSelected whileUnavailable while
WBP_BAKROptionButtonKind (Material or Variant), Zone, Option IDSets that option on that zone, such as Blue on Bonnetit is the zone's current choicea compatibility rule rules it out (the tooltip says why), or the IDs match nothing
WBP_BAKRSequenceButtonSequence ID, Action (Play, Reverse, Pause, Stop)What that action does in the Motion tab. Loop, play rate and restore come from the sequence's entry in step 05. Play continues a paused sequence.Play/Reverse: it runs that way. Pause: it is pausedthe ID matches nothing. Pause and Stop: another sequence, or none, is playing
WBP_BAKRCameraButtonCamera IDFlies (or fades) to that camerait is the active camerathe ID matches nothing

They need no HUD: drag one into any widget on screen. They follow the product the visitor is configuring, also after a product switch, and update themselves when the configuration, playback or camera changes.

  • An empty Label shows the catalog's name: the option's or camera's display name, or the caption the Motion tab gives that action.
  • An unavailable command button stays in place, disabled. Turn on Collapse When Unavailable to hide it instead.
  • An option button tints its SwatchImage with a material's swatch color. Turn off Show Swatch to keep your own image.

A row of buttons from the catalog

Kind, Zone, Option ID, Sequence ID, Action, Camera ID and Label are pins on Create Widget, so a loop over the catalog builds a row:

  1. Get Player Controller → cast to BAKRPlayerController → Product → State → Get Material Options (Zone = Bonnet).
  2. For Each Loop: Create Widget (Class = WBP_BAKROptionButton, Kind = Material, Zone = Bonnet, Option ID = the element's Id), then Add Child to your Horizontal or Wrap Box.

Sequences work the same from Motion → Sequences (each entry's Id), cameras from Get POIs (each one's Settings → Id). To change what a button targets after it is on screen, set the property and call Sync.

Rules for the generated widgets

  • Keep the functional widget names and types, and keep Is Variable on. Move and style them freely. A required widget that is renamed or removed causes a Blueprint compile error; an optional one just loses its behavior.
  • Keep the scroll boxes MaterialOptions, StyleOptions, VariantOptions and MotionOptions (and the optional SummaryOptions) as direct children of Pages. Their order can change.
  • Keep the Show Panel button and the camera bar outside ConfiguratorPanel, so they stay visible when the panel hides.
  • Add decorative widgets with any name.

The full list of required and optional names is in UI widgets.

Clicking the button again

Clicking Create / open editable UI again opens the assigned HUD. It never regenerates or overwrites your edits. To make a second skin, clear UI Widget Class and click again; new assets get numbered names. You can assign one HUD to several products.

Generated widgets are not migrated when BAKR adds new UI features. Layouts generated before the building blocks keep working: their plain buttons named ResetButton, MaterialsTab and so on are still wired by name, and their Widget Blueprints keep their old Palette category until you open and save them. To adopt a newer template, clear UI Widget Class and generate a fresh set, or add the new widget to your copy by hand. For example, add an optional Button named SectionCameraButton next to SectionButton in WBP_BAKRSection to get the zone camera shortcut.

Rename tabs per product

UI tab names in step 05 renames, for this product only:

FieldDefaultExample
Materials tabMaterialsFinishes
Variants tabVariantsModels
Motion tabMotionAnimation
Styles headingStylesPackages
Summary titleConfiguration SummaryYour car

The names also reach the kiosk page and web clients through the catalog (titles). A caption you changed directly in the HUD Widget Blueprint stays until you change the name here.

Panel side and touch

  • Panel on right on the controller sets the panel side. The camera shifts the picture the other way by the Exterior Panel Offset from Global Settings, so the panel never covers the product. With Create UI off there is no panel, and the product is framed centered.
  • The native touch handler ignores gestures that start on the panel or the camera bar. A very different custom layout should provide its own input exclusions.

Build your own from scratch

Create a Widget Blueprint with BAKRHUDWidget as parent. It draws nothing itself:

  • Implement Catalog Changed and Status Changed to build and update your buttons, or place the command buttons and let them update themselves.
  • Read the product's zones and selection through Product.
  • Call Request Command to send a choice, camera switch or playback request.
  • Call Set Panel Visible and bind On Panel Visibility Changed.

Assign it to the product's UI Widget Class. To change the default for every product, make a BAKRPlayerController Blueprint, set HUD Widget Class, and select that controller in your game mode.