Priestess of the Moon

[FlameofChange]

This could be a good classic POTM, with the johnwar version as the special Tyrande model.

 

[DREADMAN]

Woman

 

[jj84]

that's awesome, keep it up bro.

 

[deepstrasz]

Riding the T H I C C way.

 

[Loki18]

just wow dude! great great work you got here imo
i love the new get up, the hair, stand ready and the walk animation
the whole model is lovely!
please do a Tyrande redo as well

 

[Stefan.K]

Great jAb!

 

[Golasgil]

This is amazing. It's the kind of model that makes you want add a unit or hero using it in your map.

 

[Astromen]

Love it!

 

[Nyctaeus]

Best fanmade PotM asset without a doubt.

 

[Gree-D]

You're making history on May 22nd! Hopefully dismounted version will come later.

 

[raypack]

This is good! The shining eyes and the spell animations are great!

 

[Carefree World]

The only downside is that her face is a bit old.Everything else is very nice. It would be even better if she had a pretty face.

 

[Sarsaparilla]

Hot!

 

[MasterHaosis]

Hot!

 

[Jab1z]

The only downside is that her face is a bit old.Everything else is very nice. It would be even better if she had a pretty face.

well, tbh tyrande is queen XD
you can't compare anyone to her <333

 

[Lord_Of_Outland]

Very nice re-classic model. Execution and animations are great. Good job

 

[Em!]

Some issues need addressing before I can approve the models.

• Please fix the issues listed by the sanity checker.
• Please add collision to the TC version. The other version has two collision spheres with the same pivot point. Please correct the collision pivot points.
• Please fix the right arm animation jerk when transitioning from the Death to Dissipate animation.
• Please try to reduce the polygons to around 4k

 

[Jab1z]

Some issues need addressing before I can approve the models.

• Please fix the issues listed by the sanity checker.
• Please add collision to the TC version. The other version has two collision spheres with the same pivot point. Please correct the collision pivot points.
• Please fix the right arm animation jerk when transitioning from the Death to Dissipate animation.
• Please try to reduce the polygons to around 4k

i can do all of them except for the last one, i tried it with other models of mine and it failed miserably.

Edit:
in the 3rd issue: what do you exactly mean by "jerk when transitioning..."? i checked the animation and it looks okay, i mean it's natural to find glitches during each sequence since i make them with magos model editor but i haven't heard about this kind of issue ever before.

 

[Em!]

i can do all of them except for the last one, i tried it with other models of mine and it failed miserably.

Edit:
in the 3rd issue: what do you exactly mean by "jerk when transitioning..."? i checked the animation and it looks okay, i mean it's natural to find glitches during each sequence since i make them with magos model editor but i haven't heard about this kind of issue ever before.

3rd. Yeah, I accidentally caught that while testing the dissipate animation in the game. It is probably just the arm not being in the same position where it ends in death and begins in the dissipate. You can ignore the issue if you don´t spot it; it does not break the game.
The polygon rule does bother me. You worked hard on these models. I´ll ask some questions and get back to you on it.

 

[Jab1z]

i can do all of them except for the last one, i tried it with other models of mine and it failed miserably.

Edit:
in the 3rd issue: what do you exactly mean by "jerk when transitioning..."? i checked the animation and it looks okay, i mean it's natural to find glitches during each sequence since i make them with magos model editor but i haven't heard about this kind of issue ever before.

3rd. Yeah, I accidentally caught that while testing the dissipate animation in the game. It is probably just the arm not being in the same position where it ends in death and begins in the dissipate. You can ignore the issue if you don´t spot it; it does not break the game.
The polygon rule does bother me. You worked hard on these models. I´ll ask some questions and get back to you on it.

I see, but i got to say the polygon rule didn't apply to my "Dark Willow" model which has around 6k polygons and still it received approval from the site, that's why i'm confused - because it felt like a green light for me in order to make them as detailed as possible...

 

[deepstrasz]

I see, but i got to say the polygon rule didn't apply to my "Dark Willow" model which has around 6k polygons and still it received approval from the site, that's why i'm confused - because it felt like a green light for me in order to make them as detailed as possible...

I think the important thing is, do many polygon models affect the game in any way? Do they cause graphics issues or slow down the game, whatnot?
If not, we're not in 2003 anymore, people, please.

 

[Em!]

I see, but i got to say the polygon rule didn't apply to my "Dark Willow" model which has around 6k polygons and still it received approval from the site, that's why i'm confused - because it felt like a green light for me in order to make them as detailed as possible...

