Simulation Tooling

DXCenter

A Unity authoring environment for digital-twin style workflows, built around nine EditorWindow tools and an operating structure that reduced repeated manual setup for non-developer teams.

Unity 6 LTS EditorWindow UI Toolkit Authoring Flow

Role

Designed the authoring structure, implemented the tool windows, and tied data mapping and runtime behavior into one editable workflow.

Problem

Teams were paying repeated cost whenever content structure, mapping, and validation had to be rebuilt manually.

Outcome

Created an editor environment with consistent windows, reusable mapping rules, and a runtime path that non-developer teams could actually use.

Why It Matters

This is strong proof of tooling ownership: not just runtime development, but reducing operational friction for the people who maintain the content.

Before / After

Turning repeated setup into a stable operating flow

The value of DXCenter is not just the number of windows. It is the fact that those windows formalize how data, endpoints, topics, and UI mapping move through the authoring flow.

The result is a system where repeated setup work becomes a tool-guided process instead of a fragile manual chain. That is the difference between a one-off editor and a real production tool.

Named tool surface: the editor stack is built around nine windows rather than a single overloaded inspector flow.

Mapping logic: DataMappingWindow is a good example of the project’s value because it turns protocol, endpoint, topic, and UI mapping into an explicit structure.

Operating safety: the tool is meaningful because it lowers the chance that content changes break the runtime in hidden ways.

Roles: simulation tooling, editor platform, digital twin, and authoring workflow.