[1.2-1.7] Blender (2.83+) .mu import/export addon

[taniwha]

Zeblote: well, mu.py is independent of blender (other than the blender<->unity conversions on vectors), and the code is GPL, so...

[sirkut]

taniwah. What's your progress with the version 3 .mu files?

[taniwha]

sirkut: as I have to disassemble the parttools dll to support version 3, I'm not sure what to do. I guess I should send a message to Mu asking for permission (but then, he did point me to the source the first time round). That said, I did take a look and it's only particle stuff.

[sirkut]

Ah yes. I forgot that the new parttools is a dll. :/

[longbyte1]

How can I have multiple .mu-imported objects without the other objects having the first object's material?

[rasheed]

Awesome! Doesn't work for some of the .mu files though

[taniwha]

Those will be version 3 .mu files. If you're lucky, you can get away with hacking the file version var in mu.py to be 3 rather than 2, and they'll load (so long as they don't have any particle information in them).

[rasheed]

And how do i hack that?

[taniwha]

It's a variable set near the top of the file: line 25: FILE_VERSION = 2

[rasheed]

Im not finding the FILE_VERSION thing, maybe i should be looking

EDIT oops, was looking in wrong file.

Edited September 26, 2013 by rasheed

[Moon Goddess]

I don't know what to do, I can't get anything to import, I've even tried pre-.20 parts everything just throws errors at me...

Can anyone just suggest a part any part that does work so I can see how this even works.

[taniwha]

Try liquidEngine1 (that's what I used for initial testing). It's the LV-T30, and I've just confirmed it's version 1.

Also: what errors are you getting?

[Kowbell]

Great googly moogly, this is the best addon I've downloaded for Blender 3D.

The access to the color schemes and the ability to see how the models are done are the best possible resources for modeling/texturing. This is going to make all of my stuff look soooo much better. I can't thank you enough, good sir.

Note: This works with the most recent version of Blender, and every .mu file.

[Moon Goddess]

Ok, tried with Liquid Engine1

Same result...

I can't figure how to copy paste the error and if I click it it goes away so I took a screenshot.

[sumghai]

Ok, tried with Liquid Engine1

Same result...

I can't figure how to copy paste the error and if I click it it goes away so I took a screenshot.

-snip-

What version of Blender are you using?

I had problems with 2.66a, but as soon as I upgraded to 2.68a the import script worked perfectly nearly all the time.

[taniwha]

Yeah, that's a blender version error.

BTW: as for why there's little progress, I've got a few irons in the fire: this, Extraplanetary Launchpads and now Damned/Infernal Robotics. And then there's QuakeForge (not as much, but yesterday I finally got a certain sub-project done for that) and work too. I actually have to take time off stuff to play :/.

[Moon Goddess]

Ok, thank you updated blender and it works well.

[Devo]

Yeah, that's a blender version error.

BTW: as for why there's little progress, I've got a few irons in the fire: this, Extraplanetary Launchpads and now Damned/Infernal Robotics. And then there's QuakeForge (not as much, but yesterday I finally got a certain sub-project done for that) and work too. I actually have to take time off stuff to play :/.

You're working on Infernal Robotics?

[taniwha]

Indeed I am. I've converted it to use PartModule instead of Part, and I'm now getting the GUI to work again.

[Devo]

Indeed I am. I've converted it to use PartModule instead of Part, and I'm now getting the GUI to work again.

oh ok, I wasn't aware someone was working on our pack besides me and Sirkut.

Might want to talk to Sirkut about the GUI, is he also aware you are playing with his code at the same time he is working on it?

[taniwha]

He's aware, and I'm working on the version he put on github, so I'm currently a little behind. I got fed up with that cData abomination and decided to do something about it .

[TheAquired]

Wow, what an awesome importer! Thank you so much! I have a problem though. The parts keep on having certain areas of the model black, instead of textured. I tried it last night when I downloaded it, and it worked perfectly. I tried again today, and so far every attempt has given me the same result. For example, the nuclear engine has textured body, but the engine cone on the bottom is black, not textured. Any ideas?

[taniwha]

Lighting is an obvious one. There's also a very strong possibility the nuke is using an un(der-)tested shader setup path. I'll keep this in mind when I get back to working on the "transporter" (as Greys calls it).

[TheAquired]

I figured out what it is. In some of the models, such as this fuel tank, for some reason the texture has an area where it is transparent. This transparent area leads to it rendering out pitch black. If you apply the texture in a decal fashion with an underlying colour on the entire model, then the black areas will be coloured according to the underlying colour.

P.S. I am using Cycles for rendering here.

[TheAquired]

Well I sort of feel silly, as I found out the reason for this problem. At the very least, I hope it helps someone else if they run into this problem. If this happens, select the texture in the UV/Image Editor, then press N and find the checkbox called Use Alpha. It will almost definitly be checked. Uncheck it, and the textures will render out perfectly!

Thank you again for this fantastic tool Taniwha!