2252 replies to this topic

[Heffay]

Iacov, the latest version (which has a ton of bug fixes and creates the materials for you) has you put in the base path into the code. Just edit with notepad. For example, I extracted everything to e:\blender projects\mechs, so that is what is set in the current script. All the pak files get extracted there, including the textures and lib subdirs. Those contain the image files for making the materials. Be sure to convert all the dds files in those dirs too.

I really need to make an amended video #2...

IqfishLP, on 12 February 2014 - 07:50 AM, said:

Umm, it tells me I can't run scripts on my system..?

Yes I ran PS as admin

Run:

Set-executionpolicy unrestricted

[Iacov]

thanks heffay

what would happen if i didn't convert the .dds files? it would simply not asign a material/image to the part?

[Iqfish]

Okay, got the script to work.

BUT

I get errors, he can't find the mech's files in the objects directory, because there is no such file.
I checked and inside each .pak file of MWO there is another objects directory, so the correct path for the script to search in would be e:\Sample Directory\objects\objects\firestarter\body\firestarter_body.mtl, but the script only opens 1 objects directory.

[Heffay]

Oh no. Bad Iqfishlp! Bad! Rule #0 from post #1 in this thread!

Copy all the .pak files to a unique directory. Let's call it e:\mwogame. Extract them all there, so you'll have e:\mwogame\objects, e:\mwogame\textures, e:\mwogame\libs, and a bunch of other ones (e:\mwogame\environment has lots of map assets!).

Then under e:\mwogame\objects\mechs, you'll see all the mech directories. Go into each of those, and you'll see that mech's .cdf file. That is where you want to run mech-importer.ps1 from.

Under this structure, the base dir you want to set in the script would be e:\mwogame. That should be all you need!

[Iqfish]

Tehehe, I'm sorry, that was kind of stupid of me. I will do that as soon as I can.

Again: Thank you two guys, you rock!

[Heffay]

No worries.

Wife and I are driving to Vegas here in about 30 minutes. My next post will probably be from jail, so if you don't hear from me today, wait until I make bail on Monday.

[Iacov]

hope that jail has a good wifi ;P
have fun and get rich

[Iqfish]

Dat pink! I love missing textures. Gonna have to figure out why the hell it did not load them...



Could it be this?
"0.0020 sec
loading materials and images...
Material not found MTL: b'e:\\MWO Game Files zum Bearbeiten\\Game\\objects\\mechs\\firestarter\\body\\unused.mtl'"

[Iacov]

i wonder if this b' is intentional before e:\\
(i assume the files are located on e:?)

[Iqfish]

I have no idea where that "b' " comes from. What does it even mean?

yes they are on E:

Edited by IqfishLP, 12 February 2014 - 08:57 AM.

[Heffay]

Unused.mtl is what Noesis puts in the obj file when you don't tell it to use the mtl file. My script just ignores that though.

It looks like you loaded the model twice? Some of the parts look duplicated and unrotated. If you get a bad load, just close blender without saving and try again. Otherwise it'll load the objects with .001 on the name and won't be able to work on them properly.

[Iqfish]

Well, after the second load (and the third) the mech gets loaded, some parts are duplicated and I have no textures.

Do I have to REPLACE the .cgf files with the .obj files, when I converted them with Noesis or is it okay to have the files duplicated, like firestarter_lowerarm.cgf and firestarter_lowerarm.obj in the same directory?

EDIT: This is how it looks now. It seems like all the files have been imported now, but yea no textures. Does the script even import textures?

Edited by IqfishLP, 12 February 2014 - 05:26 PM.

[Heffay]

The .cgf and .obj files can happily coexist. I think the issue is in import.txt. Be sure to delete the old one before running mech importer. It just appends so it's probably getting a bit long. Will add a bug fix to that soon.

[NautilusCommand]

IqfishLP, on 12 February 2014 - 05:22 PM, said:

Well, after the second load (and the third) the mech gets loaded, some parts are duplicated and I have no textures.

Do I have to REPLACE the .cgf files with the .obj files, when I converted them with Noesis or is it okay to have the files duplicated, like firestarter_lowerarm.cgf and firestarter_lowerarm.obj in the same directory?

EDIT: This is how it looks now. It seems like all the files have been imported now, but yea no textures. Does the script even import textures?

Stuff like this just hurts my head when I look at it.

[Iqfish]

Yea it can get kinda complicated but when you are abled to understand Java the python code is quite understandable, the ps1 script is genius but easy to understand. I just did some stupid mistakes yesterday

[ssm]

Hi guys, I'm slowly making my way through this thread, and as I just begun importing meodels into blender using Heffay's script, I encountered a problem:



Namely - those "black" parts - why are they like this? Is there any easy way to either fix them or replace them with others without having to align them manually ?

Edited by ssm, 13 February 2014 - 03:38 PM.

[Heffay]

As far as I can tell, the black parts are just a display bug. If you set the 3D viewer to material or rendered mode, it'll show the objec with the proper node layout/material.

[Iqfish]

Well, I have exactly the same problem, with some "black" parts. No nodes or materials are created.

[Valcrow]

I don't use blender, but that's sometimes an indication of reversed normals.

Try flipping the normals on the black parts.

(not that I would know how to do that in blender...)

[Iacov]

ssm, on 13 February 2014 - 03:25 PM, said:

Hi guys, I'm slowly making my way through this thread, and as I just begun importing meodels into blender using Heffay's script, I encountered a problem:



Namely - those "black" parts - why are they like this? Is there any easy way to either fix them or replace them with others without having to align them manually ?

don't know how to fix it, but be careful with the right torso and the left arm
the right torso still has the "closing" part...therefore it will cut off most off the ppc underneath
the same with the left arm: a missile box is still active and you'll miss out the nicely articulated ppc
and beneath the left torso, there's still another LRM launcher...that's why it is part black part grey....

haven't yet tried to flip normals in blender
but try hitting space...type flip ... and see what options it gives you for choice
maybe flipping normals really does the trick