multiple issues (current : a problem with .bdl files ?)

[ireallyneedhelpp]

it tells me there is an error with the line temp = bmodel.bmodel() and also that bmodel is not defined. i am working on version 2.79

[niacdoial]

Hello, Sorry for the late response, but I think you are not using the latest version of the import script (IOManager.py). You will probably have to download and install the latest version of the whole add-on too. the batch file (converter.bat) didn't change, so you won't need to re-download and re-edit it, though.

Have a nice day!

PS: I still needed to fix another bug, that was in the "latest" version before this mail, but different from the bug you spotted. It is fixed now.

2018-03-15 22:32 GMT+01:00 ireallyneedhelpp notifications@github.com:

it tells me there is an error with the line temp = bmodel.bmodel() and also that bmodel is not defined. i am working on version 2.79

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/niacdoial/blemd/issues/15, or mute the thread https://github.com/notifications/unsubscribe-auth/AQR7veeZ4XxbnY2mVnZM3wkLyK8qC0Cxks5tet4AgaJpZM4Ss6qd .

[ireallyneedhelpp]

i downloaded it again and still get the same error

the scribbled out part is my name as i dont want to show that

[niacdoial]

Oh. Er... Okay now it should be actually fixed. Sorry, but for some reason I thought you were using the converter batch (a small script which runs blender in the background and outputs a fbx model) That also means that my previous reply was wrong (you probably actually had the up-to-date version at the time) and probably really confusing. And somewhat rude. Sorry for that. Thanks for your patience.

[ireallyneedhelpp]

i downloaded the newest version and now i get this message, sorry for being such an inconvenience.

also if you saw my previous version of post it was my error, i put the addon in two places

[niacdoial]

A couple of things here: 1 : The error you have means that it didn't find the "bmdview.exe" file (used to extract the images), that was supposed to be next to the other '.py' files. Meaning that either it is really missing, or it wasn't looking in the right place. I'll look for potential causes of the second. 2 : I saw the previous version of your message, and the error in this version happens before the error of the previous version even has a chance to. It probably has more meaning for you than for me, though. 3 : The error of the previous version is now sort of fixed. What it meant is that a part of the file cannot be understood by the addon (and I doubt it will be in the near future). Instead of crashing like an idiot, the addon will now ignore this part to focus on what can be imported. This means, however, that the final mesh might be incomplete, in ways I literally know nothing about. BTW, could I ask you to give me a copy of the file that triggered the "unknown mdl3 entry" error, please?

[ireallyneedhelpp]

so i downloaded it again and now the import process works and i actually get an output, however the textures are messed up and its all 1 object. is this how its supposed to be or am i missing a step or something. thanks for your help so far and sorry for being an inconvenience

and i dont know what "unkown mdl3 entry" is or the file that caused it

[niacdoial]

About the "one object" problem : I don't think this problem can ever be solved, because while the model stored inside the bmd file is divided between smaller parts, the the way it is done does rarely makes sense (at least for static elements).

About the texture problem : if the texture looks looks a corrupted mess (a bit like this : http://dreamstime.com/stock-photo-glitch-texture-data-colorful-chaos-image59140534) it might be because the BMD file does not contain the texture, but refers to it. Sadly, I haven't looked that much into this. If it looks like something decent, but badly stretched, crumpled, or simply in the wrong place, it may actually be a bug, but it is also likely because the texture was supposed to be animated, and I haven't found a way to translate texture animations to blender. Checking the "use complete materials" options might also help (bottom left when you choose the file to import). I might be able to be more precise with a screenshot of the problem (Not now though. See the end of the message)

The mdl3 error was the error reported by the first version of your previous post. I should have been more clear on that point. sorry.

Last but not least : you are not being an inconvenience. At all. During this discussion, you found no less than three different bugs, and when there was no bug, what you found was something I wasn't clear enough about.

Also, a little heads-up: I will likely not be able to do anything here in the next couple weeks or so, so I hope it works enough for you. In the meantime, have a nice day!

[ireallyneedhelpp]

i was messing around with the addon and i found out that the problem with the one object can easily be fixed just by separating the model by loose parts(even though it could potentially creates hundreds of objects) [Edit - its better to separate by material because that creates less objects] and the texture issue, some models work properly with textures but others for example gobblegut from smg2 only have 2 textures with it.

edit: the texture issue can be fixed by retexturing as the textures are included when importing the model

[hisprofile]

MDL3 is only mentioned in .bdl files, that also contain objects like .bmd files. This happened to me when I changed the .bdl file extension to .bmd. It still works and can be read properly, but BMDView2 and your addon just doesn't know what to do with the MDL3, so it just ignores it. I'm guessing it works with your plugin, because it works with BMDView2, so I haven't tested it yet.

[hisprofile]

Just tested it: changing .bdl to .bmd will work, but you may have to reapply the textures.

[niacdoial]

Quick question : could you give me a link to a .bdl file, please? I think I might manage to fix this once I know the differences between the two formats.

[hisprofile]

Sure thing: [ bdl.zip

[niacdoial]

Thanks! I looked at the file, and I already have a few ideas about what went wrong. I have also changed the documentation, so a bunch of things should be easier to understand now.

[niacdoial]

Turns out, the problems with this particular bdl file are problems that could also happen with any bmd file. I fixed them, and added a couple measures to better handle anything similar to one of them. I still have to examine the bdl-specific 'mdl3' section, though.

[hisprofile]

Alright.

[hisprofile]

Hey, do you think you'll be able to add support for .bdl?

[niacdoial]

I mean, from what I have seen (this one model), there is, I just need to make BleMD accept this file extension. I still don't know what to make of this mdl3 part, though. So I guess it just means the result is not yet "guaranteed".

[hisprofile]

Ok

[hisprofile]

Btw, heres a website. Might help with mdl3

http://wiki.tockdom.com/wiki/BMD_and_BDL_(File_Format)

[niacdoial]

Thanks, but this wiki page does not have the info I was looking for. Actually, there is a lot of missing sections in it.

On another note, I will be uploading the changes necessary to open .bdl files shortly.

[hisprofile]

Oh sweet

[hisprofile]

So hows progress on supporting the .bdl?

[niacdoial]

Well, the current version is able to open both types if files, now. It just cannot use the data from the mdl3 section, which, as far as I can tell, can only affect the materials, and the current result doesn't look broken in any way.

Le lun. 23 juil. 2018 01:23, hisprofile notifications@github.com a écrit :

So hows progress on supporting the .bdl?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/niacdoial/blemd/issues/15#issuecomment-406905187, or mute the thread https://github.com/notifications/unsubscribe-auth/AQR7vSTqWzL3FtIVuQP3ak9i-Z79yb50ks5uJQlfgaJpZM4Ss6qd .

[hisprofile]

O nice. Ill try it out