-
Notifications
You must be signed in to change notification settings - Fork 30
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
"mdl corrupted: header 2 misaligned or out of bounds" on MDL Import #189
Comments
something tells me this is either a needed thing and my |
Could be that the mdl formats you have are not supported, since there are different versions etc. |
Different Plumber versions or Blender, SFM? |
Mdl version. Most common ones should work but there can be something I haven't seen and tested before. |
Alright. I get my models from SFMLab, and usually import via drag-and-dropping the "models" and "materials" folder into the |
Unfortunately there's probably nothing you can do. Would be interesting to see if you are able to decompile the model using Crowbar. If that fails too, could also be that the model is somehow protected against decompilation/importing. In any case, even that should be possible to work around. If you have any "normal" models that have the issue and that you're willing to send, I could take a look some time to see if they can be supported. |
Managed to apparently "Decompile" the model I aimed for in Crowbar from the same directory. I'll try finding a model that'll break that's normal and I'll send it here. |
|
Describe the bug:
On trying to import most of my SourceFilmmaker
usermod
.mdl's, I get an error sayingcould not import mld: model '[path directory]' mdl corrupted: header 2 misaligned or out of bounds
To Reproduce:
usermod
directory.Expected behavior
Just let the model import per regular.
Related files
I think I'll be alright, it's just a
.mdl
file haha.Logs
Screenshots
If applicable, add screenshots to help explain your problem.
Details (please complete the following information):
Additional context
Nah.
The text was updated successfully, but these errors were encountered: