Jump to content


Photo

Blender TDM Material Manager Plugin - updated to version 2.3.0


36 replies to this topic

#26 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 08 January 2018 - 04:44 PM

Updated to version 2.2.1.

Some decal textures weren't being extracted due to their .pk4 file having a slightly different structure to the others.

Same download links as before, but since we're now on page 2:

 

Download:

Go to the GitHub page: https://github.com/R...aterial-Manager

Right click the .py file, then go to Save As and put it in some folder.

(Or go to Clone or Download and save it as a zip file to your computer).

 

Be aware that this file isn't synchronised with the one on my PC, and the latter is the one that gets uploaded to Github, not the other way round.


Edited by R Soul, 20 January 2019 - 10:57 AM.


#27 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 12 January 2018 - 07:16 PM

A tiny update, same links as above.

 

I found that the material name scanner woun't go to the first line in an .mtr file, so this wouldn't have found the extremely rare occurrence of the material you want being defined right at the start of the file. Most files begin with a comment. I discovered the bug due to writing some custom materials.


  • RPGista likes this

#28 RPGista

RPGista

    Advanced Member

  • Member
  • PipPipPip
  • 1621 posts

Posted 02 February 2018 - 09:57 AM

Thats brilliant work man, its a shame I cant seem to find any time to work on blender these past few months. Any help with setting up materials is such a blessing, its the single most annoying aspect of modeling for me, all the paths and materials and placing the textures here and there... 



#29 Judith

Judith

    Advanced Member

  • Member
  • PipPipPip
  • 1910 posts

Posted 02 February 2018 - 10:25 AM

If there's one good remedy for that, it's using as few materials per mesh as possible. It's also very beneficial for performance.



#30 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 14 October 2018 - 06:48 PM

I've updated this addon. Now, when a texture is shared by multiple materials, it lists each of them as values of a set of custom properties. You can then paste the correct value to your Blender material name, and set the NoChange custom property to keep the chosen material.

 

It does this for collision textures too. You'll end up with 36 custom properties to choose from.

 

Same link as before, but reposting anyway:

Go to the GitHub page: https://github.com/R...aterial-Manager

Reinstalling it is very easy. Just download the above, in Blender go to User Preferences > Addons >Install from file. Select the zip file and it'll overwrite the previous version.


Edited by R Soul, 12 January 2019 - 08:12 AM.

  • Skaruts likes this

#31 Skaruts

Skaruts

    Member

  • Member
  • PipPip
  • 279 posts

Posted 14 October 2018 - 08:05 PM

I'm having a little issue with it finding me a wrong texture. The shader name is textures/darkmod/stone/brick/rough_big_blocks02 (copied from DR), but it chooses the texture from the file rough_big_blocks02_cornerstone_light.dds, instead of rough_big_blocks02.dds.

 

Meanwhile, is there a way to lock a texture so it doesn't change it when I load textures for new materials? 

 

EDIT: I just installed the new version, btw, but it still chooses that wrong texture.


Edited by Skaruts, 14 October 2018 - 08:07 PM.


#32 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 15 October 2018 - 12:42 PM

The material can be locked by giving it a custom property called NoChange with a value of 1.

 

I'll look in to the example you gave and see if it's a code bug or if it's an error that can't be avoided. I'll edit this post with my findings, unless there's another reply to this thread in the meantime.

 

edit: On my PC the correct texture is assigned. Does your 'extracted textures' folder have the same structure as the pk4 files. E.g. some_path/stone/brick, some_path/wood/panels etc?


Edited by R Soul, 15 October 2018 - 03:14 PM.


#33 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 12 January 2019 - 08:19 AM

I've uploaded the files on to Github which may make it easier for people to view, and to make suggestions etc. I don't have any auto-snyching going on, but I don't expect to be making any changes in the near future. See the first post.



#34 OrbWeaver

OrbWeaver

    Mod hero

  • Active Developer
  • PipPipPipPipPip
  • 7599 posts

Posted 21 January 2019 - 03:53 PM

Thanks for putting this on GitHub, that's a big improvement over ZIP files on download sites.

 

I'm happy to have a look at updating this for Blender 2.80, but I noticed that you haven't included a license with the code, which means that by default the code is "all rights reserved" and modifications (from other people) aren't allowed. Assuming this isn't the intention, would you mind choosing a license and putting it in a LICENSE file in the repository root? GitHub's default suggestions of either GNU GPL v3 or MIT seem pretty sensible, depending on whether you care about the "share-alike" protection or not.



#35 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 24 January 2019 - 02:10 PM

I've done that now. The master branch now has the GPL license. I also reuploaded the file addon in a "2.79 archive" branch to preserve that version while the master gets updated for 2.80. I recently thought about updating it but read about 2.80 not being finished yet, but if you're willing and able, then you have my sword.


Edited by R Soul, 24 January 2019 - 02:13 PM.

  • OrbWeaver likes this

#36 OrbWeaver

OrbWeaver

    Mod hero

  • Active Developer
  • PipPipPipPipPip
  • 7599 posts

Posted 25 January 2019 - 04:55 AM

Excellent, thanks. I might have a look at this next week, although don't let me discourage you if you were interested in working on Blender 2.80 support yourself — it is your project, after all.

 

You are right that Blender 2.80 is still in beta, but they are saying the API is mostly stable now, with only minor tweaks expected before release, so it should be fine for script developers to start updating their scripts to 2.80.



#37 R Soul

R Soul

    Member

  • Member
  • PipPip
  • 167 posts

Posted 25 January 2019 - 08:27 PM

Feel free to experiment as much as you want. I have another thing that's occupying me at the moment.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users