About Nubble

Why Nubble is being made

Large 3D suites serve film, engineering, animation and simulation at once, and earn their complexity doing it. That breadth costs the most for someone who just wants a crate, a tree and a character for the game they are building this month.

Nubble does one job: low-poly modeling for game assets. Fewer menus to search, fewer modes to remember, and a shorter distance between opening the window and having something you can export.

What Nubble deliberately leaves out

No animation or rigging, no dynamic-topology sculpting, no path tracing, no node-based material graphs, no scripting API, and Windows only.

Every dependency is vendored rather than fetched, so the build has no package manager and no network step. That is why the download is one executable and a folder.

Built by one developer

Nubble is written by one person, not a company. Progress happens in milestones rather than on a schedule, there is no support contract, and there is no release date yet.

That is also why the scope is drawn tightly. The project keeps a log of what shipped in each milestone and what was deliberately not built.

What is next

The near-term goal is a complete first pass of the modeling loop: model, unwrap, texture, export. UV editing and texturing are in progress; painting and image effects come after.

Contact

Questions and bug reports are welcome, especially while the interface is still settling.

support@nubble3d.com