Back in the day, before I learned how to model, I did not care about any issues with models as long as they did not break immersion. High polygons just meant more awesome. I am waiting for an answer, but I think there shouldn't be a problem. Site rules only state no unnecessary polygons. I think there are no such issues with your work.

 

[Em!]

Alrighty, the polies are not an issue .

(double posting might be one though "cough".)

 

[Nyctaeus]

I think the important thing is, do many polygon models affect the game in any way? Do they cause graphics issues or slow down the game, whatnot?
If not, we're not in 2003 anymore, people, please.

Geometry itself is very light both in terms of filesize and rendering performance on any engine. In the end, it's the GPU doing the work. In modern engines, assets between 10k-100k tris are considered lowpoly and desirable polycounts. I produced vastly heavier objects, like 700k tris for ingame usage and those were still lowpoly objects.

Not that WC3 engine is optimized to handle this kind of assets, but I guess multiple objects of about 10k tris [even units] would actually work well. Exodus 2 features tons of WoW ports to create the enviro, and maps have no related performance issues. It's not an excuse to go completely stupid with polycounts and keeping things as optimized as possible is always the way, but I see no reason to stick to outdated dogmas.

Still, WC3 probably does not calculate in-engine collisions based on geometry. Afaik it uses extents or collision meshes of much lower polycounts, so there are ways to optimize collision further. I frequently see moderators of Hive recommending ppl to add collision meshes. This is very good practice.

What really cloggs GPU memory is bitmaps. Tons of textures of high resolutions, overambundance of particles etc.

Tl;dr - I'm not a specialist when it comes to making assets exactly for WC3, but as asset designer doing 3D for living, I can rather conviniently say that Jab1z's assets are perfectly fine in terms of polycount and... Geometry is sexy :]. I feel rather inclined to encourage modellers around to go above vanilla WC3 polycounts.

 

[Jab1z]

Geometry itself is very light both in terms of filesize and rendering performance on any engine. In the end, it's the GPU doing the work. In modern engines, assets between 10k-100k tris are considered lowpoly and desirable polycounts. I produced vastly heavier objects, like 700k tris for ingame usage and those were still lowpoly objects.

Not that WC3 engine is optimized to handle this kind of assets, but I guess multiple objects of about 10k tris [even units] would actually work well. Exodus 2 features tons of WoW ports to create the enviro, and maps have no related performance issues. It's not an excuse to go completely stupid with polycounts and keeping things as optimized as possible is always the way, but I see no reason to stick to outdated dogmas.

Still, WC3 probably does not calculate in-engine collisions based on geometry. Afaik it uses extents or collision meshes of much lower polycounts, so there are ways to optimize collision further. I frequently see moderators of Hive recommending ppl to add collision meshes. This is very good practice.

What really cloggs GPU memory is bitmaps. Tons of textures of high resolutions, overambundance of particles etc.

Tl;dr - I'm not a specialist when it comes to making assets exactly for WC3, but as asset designer doing 3D for living, I can rather conviniently say that Jab1z's assets are perfectly fine in terms of polycount and... Geometry is sexy :]. I feel rather inclined to encourage modellers around to go above vanilla WC3 polycounts.

i see, thank you for your explanation
also thanks for your compliments. well yeah i have a plan to use more modern apps later.

 

[diosdadolinares5]

Ooooo¡ The animation of Stand Victory is great. Could you add the animations of the priestess coming down and up from the tiger?

 

[kadakash1]

Nice model

 

[Jab1z]

i see, thank you for your explanation
also thanks for your compliments. well yeah i have a plan to use more modern apps later.

Nice model

View attachment 482430

Oh dear lord xDD

 

[Nyctaeus]

Lel, I just realized that Priestess and tiger were a single, manifold mesh before your rework and you had to separate them, fill the holes of both meshes and do other modelling shinenigans to make Stand Victory anim possible. Noice werk.

Now she asks for mountless version methinks.

 

[Jab1z]

Lel, I just realized that Priestess and tiger were a single, manifold mesh before your rework and you had to separate them, fill the holes of both meshes and do other modelling shinenigans to make Stand Victory anim possible. Noice werk.

Now she asks for mountless version methinks.

well, yeah i originally had the plan to create a dismounted version of her, but that would've been a bit of too much work.

 

[Luu]

I loved the model and I'm going to use it on my map. I'm a big fan of your work, one of my favorite artists

 

[Em!]

Excellent work. Changes made, resource approved.

 

[Deolrin]

I love that Stand Victory pose. Well done!

 

[BaiyuGalan]

Very beautiful tiger and good animation.

 

[taiga01]

Well done!