Drag a model in and it becomes a scene

Connecting "assets from outside" to "editing inside"

After the editor wrapped up over the preceding days, what this day added was the intake it most deserved yet had been missing: bringing in assets made outside. However powerful a creation tool, if it can only use what it generates itself, the creator's asset library is locked into a small circle; true openness is being able to pull in models and textures made anywhere and keep using them. The day had just this one main line, but a weighty one — letting the editor "ingest" a standard 3D model file and turn it into a scene you can keep arranging. Around it, the backend opened a few new entry points and the front end added an import menu, while the same day also swept away a long-accumulated pile of instability in the editor's multi-window operations at once and fixed a once-broken sky display. In a word: this day both opened "assets can come in" and made the editor itself "stable to use."

Drag a model in, and it becomes a scene

The day's core capability: drag a 3D model file into the asset panel and it's automatically broken down into an editable scene. The prior pain was concrete — a standard model file isn't an isolated blob of geometry; inside it usually carries full structure: a node parent-child hierarchy, individual sub-meshes, attached lights, even preset cameras; but on import those structures were often all lost, leaving you a single opaque, immovable lump. The approach now: the backend runs model parsing on demand and translates the model's internal node tree faithfully into that "document-driven" scene — whatever hierarchy, lights and cameras the model holds, the scene restores the corresponding objects, one-to-one, individually selectable and editable. An import dropdown was added to the editing surface for common model, texture and scene-pack formats; the backend opened three steps — uploading binary assets, parsing the model on demand, and breaking the node tree into a scene document — to wire the path through, and the asset panel auto-refreshes after import with no manual reload. For creators this means a whole scene or a rigged character you sculpted externally can be dragged in and arranged and tuned right away, rather than rebuilt from scratch.

Detaching panels no longer misbehaves: a docking overhaul

This day gave the editor's panel docking a thorough overhaul, clearing in one go a long-accumulated pile of "glitchy" behavior. The prior pain: multi-window operations were full of traps — dragging a panel like the inspector out into its own OS window, then closing that window, or undoing/redoing in a detached panel, could all glitch, misalign or even freeze. The root cause was the docking's deeply-nested internal structure with hard-to-track state. This day changed it to a "flat structure": preview and edit were promoted to top-level independent panels, and flattening the hierarchy made behavior predictable. On this new structure, a string of specific bugs were fixed one by one: dragging a panel to empty space cleanly pops it into its own window instead of vaguely floating within the app; when an independent window is closed, the panel inside dutifully returns to the main interface; and undo/redo finally works in detached panels. Visually, the somewhat harsh blue tab highlight was swapped for a neutral dark tone, and panel names were tidied and unified. The multi-window workflow went from "usable but nerve-wracking" to "genuinely stable."

The skybox returns: HDR environment-map import fixed

A while back, the chain responsible for loading HDR environment maps had broken for a stretch, with the direct consequence that the sky in scenes went black for a time — sky light and ambient atmosphere all gone. This day restored the whole environment-map import and loading path, so the HDR sky renders correctly again in both edit and play. It's worth explaining why this matters: an HDR environment map isn't just "drawing a pretty sky backdrop"; it's simultaneously the lighting source for the entire scene — what color the sky is, where it's bright and where dim, naturally falls on every object in the scene and decides the whole image's light and shade, warm and cool. So when the sky goes black, what's lost isn't just the backdrop but the scene's "atmosphere of light." Restoring this chain relights the scene's "soul lighting." It's also a reminder: the more a foundational chain affects everything downstream, the more it needs regression protection, lest it quietly break again with no one noticing right away.

Laying groundwork for "placing many copies of one model"

The engine also did a performance-paving thing underneath this day: wiring several shaders to a dedicated "per-instance transform" channel. What does this mean? Many game scenes feature heavy repetition of the same model — hundreds of trees in a forest, rows of bricks on a wall, a crowd of identically-shaped enemies. The naivest approach redraws the model one by one, but that cost balloons linearly with count and a large scene stutters. The more efficient approach is "instancing": the same model is handed to the GPU just once, attached with a list of "each copy's own position, orientation and scale," letting the GPU draw hundreds or thousands of copies into their places in one pass. This day wired several shaders in the scene to this per-instance data channel, aligned shadow drawing with it, and added regression protection. This is the kind of under-the-hood work users don't see but that directly decides "how big a scene can be stacked and how smoothly it runs" — not a feature in itself but the precondition that makes many later "large-scene" features possible.

What this day means

If the preceding days were about "building the editor up," this day was about "running its water and power and firming its foundation." The import capability makes the editor no longer an island that can only use its own materials but an open workbench that can take in external assets and keep creating on top of them — a step that vastly broadens the range of materials creators can use. The docking overhaul is value of another kind: it added no new feature, purely polishing what existed from "usable but often glitchy" to "solid in use," and that solidity is exactly the foundation on which a professional tool earns long-term trust. With the return of sky lighting and the groundwork for instanced rendering, this day pushed the editor's "intake, stability, visuals, performance" four facets forward a notch at once. It reminds us: a tool matures by both continually growing new capabilities and continually going back to firm old ones into true reliability — neither dispensable.