UDK/UT3 Video Tutorials List and Support Thread

[PsychotropicDog]

The mesh was parented to the armature - empty groups, then the verts assigned. Yes I checked. a lot.
There is no other way I know to find the weights of the verts besides having them in seperate vertex groups, and 'N' properties in 3D viewport with a single vert selected also shows that vert's group(s) weights.
There is something odd going on.

tried blender 2.60a .. it doesn't like newer blends; didn't work. to test 2.60a, I will have to import as obj, rebuild the armature blah blah blah. Later.

edit: started a thread in reporting forum.

[geodav]

just tried with blender 2.64_RC2 and get the same problems !!!!!!

[PsychotropicDog]

Well I was going to take a nap, but it's niggling at me, so maybe I will try FBX morphs and see if this problem creeps into them as well.

Edit:
yes, you can get this same strange behaviour with FBX morphs.
It seems to involve the 'update morphs' function that automatically crops up.
Sadly, unlike (maya2009) actorX psk's and FBX 2013 morphs that can be deleted and simply re-imported to fix, I can not get this type of work around to work with blender's psk exporter.

[geodav]

looks like we need to speak to the blender people to fix the exporter but before we do that let me try something else

nope that worked fine !!!! there must be some sort of problem between blender and udk as the blender morph loads fine as a normal mesh ?

[PsychotropicDog]

looks like we need to speak to the blender people to fix the exporter but before we do that let me try something else

nope that worked fine !!!! there must be some sort of problem between blender and udk as the blender morph loads fine as a normal mesh ?

You mean as a static mesh or a seperate skeletal mesh? Err, it should load fine...
Sure there 'might' be a problem with the psk exporter, I am not ruling that out, but it concerns me that the very same behaviour happens with FBX importing - which leads me to guess that there is something odd in the way UDK handles vehicle morphs.

[geodav]

i did a quick test last night and i couldn't get the fbx morph to load at all, i'll try some simple meshes in older blenders to where the problem started and then report it to the blender people

ok hear is what i've just tried, in 2.60a i made a sphere+rig+uvw map saved 2 files
1. Clean
2. Damage
exported using the blender Unreal Tools , the morph worked fine
using the same files it all works in 2.60a 2.61 2.62

guess i'll have to report it tomorrow when i have a bit more time

[geodav]

ok just re-created the same mesh in blender 2.63a and did the morph, so far everything worked fine

Darknet mentioned if you have moved your mesh from 2.62 or before you might try to rebuild the armature as this could fix the problem
or the unlucky fact that the new blender mesh system breaks the old meshes in some way

[DemoMan2]

For what it's worth I've been having trouble importing a new vehicle skeletal mesh using Blender 2.63 & 2.64 into UDK. It seems that many of the faces just disappear. It doesn't seem to matter if I use .FBX or .PSK formats. I have no idea why this is happening.

[geodav]

basically what i did was to make a sphere then uvw map, apply material/texture, add an armature with 3 bones and skinned it, then exported the mesh via the udk tools as a psk, after that i made a simple morph-target exported as psk both imported fine.
darknet thinks this could be a problem with the new bmesh system in blender which was introduced with version 2.63 atm the best thing to do is use 2.62 or register on the blender site and report the bug.

as and when i get time i'll try a more complex mesh/rig

[DemoMan2]

Well, I gave Blender 2.62 and 2.61 a go and neither of them where able to fix the problem. It's probably something I did with the mesh that just sort of blew UDK's mind. BTW, I am using July 2012 UDK.

[DemoMan2]

Now that I think about it, I started building this vehicle model using Blender 2.63 so the problems may be in the .blend file. If that's the case it would explain why even the older version of the program can't translate the model correctly. Of course, it could also just be a lose nut at the keyboard issue as well. I am still pretty new to 3D modeling.

[PsychotropicDog]

Blender 2.64 has been released.

[geodav]

as we say "it's the nut behind the steering wheel thats causing the problem"

an old mechanic's joke

hope to have a bit more time later in the week to see if we can solve the problem

[DemoMan2]

as we say "it's the nut behind the steering wheel thats causing the problem"

an old mechanic's joke

hope to have a bit more time later in the week to see if we can solve the problem

That reminds me of a phrase that I heard many years ago when I used to do computer consulting for the National Park Service.

"Just when you make your software foolproof, along comes a better fool"

Sort of says it all. And yes I did try to export the model using Blender 2.64 but the results are the same. One thing I did do is use the mirror modifier on the body of the vehicle which is where most of the faces got distorted in the translation process to UDK. Are there any good sites that show how to fix common 3d modeling problems? Perhaps it's something simple that I just don't know how to fix yet.

[DemoMan2]

Btw, here's a couple of pictures of the model. First picture is from Blender, second one from UDK.