-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSA animations distort some meshes from corresponding PSK #75
Comments
is there ".config" file near ".psa" file? if so, i want to look at them (psk/psa/config) |
Don't see any .config files, got a json?! , This is exported using fmodel if that helps |
oh. its fortnite. so... i think the problem is on the exporter's side(?) |
thanks for looking, I'll look into export... |
Can you tell from the psa and psk if some bones or the deformation have wrong "scale" or something? Is there a way/tool to dump the animation? I'll see if I can find a model that was previously exported with different tool and compare |
It's not. I'm having deformity problems too but they're much more severe. On 3.0, skeletons do not import correctly (as someone has already pointed out), .PSAs cannot be imported (again, as someone has already pointed out), and in older versions of blender (I installed 2.82 in hopes the importer would actually work), meshes get squashed into balls like they're made of paper whenever anims are applied. I do have a .config file. Would you like me to send it over? I'm getting sick of having to constantly open Max in order to get things to import/export correctly seeing as I don't actually have any other use for Max. |
Blender 2.93.5
addon 280 version
Is it a know issue where some fortnite meshes get weird distortions from deform bones, especially in facial animations.
![image](https://user-images.githubusercontent.com/47461175/143780354-2a3f7d6a-43dd-42ae-aba5-ccace76783ee.png)
Unchecking deform on the individual problem bones puts helps, but undoes and deformation that the bone is supposed to make
eg
The text was updated successfully, but these errors were encountered: