Hermoor's monsters

[xxxxxxxxxxxxxxxx]

While bored, I decided to rig up the Horse Man. I'm willing and capable of animating him. I already have a walk and run cycle, as well as an idle. I'm still need to make some attack animations. Any suggestions?

When I get it to work properly, I'll upload it for the community. Odds are I have to restart the rigging process, as the model goes all....ooglywoogly, when the motion starts.

Yeah! Horseman is my favourite of the bunch, design-wise. Can't wait to see him animated.

Ooglywoogly? How exactly? A skinning problem or funky joint orientation? A pesky gimbal lock? For some strange reason, I love doing troubleshooting, just tell me some details (or send me the file...)

If it's a just problem with the skinning, you don't necessarily need to skin it again. If you still have a version where the skinning is fine you can import the animation into that file either as animClip via trax editor (in that case you can't really edit it anymore though) or with the awesome dkAnim script. (using mayas native anim export is not recommended -.-)

[Acies]

While bored, I decided to rig up the Horse Man. I'm willing and capable of animating him. I already have a walk and run cycle, as well as an idle. I'm still need to make some attack animations. Any suggestions?

When I get it to work properly, I'll upload it for the community. Odds are I have to restart the rigging process, as the model goes all....ooglywoogly, when the motion starts.

Yeah! Horseman is my favourite of the bunch, design-wise. Can't wait to see him animated.

Ooglywoogly? How exactly? A skinning problem or funky joint orientation? A pesky gimbal lock? For some strange reason, I love doing troubleshooting, just tell me some details (or send me the file...)

If it's a just problem with the skinning, you don't necessarily need to skin it again. If you still have a version where the skinning is fine you can import the animation into that file either as animClip via trax editor (in that case you can't really edit it anymore though) or with the awesome dkAnim script. (using mayas native anim export is not recommended -.-)

Would you be interested in exploring amnesia's support for animations? Sometimes exports viewed in game appears choppy, as if skipping a few frames. Would you have any clue to why?

[Obliviator27]

While bored, I decided to rig up the Horse Man. I'm willing and capable of animating him. I already have a walk and run cycle, as well as an idle. I'm still need to make some attack animations. Any suggestions?

When I get it to work properly, I'll upload it for the community. Odds are I have to restart the rigging process, as the model goes all....ooglywoogly, when the motion starts.

Yeah! Horseman is my favourite of the bunch, design-wise. Can't wait to see him animated.

Ooglywoogly? How exactly? A skinning problem or funky joint orientation? A pesky gimbal lock? For some strange reason, I love doing troubleshooting, just tell me some details (or send me the file...)

If it's a just problem with the skinning, you don't necessarily need to skin it again. If you still have a version where the skinning is fine you can import the animation into that file either as animClip via trax editor (in that case you can't really edit it anymore though) or with the awesome dkAnim script. (using mayas native anim export is not recommended -.-)

The problem with him is somehow the weight painting goes off. I'm not sure how or why, though. I've redone it at least four or five times.
When he moves after importing into the HPL engine, his vertices explode all over the place. This doesn't show up in Maya, so I really don't know what the issue is. After tackling it a few different times, I think it has something to do with the program it was modelled in. I'm not sure, though.

[xxxxxxxxxxxxxxxx]

Would you be interested in exploring amnesia's support for animations? Sometimes exports viewed in game appears choppy, as if skipping a few frames. Would you have any clue to why?

Well, problem is I've never even taken a look at the HPL engine (I'll make sure to do that once I have a bit more time though), I only know my way around Maya and UDK (a bit) :/.

So I can only take some wild guesses here... skipping frames could maybe be a problem with animation compression either while exporting or in the engine itself. Are there any settings for that in the engines editor you use to view the animation or maybe while ex- or importing the file?
You could also try baking the animation prior to exporting. This will put a keyframe on every frame, so the exporter/ engine won't have to interpret your animation curves and tangents anymore.

It could maybe even be that the engine uses a different number of frames per second than what you were using in maya. Standard in maya is 24 fps, but UDK for example uses 30 fps so it's best to change that in maya before exporting or your animation might look different in the engine. (Maya can change the fps while keeping the speed of your animation constant, it will then just move the keyframes accordingly.)

When he moves after importing into the HPL engine, his vertices explode all over the place. After tackling it a few different times, I think it has something to do with the program it was modelled in. I'm not sure, though.

What if you import your exported file into Maya again instead of HPL? Does it show up correctly then?

You could also try maya's cleanup-function. (mesh>cleanup) It will tell you for example whether the mesh has non-manifold geometry (that's for example an edge with more than two faces attached to it) or other problems. Stuff like that can cause problems in an engine and sometimes the mesh errors are almost invisible to the bare eye.

Also have you already tried the crazy stuff like duplicating the model and deleting the original or going into sub-object mode, duplicating all faces and detaching them as a new mesh? =D Weird tricks like that really help sometimes if there's a problem with the mesh!

If you're using a newer version of Maya (not sure since which version this was included), you could also check the "normalize weights" options of your skinning (can be found in the attribute editor of the mesh under the "skin cluster" tab). It should be set to "interactive" , if it's set to "post", you can run into all kinds of problems. (Had a lot of trouble with this pesky option myself before I figured that out ) This is because "post" allows a vertex to have a combined skin weight of more than 1. I guess this could confuse an engine if for some reason it gets exported like that. (It shouldn't but you never know)

Hm...another reason could be that you have too many joint influences per vertex for the engine to handle. Maybe try a quick 'n dirty smooth skinning with only 1 or 2 influences allowed and see if the bug is still there?

Well, that's all I can think of now. Maybe I'll get some more ideas later

[Lake]

sorry but I do not work, but I put in the entities in the level editor does not appear

[Ank2503]

I like it =)

[Ongka]

It's because the .dae files are missing some entrys and the texture is a .png instead of a .dds
You gotta convert them by yourself.

[Lake]

It's because the .dae files are missing some entrys and the texture is a .png instead of a .dds
You gotta convert them by yourself.

I converted but the monster still does not exist

[Danny Boy]

It's because the .dae files are missing some entrys and the texture is a .png instead of a .dds
You gotta convert them by yourself.

I converted but the monster still does not exist

you probably haven't made a mat file

[The chaser]

The Vitra is very scary... It would give me a heart attack if i saw THAT on a CS.