Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Midnight-shcode3023248dtbh, finding the right export settings for any engine is usually pain in the ass.
thebiochemic184248dHad made rigs in Blender 2.79 for Unity5 back then. That was pretty painless actually, the only thing was the naming.
UE is still on my list though
Midnight-shcode3023247d@hasu well... maybe i'm weird but i saw nothing wrong with the solution of "do five trial and error exports+imports with different settings, find the one that works, note it down, never change it again" =D
... yeah, i definitely am weird, all the info needed for the importer to import correctly should be embedded in the file itself, now that i think about it...
hasu2524200dfyi I found a solution. Lol. So my meshes had the same names as the links, which is fine for blender since it knows those are different objects, but not fine for Unreal. Lol.
Also it didn't like multiple layers.
Now that I prefixed every mesh with "mesh" and removed the layers it imported fine.
Now I'm mad about Unreals definition of Bones though. Had to rework my entire fking model because of this. fk this shit :D I want to cry... and don't get me started on IK constraints... ugh