Ragnok Bloodreaver

[deepstrasz]

Greato stuffo!
Particular animations and looks.
One can never be tired of death knights and this one is a mix of the Warcraft II and III ones.

 

[DREADMAN]

"The heartthrob"

 

[deepstrasz]

The heartthrob"

 

[MasterHaosis]

This is awesome! Pure awesome. I like faces of him and that horse
Oh, I am getting ideas from this model.

 

[StonemaulMidget]

Straight out of the comics, I say! Great job, my man!!

 

[CGCyan]

Got plans for Gaz Soulripper?

 

[Lefroit]

He's here! Another fantastic model.

 

[Lord_Of_Outland]

Thank you for sharing such a good and useful models!

 

[Thrall Zadeera]

Portrait - 4: as if he is saying for all Warcraft:

 

[kangyun]

great as always

 

[BaiyuGalan]

Got plans for Gaz Soulripper?

No, he doesn't have any photos, and there are very few stories about him. Any Death Knight model can replace him.

 

[KaiZen7th]

That's a lord Teron I would love to meet!

 

[Tryndamere]

Peak model for Death Knight

 

[Jab1z]

That's a very nice model and texture right there! 5/5

 

[Villagerino]

A definitely cool variation of the Death Knight, a good addition for the SD+ detailed maps and models, love the Spell Slam sequence
I understand that animating heroes with mounts is painful though I'd love to see a bit more natural moves

 

[Carefree World]

A novel and good model.

 

[Nyctaeus]

Peak of SD asset making. Excellent design and very faithful recreation of the source material. He's hella creepy and invoking anxious feelings. Definitely a valid DC candidate.

 

[paladinjst]

Finally it comes ~

 

[789789]

Wow, it's so handsome

 

[ILH]

Box collision shapes should be used for buildings only, please change the collision shape to spheres.

 

[Lefroit]

Box collision shapes should be used for buildings only, please change the collision shape to spheres.

In-game Lich, DK, Archmage and many more use box collision shapes. How did you come up with this weird rule that restricts box collisions?

 

[ILH]

In-game Lich, DK, Archmage and many more use box collision shapes. How did you come up with this weird rule that restricts box collisions?

From personal experience where box collision shapes would often makes the units "unselectable" when moving in certain places.

 

[Commedia]

From personal experience where box collision shapes would often makes the units "unselectable" when moving in certain places.

I've never heard about this. In fact, it is vanilla war3 DeathKnight that uses box collision shape.

Could you give some examples that units with box collisions become unselectable?

 

[ILH]

I've never heard about this. In fact, it is vanilla war3 DeathKnight that uses box collision shape.
...
Could you give some examples that units with box collisions become unselectable?

Here's a recent example (Hussite War Wagon), where you can't select the horses in-game. Another thing about collision boxes that I know is that they aren't included in extent calculations. You can test it by making a giant collision box, calculate extents, and try to select it in-game.

The point of the collision sphere is to allow the player to easily click on the unit in-game, especially in the case of slim models.

If you have any further concerns feel free to ask me either through my profile or privately.

 

[Lefroit]

Here's a recent example (Hussite War Wagon), where you can't select the horses in-game. Another thing about collision boxes that I know is that they aren't included in extent calculations. You can test it by making a giant collision box, calculate extents, and try to select it in-game.

The point of the collision sphere is to allow the player to easily click on the unit in-game, especially in the case of slim models.

If you have any further concerns feel free to ask me either through my profile or privately.

The problem with Hussite War Wagon unselectable horses is because author misplaced collision shapes, not because they're boxes. You can look it up in sanity test.

 

[Commedia]

Here's a recent example (Hussite War Wagon), where you can't select the horses in-game.

This is because the author didn't set the pivot point of the collision shape nodes properly. As Lefroit showed, you can check it in the sanity test.
For collision shapes, the selectable range is not only decided by collision-shape-specific data (the two vertices for box, the center and radius for sphere), but also the coordinate of node pivot point.
So this is not a issue caused by box collision shapes. Using a sphere collision shape with misplaced pivot point will also cause it.

Another thing about collision boxes that I know is that they aren't included in extent calculations. You can test it by making a giant collision box, calculate extents, and try to select it in-game.

What will this cause? I tried it as you told but nothing weird happened. The model's selectable range is correct as the giant collision shape delineates.

 

[ILH]

An intricate piece of work for a death knight.
Changes made. Works in-game. Approved!

 

[Villagerino]

Feels like Gluma's portrait geosets here like long narrow face, mustache, beard and frown would be a perfect fit for your skin

 

[venger07]

I love how it has no mount version! Fantastic work!