We build assets that bring games to life
Lamiseton started in 2015 with a simple goal: helping indie developers and studios create 3D models that actually work in production.
Over the years, we learned that good modeling is about understanding game engines, optimization constraints, and what players notice. Technical precision matters more than artistic ambition when a model needs to run smoothly across different platforms.

Who makes it happen
Two people who understand both the artistic side and the technical requirements. One codes, one sculpts, both know how polygon count affects frame rate.

Kieran Blackwell
Spent eight years optimizing character rigs for mobile games. Now ensures every model we deliver loads fast and animates cleanly without shader errors.

Isla Thornby
Worked on asset pipelines for three different game engines. Balances visual quality with performance constraints so models look good without killing the frame budget.
How we got here
Project Growth
We started with small character commissions for mobile puzzle games.
Most clients needed assets fast, so we built templates for common character types and weapon categories. That meant less time modeling from scratch and more time refining topology for different LOD levels. Every project taught us something about export formats, normal map baking, or UV layout optimization.
The work changed as game engines improved. Unity and Unreal added better PBR workflows, so we adapted our material setups. Clients needed assets that worked across PC, console, and mobile without separate versions. That required understanding texture compression, draw call batching, and how different platforms handle transparency.
Now we handle everything from stylized environment props to realistic vehicle models. The technical requirements vary, but the core principle stays the same: models need to look good and perform well in actual gameplay, not just in renders.


Technical First
Every model is built with game engine requirements in mind. We test assets in Unity and Unreal before delivery to catch issues with import settings, collision meshes, or material slots.

Practical Delivery
Models come with proper naming conventions, organized hierarchies, and documentation for material setup. No guessing how to implement assets or fix broken references.

Performance Balance
We optimize for target platforms without compromising visual quality. That means appropriate polygon density, efficient UV layouts, and texture sizes that make sense for the intended use case.