Wundur Studio

Log ·

Game assetsProjects

A guided path for game assets, and sessions grouped into projects

Most of the morning went into a new way of making game assets, and the rest of the day into how sessions and panels are arranged.

A guided path for each game asset

New game asset… in the chat's menu puts a short form in the chat: a name and what kind of thing it is. Create turns it into a card for that asset, and the card walks it through the steps, with you deciding at each one.

  1. Concept. Quick low-resolution tries from your description. Pick one, ask for a change in your own words, or try another.
  2. Views. Front, side and back of the chosen concept, a character standing in an A-pose. All three are asked for together, and each can be redone on its own until it's right.
  3. Model. A 3D model built from the approved views. Each try shows a preview and a View in 3D button, which opens the model in a viewer beside the chat. Approve one to move on.
  4. Rig comes next. It isn't part of the path yet.

Everything is saved in your project, in a folder for the asset (assets/characters/knight/, for example), with a record of every try: what was asked, what it was made from and what you approved. The card comes back when you reopen the session, and Open on the card shows the asset's whole history in a tab. The pictures and models come from the game-assets pack, with your own keys.

The card was redrawn later the same day to be quieter. It has a small header with a Concept, Views, Model, Rig stepper that ticks off finished steps, larger pictures with a check on the chosen one, and a shimmering tile where the next picture is being made. Each step has one main button, with Another and Change beside it. The cost of each try is still recorded in the asset's record, but no longer shown on the card. If the image service says it's busy, the request waits as long as asked and tries again.

Sessions grouped into projects

The session list groups sessions by project. By the end of the day, every folder that has sessions counts as a project on its own, with nothing to set up. A session in a folder inside another goes under the outer one, and sessions on another machine get a project for each folder there. A project's row folds, shows what its sessions are doing, and has a + for a new session in its folder. The list is headed Projects.

Each session's row now says what it's doing in words where its cost used to be: Working, Needs you or Agents working. Under its title it shows its place in the project: a deeper folder, its branch, and how long ago it last did something. The folded rail and the list that peeks out over it group the same way, and a project's mark there can be renamed or removed with a right-click.

To jump to any session, type part of its name or its project's in Session > Go to Session…. It started on Cmd+K and moved to Cmd+P the next day, so Cmd+K could clear a terminal again.

The tool panels move under the list

Files, Changes, Agent and Skills used to live inside each session's own layout. They now sit in the window's left column, under the list of projects, as tabs along the bottom, with a divider to give either half more room. Cmd+B shows or hides them. The column itself is wider, and you can drag its right edge to anywhere from 200 to 520 wide. Layouts saved before this open once in the new arrangement.

Smaller things

All entries