Demon Commander

Scenes that want a winged demon standing in the middle of them

A boss arena, a corrupted cathedral interior, the last chamber of a dungeon run. These are the rooms where a character has to hold a silhouette from across the space and still read as a threat up close. Demon Commander is built for that slot — a demonic, monstrous figure that the tag list files under beast, mutant, undead, reaper and monster, with wings and a dark, horror-leaning tone running through it.

It is a character rather than a set dressing piece. The tags also carry character, script and animation blueprint, which places the asset on the gameplay side of a project instead of in the background decoration layer.

The tag cloud reads almost like a scene brief

Beast, demon, mutant, undead, reaper, monster, wing, dark, horror, fantasy, death, realistic, lowpoly. Read together, that is a fairly specific brief: something dead or death-adjacent, something that was once alive and is now bigger than it was, and something with wings that changes its footprint in a frame compared to a humanoid. A winged silhouette occupies vertical space, which matters when you are staging a confrontation and need the camera to feel crowded.

The remaining tags — pbr, character, script, animation blueprint — say less about mood and more about how the asset behaves once it is loaded. Animation blueprint and script are integration signals. This is not a static mesh waiting for a turntable render.

14,520 vertices and 24,210 triangles

Those are the numbers to plan against. The vertex count lands at 14,520 and the triangle count at 24,210, which is the figure that actually affects your lighting and shadow budget once the character is instanced into a scene. The tag list calls it lowpoly, and both figures coexist with that label — the practical move is to treat 24,210 tris as the real cost per instance and decide how many Demon Commanders a scene can carry before you start blocking out the encounter.

Wings complicate that calculation in ways a torso does not. They project outward and upward, catch rim light, and throw shadows over a wider area than the rest of the body. If the scene places several of these creatures, the wings are what will define the shadow footprint, not the mesh density of the chest.

Three materials, eight maps, 4K metal/roughness

The texture set follows a PBR metal/roughness workflow at 4K, delivered as eight texture maps across three materials. The maps named cover normal, metallic/roughness, base color and ambient occlusion. Splitting the character into three materials means the surface treatment is broken into parts rather than handled as one continuous shell, which is worth knowing when you are deciding whether to swap a material instance for a variant of the creature or keep the original setup intact.

Because the maps are authored at 4K, close-up framing is viable — a hero shot of the face, a slow camera push during a confrontation. The trade is texture memory, so a scene that spawns many instances may want to reconsider how the full-resolution set is applied at distance.

The two-sided shader note is part of setup, not a footnote

One instruction sits apart from the rest of the technical detail: the model is meant to be displayed with a shader that renders polygons from both sides. That is a material and shader setting rather than a texture, and it belongs on the checklist before any look development begins. Get it wrong and the surfaces facing away from the camera will not draw the way the model intends.

It is the kind of detail that costs five minutes at the start of a project and a confusing afternoon if it is discovered later, after lighting has already been tuned around a shader that culls back faces. Set it first, then build the rest.

A UE4 skeleton, and what that means inside UE5

The rig comes from UE4. Anyone working in UE5 gets a direct heads-up on that point rather than a promise of native behaviour in the newer engine. Treat the skeleton's origin as something to resolve early — before animation work is scheduled, before an animation blueprint is wired up, and before the character is dropped into a test level and assumed to be ready.

That single sentence is the most consequential line in the whole description for a UE5 team, and it is easy to skim past because it arrives first, before the texture and geometry figures that people usually scan for.

Sitting alongside Demoness Girl Pack 2

Demon Commander is compatible with Demoness Girl Pack 2. If that pack is already part of a project, the compatibility is worth checking against your existing setup rather than assuming two separately sourced characters will sit together without attention. A project running both has a reason to verify how they line up before committing scene time to either.

Who gets the most out of it

Teams building dark fantasy or horror encounters need a creature that carries a scene on presence alone — wings, mass, a death-and-undead theme — and can be animated rather than posed. The animation blueprint and script tags, combined with a real skeleton and a full PBR texture set, point at that production need specifically.

Anyone on UE5 should plan the skeleton question into the schedule from day one. Anyone on UE4 has a shorter path. Either way, three setup items decide how smoothly the character lands: the two-sided shader, the 4K material split, and the rig origin. Handle those and the rest of the scene work can proceed on the assumption that the demon will behave the way it looks.

Continue Browsing Similar Packs

• Young Imp
• Yokai
• Demon 10
• Otherside beast
• Medical Worker 01