I finally had a chance to pursue this issue. You’re right to rebuild from source: the launcher only delivers Windows binaries, and they won’t load in a source-built Linux editor.
Find the plugin inside your Lutris prefix. The launcher runs under Wine, so the files are in its prefix rather than your normal file system:
find ~/Games -iname ‘OmniWalk.uplugin’ 2>/dev/null
(If you put the Lutris prefix somewhere else, search ~ instead.) The folder containing that file should have Source/, Config/, Resources/ and Docs/.
Copy it into your project as YourProject/Plugins/OmniWalk/, then delete its Binaries/ and Intermediate/ folders (they were built for Windows).
Build it with your engine. For a C++ project:
/Engine/Build/BatchFiles/Linux/Build.sh YourProjectEditor Linux Development -project=“/path/to/YourProject.uproject”
For a Blueprint-only project, or to install it for the whole engine:
/Engine/Build/BatchFiles/RunUAT.sh BuildPlugin -Plugin=“/path/to/OmniWalk/OmniWalk.uplugin” -Package=“/tmp/OmniWalk_Linux” -TargetPlatforms=Linux
Then copy /tmp/OmniWalk_Linux into /Engine/Plugins/Marketplace/OmniWalk, and enable it under Edit → Plugins.
If there really is no Source/ folder, send me the output of ls -R on that folder and your Fab order number, and I’ll send you the source package directly. If the build shows any errors, please send the log. Linux editor builds are the configuration we’ve tested least, and I’d like to fix anything you hit.
A housekeeping & fixes update to streamline the code before an eventual 0.7 version.
Linux Editor Fix, Include Hygiene & Example-Level Placement
Engines validated: include fix on UE 5.5, 5.6, 5.7, 5.8; example-level fix on 5.7 and 5.8 (Win64) and on Linux — zero source changes between engines.
Linux: both modules compiled in editor configuration for Linux x64 — 52/52 translation units, 0 warnings under -Wall -Werror, with and without precompiled headers.
Example Level
The current example level started the player on a planet that belonged at the far end of the course. AOmniWalkShowcaseLevel spawned its zone labels, the orbit planetoid and its four moons as bare AActors. The planetoid — a 7 m sphere
with BlockAll collision — enclosed the start platform’s PlayerStart: the player
spawned inside it, was pushed out onto its surface, and OmniWalk adhered to it, so play began on
a sphere with gravity tilted 58°. All 65 zone labels were stacked at the origin facing the wrong
way, and the orbit zone had point gravity and ramps but no planet. Each root is now placed at the
intended transform before it registers.
→ AOmniWalkShowcaseLevel (SpawnLabel, Zone_OrbitPlanetoid)
Build Hygiene
Two editor headers depended on the precompiled header for declarations they use. OmniWalkSetupWizardUtility.h declares UENUM(BlueprintType) EOmniWalkPreset but included only CoreMinimal.h — which does not define UENUM — and never included its own .generated.h. SOmniWalkSetupWizard.h holds a TSharedPtr<class SComboBox<...>> without including SComboBox;
clang rejects an elaborated reference to an undeclared template (MSVC tolerates it). Every
default build force-includes UnrealEd’s shared PCH, which happens to supply both declarations,
so neither header ever failed on Windows or in a normal Linux build. Any build without that PCH — -NoPCH, bUsePCHFiles=false, or a future engine trimming the PCH — failed 3 of the editor
module’s 10 translation units. The first header now includes OmniWalkSetupWizardUtility.generated.h
(the UHT convention), the second Widgets/Input/SComboBox.h. Includes only; no code changed.
→ OmniWalkEditor
Validation
Linux editor configuration verified. Launcher engines refuse Linux editor targets,
so the compile was reproduced from UBT’s own Linux and editor flags with UE 5.6’s
pinned toolchain (clang 18.1.0): runtime 42/42 and editor 10/10 translation units, 0 warnings,
with and without the shared PCH. Objects verified as ELF x86-64; a probe confirmed PLATFORM_LINUX=1 and WITH_EDITOR=1. Linking and running inside a Linux editor are not yet
verified — that needs a Linux engine build.
All 504 quoted #include directives match on-disk case against UE 5.6 — required on
case-sensitive file systems, and never checked by a Windows build.
Regression test added — OmniWalk.Editor.SetupWizard.ShowcaseHelperActorPlacement builds the
showcase in an isolated game world away from the origin and asserts that the planetoid sits on
its point-gravity centre, the moons orbit it, and every label keeps its spawn location and
facing. Verified against the unfixed code first — it failed on all four assertions (planetoid off
centre, 4/4 moons inside the planet, 65/65 labels at the origin and misfacing) — and a mutation
run that restored only the moon defect was caught by the moon assertion alone.
Verified live in the 5.8 editor. With the fix, Play-In-Editor spawns the player at the PlayerStart on the start platform, walking, with gravity (0, 0, -1); before it, the player
rested on the misplaced planet 4 m above the floor. The existing showcase tests passed throughout,
because none of them checked where the helper actors ended up.
Conflict — two systems fighting over the same state
Logic — incorrect or dead behavior
Gap / Quality — missing, degraded, or untidy
New — added API or capability
Changed — refactor / rename
Validated — confirmed by build / test
Modernization & the “Chroma Orbit” Demo Minigame — v0.7.0
v0.6.7 (67) → v0.7.0 (70) — new runtime classes and Blueprint API; nothing removed. Three behaviour changes (see Upgrade Notes). Builds: Win64 editor (Development) — both plugin modules compile and link with 0 warnings, 0 errors on UE 5.8 and 5.7. Tests:31/31 pass on 5.8 and 5.7 (18 → 31). Engines validated: UE 5.8 (new working-tree baseline) and 5.7 (throwaway host whose plugin source is byte-identical to the tree; only EngineVersion changed). Platforms:Win64, Linux (unchanged).
The interactive demo is rebuilt from a feature tour into a third-person minigame whose one rule — light up every surface you walk on — turns OmniWalk’s major point into the whole game. Around
it, the plugin moves to UE 5.8 conventions, the third-person starter gets gravity-aware animation
and a modern camera, and the final review fixed two input bugs that appear when a player switches pawns.
A complete third-person game loop on three small worlds above a sea of clouds. Every
surface — floors, walls, ceilings and the undersides of worlds — is tiled with dark panels that light up in the world’s colour as the courier walks over them. Charge a share of each world
before its clock runs out, step on the sling pad, and fly to the next world, flipping to its
gravity mid-arc.
→ AOmniWalkChromaOrbit (director), UOmniWalkPaintFieldComponent, FOmniWalkPaintGrid, OmniWalkChromaTypes.h
The Loop
🏁 Title ─▶ 3·2·1 ─▶ 🚀 ─▶ 🟦 THE CUBE ─▶ 🚀 ─▶ 🌗 TWIN MOONS ─▶ 🚀 ─▶ 💫 THE HALO ─▶ 🚀 home ─▶ 🏆 Score card ─▶ 🔁 next round
⏱️ Clock runs out on any world ─▶ 🏆 Score card ("TIME UP") ─▶ 🔁 next round
Phase
What happens
Length
Attract
Title card over a slow orbiting camera. Player mode waits for Start; autopilot starts by itself
5 s (autopilot)
Countdown
3 · 2 · 1 on the launch deck
3 s
Slinging
Bézier arc to the next world; gravity blends to the destination’s, the FOV kicks by 14° mid-flight
1.1 – 2.8 s
Playing
Paint panels against a 45 s clock; banner “Light up N% before the clock runs out”
≤ 45 s
Stage clear
“WORLD CHARGED!” + time bonus; the exit sling pad lights up and waits to be stepped on
until stepped on
Results
“ROUND COMPLETE” or “TIME UP”, score, medal, round time, session best
7 s, then
The Worlds
World
Shape (collision)
Panels
Gravity
Target
Colour
Launch Deck
14 × 14 m slab with a dashed sling ring
—
world default
—
The Cube
10 m cube with 1.5 m rounded edges and corners
462
Point volume
50%
cyan
Twin Moons
two spheres, R 4.5 m; hop pads at the facing poles fling you across at any time
504 (2 × 252)
Point volume per moon
45% combined
magenta
The Halo
ring, inner R 9 m × 6 m wide (64 slabs), walked on the inside like a loop-the-loop
342
Spline volume pulling outward
75%
amber
Falling off a world (leaving its fall-out radius, or airborne for 4 s) respawns you on it
with a “LOST IN SPACE” banner and −3 s on the clock.
120 floating shards 150–400 m out give the sky depth and parallax; the layout is seeded (DecorSeed).
Scoring
Rule
Value
Each panel lit
10 points × combo
Combo
×1 → ×5; +1 for every 12 panels in an unbroken chain; breaks after 1.5 s without a new panel
Time bonus when a world is charged
50 points per second left on the clock
Medals
18,000 · 28,000 · 36,000
Session best
kept across rounds, shown on the score card
Controls
Action
Keyboard / mouse
Gamepad
Start a round
Space or Enter
A / Cross, or Menu / Start
Move
WASD or arrow keys
Left stick
Look
Mouse
Right stick
Jump
Space
A / Cross
Sprint
Left Shift
Left stick click
Crouch
Left Ctrl or C
Right stick click
Autopilot
UOmniWalkAutopilotComponent drives any ACharacter along a waypoint route with ordinary
movement input. Steering stays in the plane of the surface being walked, so it climbs walls and
circles planets without special cases. It sprints on straights, jumps where a waypoint asks,
keeps its heading while crossing onto the next face, and skips a waypoint after 1.25 s without
headway instead of pushing into a wall forever.
The demo turns it on with the ?Autopilot map option or AOmniWalkChromaAutopilotGameMode:
cube laps, a ring on each moon with a hop between them, and a helix around the halo, with a
fallback to the nearest unpainted panel. An unattended round clears all three worlds in ≈ 62 s for a Gold (38.8k – 40.6k measured).
Useful beyond the demo: a quick soak test for traversal changes.
HUD
AOmniWalkChromaHUD draws a Slate interface: brand, world chip in the world’s colour, clock (blinks red in the last 10 s), score that rolls up, combo chip, charge bar with a
target tick, title card with controls, banners (GO!, SLING!, WORLD CHARGED!, LOST IN SPACE), results card, and an AUTOPILOT tag.
The title card’s prompts follow the device in use: “PRESS A TO START” and stick controls
after gamepad input, “PRESS SPACE TO START” and WASD after keyboard or mouse input.
The clock sits on a soft translucent plate, so it stays readable over the Halo’s bright panels.
It is added to the player’s viewport layer rather than a canvas, so Movie Render Queue’s UI
pass composites it into renders. It attaches lazily, once a viewport exists, which is what MRQ needs.
Look — engine content only
FOmniWalkChromaEnvironment::Apply configures, and spawns when missing: a movable golden-hour
sun (−5°, warm) for Lumen, sky atmosphere, a volumetric cloud sea just below the worlds, a
real-time sky light, near-invisible height fog, and a graded post-process volume (bloom,
exposure −0.3, vignette, saturation and contrast lift, light motion blur and grain).
Panels, hulls and neon accents use only /Engine basic shapes and materials — no new content assets.
Opt out per level with bConfigureEnvironment.
New Classes
Type
Kind
Role
AOmniWalkChromaOrbit
Actor
Director: builds the arena (hulls, panels, pads, decor), runs the round, slings, respawns, title camera, autopilot routes
UOmniWalkPaintFieldComponent
Component
One world’s panels on two instanced meshes (dim → lit) with a pop animation
FOmniWalkPaintGrid
Struct
Spatial hash of panels: paint within a radius (facing-aware), nearest unpainted, coverage
CourierGravityScale 2.2 keeps the courier planted over curved crests at run speed (at 1.0 the
centripetal requirement v²/r exceeds gravity and the courier leaves the surface).
Third-Person Starter
The Mannequin played idle while running up a wall. (An old bug that came back.) The template ABP_Unarmed measures
ground speed as VSizeXY(Velocity) — world-space horizontal speed — which is near zero for a
character climbing a wall or walking a ceiling. New UOmniWalkLocomotionAnimInstance is a C++,
graph-free locomotion instance (idle / walk / jog / jump / fall / land with crossfades, evaluated
through its own anim-instance proxy) that measures speed in the plane of the current
gravity. AOmniWalkThirdPersonCharacter uses it whenever the Mannequin sequences exist.
WalkAnimSpeed 180 · JogAnimSpeed 420 · BlendTime 0.18 s · AirborneGraceSeconds 0.12 s
Sequences are soft references to the Mannequin’s Unarmed set, overridable per instance;
a sequence for a different skeleton is dropped rather than evaluated.
bUseGravityAwareLocomotion (on by default) switches back to ABP_Unarmed.
The third-person starter was invisible in projects without the Mannequin. It now builds a “courier” stand-in from engine basic shapes — body, glowing visor, antenna — with a procedural bob.
Camera: boom length 380 cm, position lag 12 and rotation lag 10, framing offset
+45 cm, 80° FOV.
Camera auto-follow on AOmniWalkPlayerController: after a pause in look input the view eases
behind the direction of travel, gravity-relative. Off by default; the demo turns it on.
Property
Default
Meaning
bAutoFollowMovement
off
Master switch
AutoFollowDelay
1.0 s
Quiet time after look input
AutoFollowYawSpeed
120 °/s
Max turn rate (reached at 600 cm/s)
AutoFollowMinSpeed
150 cm/s
Below this the camera is left alone
AutoFollowPitch
15°
Resting pitch, looking down onto the pawn
AutoFollowPitchSpeed
25 °/s
How fast pitch settles
AOmniWalkExampleCharacter::SetSprintActive / IsSprintActive for code-driven sprinting.
Switching Pawns
The example character stopped responding after the player left it and came back. Actions
were bound once per pawn, guarded by a flag. Every possession gives a pawn a new input
component, and the engine creates it under the same object name, so the flag — and any
identity check — still said “bound” and the new component got no bindings. After driving a
vehicle, or any other Possess round trip, WASD, jump, sprint and crouch did nothing. Binding is
now judged by the component’s contents, so each new component is bound exactly once.
→ AOmniWalkExampleCharacter::BindEnhancedActions
The hover vehicle ignored WASD when entered from the example character. Its driving context
was added at priority 0, below the character’s (1), which stays registered and maps the same keys,
so the character’s actions consumed them. The vehicle now adds its context at DriveMappingPriority (default 2) and removes it when unpossessed, so the keys return to
the character on the way out.
→ AOmniWalkHoverVehicle
Pinned by OmniWalk.Editor.HoverVehicle.DrivesAfterLeavingExampleCharacter, which plays in the
editor and walks → drives → walks again with simulated key presses. Before the fixes it
failed on all three steps.
Review Follow-ups
Six small items from the final review, all fixed. Four are pinned by a test that failed first, one is checked in a render.
Gamepad players could not jump. The example character mapped A / Cross to Crouch and
nothing to Jump. A / Cross now jumps (like Space), and Crouch moves to the right stick click. Behaviour change for gamepad crouching — see Upgrade Notes.
→ AOmniWalkExampleCharacter · OmniWalk.Editor.Input.ExampleCharacterGamepadMappings
The title card always said “PRESS SPACE TO START”. The director now tracks whether the player
last used a gamepad or keyboard and mouse (FOmniWalkChromaInputDevice) and the HUD shows matching
prompts and controls. Activity on one kind of device switches; activity on both, or on neither,
keeps the current prompts, so a bumped mouse does not flicker them.
→ AOmniWalkChromaOrbit, AOmniWalkChromaHUD · OmniWalk.Chroma.Input.DevicePromptSwitching, OmniWalk.Editor.Chroma.PromptsFollowInputDevice
The hover vehicle failed silently in projects without Enhanced Input. If the default input
component class is the legacy UInputComponent, it now logs an error naming the class and the
project setting to change, like the example character does.
→ AOmniWalkHoverVehicle · OmniWalk.Editor.Input.HoverVehicleReportsNonEnhancedInput
The clock was hard to read over bright panels on the Halo. It now sits on a soft translucent plate.
→ AOmniWalkChromaHUD · checked in a new 1080p render
A stray “Results → Attract” log line appeared when the first pawn was configured on the title
card. Re-running the title setup for a new pawn is not a phase change, and is no longer logged as one.
→ AOmniWalkChromaOrbit · OmniWalk.Editor.Chroma.PromptsFollowInputDevice (log capture)
The Mannequin mesh was loaded without checking it exists. The third-person character now checks
the package first, as 0.6.x did, so packaged games without the Mannequin log nothing. There is no
failing test for this: a missing package loads silently in the editor.
→ AOmniWalkThirdPersonCharacter::SetupMannequin
Modernization
UE 5.8 is the working-tree baseline — descriptor EngineVersion 5.8.0; dev project targets use BuildSettingsVersion.V7 (5.8 refuses V6) and EngineIncludeOrderVersion.Unreal5_8. The source
still builds unchanged on 5.7 (validated).
Every raw object-pointer UPROPERTY in the public headers is now a TObjectPtr<> (40), for
editor access tracking and lazy loading — the UE5 convention since 5.0.
AOmniWalkHoverVehicle uses Enhanced Input. The plugin’s last legacy bindings, BindAxis("MoveForward"/"MoveRight"), depended on axis mappings modern projects no longer define.
They are replaced by runtime-created actions and a mapping context added on possession:
Action
Keys
Gamepad
Throttle
W / S, ↑ / ↓
Left stick Y
Steer
D / A, → / ←
Left stick X
IWYUSupport.Full on both modules. The runtime module adds Slate / SlateCore (HUD); the
editor module adds EnhancedInput (tests).
Unreal Insights CPU scopes on the per-frame hot paths:
Descriptor: 0.7.0 (70); the description says “UE 5.5+” (was “UE5.4+”) and mentions the demo.
A duplicated copyright line removed from OmniWalkZeroGPad.h / .cpp.
Editor & Setup Wizard
The generated example level is Chroma Orbit.UOmniWalkExampleLevelUtility builds the
director, the environment and one PlayerStart on the launch deck, sets AOmniWalkChromaGameMode,
and removes the previous generation’s showcase, demo generator and placed pawns. Panels are built
in the editor, not only at play, so the level reads correctly before pressing Play.
Setup Wizard → Example Tools: the button reads “Create And Open Chroma Orbit Demo”.
The utility’s functions are now also BlueprintCallable, so they can be scripted from Python
(unreal.OmniWalkExampleLevelUtility).
The feature tour is still available: drop AOmniWalkShowcaseLevel into any level.
Upgrade Notes
Change
Who notices
What to do
Example level is now Chroma Orbit
Anyone who regenerates OW_Example
Place AOmniWalkShowcaseLevel for the old tour
Third-person character no longer uses ABP_Unarmed by default
Projects with the Mannequin
Set bUseGravityAwareLocomotion = false to get it back
Hover vehicle reads Enhanced Input, not legacy axes
Projects that mapped MoveForward / MoveRight for it
Nothing — the vehicle now brings its own actions and needs no project input settings
Gamepad A / Cross jumps; Crouch moves to the right stick click
Projects using the example character’s built-in gamepad mapping
Nothing, or map Crouch back in a subclass’s mapping context
“No PlayerController” at BeginPlay logs at Verbose, not Warning
Log watchers
It fired for every pawn that nobody controls yet; possession adds the context anyway
Descriptor EngineVersion is 5.8.0
Source users on 5.5 – 5.7
Set EngineVersion to your engine to skip the load prompt (5.7 verified)
DefaultEngine.ini: startup and default map /Game/OmniWalkExamples/OW_Example; global game mode OmniWalkChromaGameMode; deprecated r.Mobile.VirtualTextures removed (5.8 raises a startup ensure).
Content: Mannequins copied from the UE 5.8 template; /Game/Cinematics/ holds LS_ChromaWalkthrough
(empty on purpose — with no camera cut, MRQ films the player camera).
Docs/Manual.html — the Example Level section describes Chroma Orbit (round-loop diagram, topics table).
Docs/SetupWizardManual.html — Example Tools Mode text updated.
Known Limitations
Hard 90° convex edges at run speed. At 600 cm/s the gravity turn over a sharp 90° lip lags
about 1.5 m behind the character, which leaves the surface and falls. Chroma Orbit’s cube therefore
has 1.5 m rounded edges, which keeps every surface change under 45°, so OmniWalk tracks it
continuously. Core convex traversal is unchanged in this release.
The small open items found in the final review are fixed — see Review Follow-ups.
Validation
Engine
Build
Tests
Live
UE 5.8
0 warnings
31/31
autopilot rounds, player-mode round, MRQ render
UE 5.7
0 warnings
31/31
One test (ExampleLevelChromaGeneration) logs two engine warnings about TypedElements reference
tracking on both engines. It passes.
The generated example level is Chroma Orbit, panels built in the editor
Verified live in the 5.8 editor over Epic’s Model Context Protocol server. Autopilot rounds
cleared all three worlds in 61 – 63 s for 38.8k – 40.6k ( Gold) with no respawns and looped
into the next round. In player mode the title card waits for Start, and a round that runs out of
time goes to the score card and then a new round.
v0.7.0 (70) → v0.7.1 (71) — new content (a 14-model kit), new Blueprint API on the hover vehicle, and fixes that make the OmniDrive, the track generator and the planetoid generator work as documented. Two behaviour changes (see Upgrade Notes). Tests:43/43 on UE 5.5, 5.6, 5.7 and 5.8 (32 → 43: new content, driving, track, cinematic, wall, surface-response and spider-walk tests), each in a fresh host with the plugin built for that engine. Per engine: each engine builds the model kit from the same sources (14 models, 37 packages, all saved by that engine) and regenerates the demo map, like 0.7.0’s (see ). Not packaged yet.
The OmniDrive hover vehicle now ships with a complete model with physics body; it hovers level on flat ground, planetoids and loops, and steers. Around it, the plugin ships a kit of fourteen models built in Blender, so every OmniWalk actor that needs a visual has one.
At a Glance
Area
What changed
Markers
OmniDrive
Ships with a model and collision; stable hover; suspension strong enough for loops; per-point gravity on curved fields; real steering with grip; SetThrottleInput / SetSteerInput
Track generator
Default road mesh; roads follow each spline point’s up vector (loops no longer twist or roll); gravity pulls onto the road surface; closed splines; builds at runtime
Planetoid generator
Default planetoid model and regolith surface; builds at runtime
Zero-G pads
Visible pad (cyan entry, amber exit), flush with the floor at any scale
Spider walk
Walkers now go over hard 90° edges (up a wall and over the top, off a ledge and down its face) instead of being flung off
Walking, cinematic, surfaces
Idle walkers no longer creep along walls; the cinematic turns the character with gravity; surface response no longer cancels mag-boot presets
Model kit
14 models, a master material with 14 instances, 7 textures, saved by each engine
Tests
8 new tests, including five Play-In-Editor physics tests
It now defaults to /OmniWalk/Models/SM_OW_OmniDrive
(479 × 275 × 128 cm): four pods on the component’s trace points, two convex collision hulls.
Bounced and flipped at 60 fps. The push-only suspension damper is integrated explicitly; with the
old default Damping = 50, four points × 50 /s × 1/60 s = 3.3, above the stability limit of 2. An idle
craft swung between 0.9 and 9 m above a planetoid and ended upside down. The default is now 3
(settles in about a second; stable down to 30 fps), and the property documents the limit.
Nose-up tilt on curved fields. Every suspension point was damped against the gravity-up at the
craft’s centre; on a 40 m planetoid a pod 150 cm ahead sits on a radial rotated by 150/R, so steady
driving read as vertical motion at the front and back pods and pitched the nose up 12° at 11.5 m/s.
Each point now samples the field at its own position: measured tilt 2.4° (up · radial 0.9991).
Could not steer.TurnTorque was scaled by mass but not by the moment of inertia, so a car-sized
craft reached about 0.08 rad/s² of yaw: a full-steer run turned 0°. Steering is now a yaw-rate
controller about the craft’s own up axis (MaxTurnRate 90°/s, TurnResponse), with LateralGrip
so the craft goes where it points: measured 194° in 3 s at 11 m/s, 18.6° slip.
Scraped round loops. At full compression the four suspension points lifted 4 × HoverForce = 2 g
with the old default of 500; entering the showcase’s 20 m loop at 16 m/s needs 2.3 g, so the pods
bottomed out, scraped the road and the craft slowed to 2–3 m/s at the top of the loop. The default is
now 1000 (4 g of lift); round the showcase loop the craft now holds 15–17 m/s. It rides a little
higher (about 72 cm at rest).
SetThrottleInput, SetSteerInput, GetSteerInput (Blueprint-callable), for AI, cutscenes and
scripted demos. A held drive key overrides them while a player drives. GetThrottleInput is now
Blueprint-pure as well.
ForwardThrust is applied as an acceleration (same result as before, now stated in the tooltip).
Track Generator (AOmniWalkTrackGenerator)
No road.TrackMesh defaulted to none, so tracks had no mesh and no collision (the OmniDrive
showcase’s vehicle fell through). It now defaults to SM_OW_TrackSegment: one metre of 9 m deck with
its driving surface on the spline, so the spline field pulls a craft straight onto it.
Loops twisted. Spline meshes ignored the spline’s up vectors; every segment faced world up and
flipped at vertical tangents. Each segment now uses its spline point’s up vector. The template
generator’s loop sets its points’ up vectors toward the loop’s centre.
Closed splines get their closing segment; segments take the spline’s mobility (a Static segment
cannot attach to the Movable spline).
Runtime tracks were empty.OnConstruction (which builds the road) was editor-only, so tracks
spawned at runtime, including the template generator’s in a packaged game, had no road. It now runs
in every build. The same applies to the planetoid generator.
Road collision cut across curves. The road was one spline mesh per spline point, several metres
long on a loop, and a spline mesh’s convex collision spans the chord of its piece, so a craft struck
the inside of the curve. The road is now laid by distance in pieces of at most MaxSegmentLength
(new, 250 cm): within 4 cm of a 20 m loop.
The OmniDrive template’s loop ran into itself. Its entry and exit shared one lane, so the road
leaving the loop passed through the road entering it. The loop now shifts sideways by 11 m from entry
to exit, like a real loop-the-loop. The template’s craft now starts 5 m in from the road’s start, with
all four pods over the deck.
Track gravity pulled sideways. A track’s field pulled toward the spline’s centre line, so a craft
off-centre on the 9 m deck was pulled across the road: 2.3 m off-centre on the loop, gravity was 75°
from the road’s down and the craft stalled against its own thrust. Tracks now pull along the road’s
down wherever you are on the deck (new bSplineGravityAlongUpVector on gravity volumes, on for tracks,
off for tubes).
Loops rolled near the top. Between the top point of a loop and the next, the spline’s own up
vector rolled up to 9° sideways (the engine interpolates point rotations stored as shortest-arc
quaternions, which flip sign where the up vector passes upside down), and a craft’s pod struck the tilted
road. Road pieces and road gravity now interpolate the points’ own up vectors: the largest sideways
lean on the showcase loop is 0.4°.
Spider Walk Over Hard Edges (UOmniWalkPro)
Walkers were flung off hard edges. Convex traversal only changed the target gravity; nothing
carried the character round the edge. A walker holding forward up a wall reached the top edge, left the
wall with gravity still pointing into it, and was thrown across the top and off the level (airborne for
10.6 s in the new test). Walking off a ledge onto its face failed the same way.
Edge wrap. When the surface ends just ahead and a face continues round the edge, the character is
now carried round the edge line onto that face in ConvexWrapSeconds (new, 0.15 s; 0 = at once), its
foot rolling round the edge, keeping its speed, with gravity into the new face. It only wraps onto a face
it fits on and that goes on far enough to stand on (not the rim of a floor tile), and never at a concave
corner. IsWrappingConvexEdge() (Blueprint-pure) reports a wrap in progress. Measured over the kit’s hard 4 m
block at walk (3.6 m/s) and sprint (9.9 m/s): up, over, down and away without leaving the surface.
With convex traversal on (the example characters’ default), walking off a ledge now carries the
walker down its face instead of falling. Turn bEnableConvexTraversals off where a character should
drop off ledges.
Walking, Cinematic and Surface Response
Idle walkers crept along walls at about 63 cm/s. The adhesion impulse, meant to hold a walker to
its surface, was also applied while it stood on that surface; walking movement then rescaled it into
motion along the wall. Adhesion now applies only while falling or detached, not while walking: an idle
walker on a wall stays within 0.0 cm over 3 s.
UOmniWalkCinematic turned gravity but not the character. The walker stood sideways to its new
gravity until surface detection caught up. The character now turns with the gravity during the
transition, on an immediate snap, and at the end. Auto-exit suits flips onto a surface the walker is
already touching; see Modules.html for flips across a room.
Surface response cancelled mag-boot presets.UOmniWalkSurfaceResponse rewrote friction,
adhesion and walk speed every 0.1 s from values captured at BeginPlay, so Hover and Mag-Lock were undone
at once and sprint speed flickered, even on an ordinary floor. It now writes only when the surface type
changes and, on leaving, restores whatever was in effect when it arrived.
Docs: UOmniWalkPhysicsField affects PhysicsBody objects (the PhysicsActor profile); a StaticMeshActor spawned at runtime needs the profile set.
Chroma Orbit Demo
The autopilot could stall on the halo after its stage cleared. The halo’s exit pad sits at the bottom of
the ring’s inner surface, and the autopilot steers at a waypoint’s projection onto the floor it stands on. When
the stage cleared with the courier directly opposite the pad, at the top of the ring, that projection was the
courier’s own spot, so it never set off and the round never reached its results. The exit route from the ring’s
upper half now goes round by the quarter point on the courier’s side first. Found by the 0.7.1 cooked-game
validation: 0.7.0’s rounds happened to clear elsewhere on the ring.
Planetoid Generator, Zero-G Pads
Planetoids default to SM_OW_Planetoid (dense sphere, regolith texture, exact sphere collision) and MI_OW_PlanetSurface; the engine sphere remains the fallback. Radius / 50 still scales it.
AOmniWalkZeroGPad has a visible PadMesh (no collision): cyan on entry pads, amber
(ExitGlowMaterial) on exit pads, kept flush with the floor at any actor scale.
Model Kit
Fourteen models in /OmniWalk/Models: OmniDrive, Planetoid, Track Segment, Tube Segment,
Block Hard (true 90° edges), Block Rounded, Ramp, Floor Tile, Zero-G Pad, Gravity Beacon, Crate,
Canister, Surface Drone (a custom-pawn body) and Sky Sphere. Simple collision where needed: convex
hulls, a sphere primitive for the planetoid, complex-as-simple for the tube, none for the sky.
Materials in /OmniWalk/Materials: M_OW_Master (legacy material pins, so it works with and
without Substrate: tint × detail albedo, roughness variation, detail normal, emissive) with 14
instances, including five floor-surface presets (MI_OW_Surface_Ice, _Magnetic, _Rubber, _Sticky, _ZeroG) for the surface-response presets, and M_OW_Sky (unlit starfield).
Textures in /OmniWalk/Textures: hull panels and regolith (albedo, normal, mask) and a space
panorama. They were generated with FLUX.2 [klein] 4B (Apache 2.0) and made tileable; prompts, seeds
and sources are kept outside the package.
Built by each engine. The models are generated from code in Blender
(Tools/Blender/omniwalk_models.py, outside the package) and imported by each engine
(Tools/UE/build_omniwalk_content.py) before packaging, like the demo map. The package tools check
that every kit package was saved by the target engine and kept its collision and materials.
Upgrade Notes
Hover damping default 50 → 3. A craft that relied on the old value (at a high frame rate) may need Damping set back; keep points × Damping × frame time below 2.
TurnTorque is removed in favour of MaxTurnRate, TurnResponse and LateralGrip. With no
steering input the craft now holds its heading, and sideways sliding is damped (set LateralGrip
to 0 for pure drift).
Hover force default 500 → 1000. Crafts ride about 25 cm higher; set HoverForce back for the old
ride height on flat ground (keep points × HoverForce well above the loads your tracks reach).
Track gravity follows the road surface (bSplineGravityAlongUpVector, on by default for AOmniWalkTrackGenerator). Set it off for the old pull toward the centre line.
Spider walk wraps over ledges. Characters with convex traversal on now walk down a ledge’s face
instead of dropping off it (see ).
GenerateDeadSpaceTemplate is renamed GenerateAirlockTemplate on AOmniWalkTemplateGenerator (the old
name was a third-party trademark). Same template: an artificial-gravity airlock room. It is an editor button
only (no Blueprint node), so only Python or C++ that called the old name needs the new one.
New /OmniWalk/Models, /Materials and /Textures folders (about 16 MB).
Tests (32 → 43)
Test
Checks
OmniWalk.Editor.Content.ModelKit
All 14 models load, every slot has an OmniWalk material, collision per model, OmniDrive size
OmniWalk.Editor.Content.DefaultModels
Vehicle, planetoid, track and pad defaults; hover damping stable down to 30 fps
OmniWalk.Editor.HoverVehicle.CirclesPlanetoid
PIE: settles at 47 cm, level; drives 150° around a 40 m planetoid in 10 s, 47–65 cm, up · radial ≥ 0.999