Jump to content
The Dark Mod Forums

R Soul

Member
  • Posts

    185
  • Joined

  • Last visited

  • Days Won

    9

R Soul last won the day on January 10 2020

R Soul had the most liked content!

Reputation

205 Excellent

2 Followers

Recent Profile Visitors

1497 profile views
  1. While browsing for 3d objects I saw these 3d Frieze models and was thinking they could be of use for someone making TDM resources. In some scenarios the 3d shapes themselve may be good, or it may be better to use them to generate the various texture required for materials: https://creazilla.com/nodes/63996-frieze-set-3d-model Note that they are in the native format for Blender, and there are other models on that site that may also be suitable.
  2. Very early days but I had another go at mild trolling on LinkedIn, getting two likes so far:
  3. It is, but as mentioned in the first post, there's no way of know if it will ever get fixed. I've made a request in a number of places, but so far nothing has come of it.
  4. Something could be done. A few years ago I wrote an addon that looks at a Blender material's diffuse texture and scans the .mtr files to work out the TDM material name. Any name over 63 chars long gets saved in a custom property called FullName. An export script could look in there and do a swap. It's worth noting that my addon is not linked to any export process. Any user can make their own custom properties. I think OrbWeaver did some unrelated modifications to some of the import/export scripts, but it's been a very long time since I've been here so I don't know the current state of that side of things.
  5. That's my understanding too, but a material hierarchy seems like a good thing to keep. And my suggestion is aimed at helping Blender users make use of existing materials, in which case the users have to deal with what they're given.
  6. People who use Blender for object editing sometimes run into a problem with material names. It has a character limit of 63. That's usually fine but some existing TDM materials have names which are longer than that, so it becomes impossible to use them. An FM author can make a copy of the material with a shorter name, but that might be adding unnecesary complexity for people who are just making standalone objects to share. I've been mounting a valiant campain on various Blender forums, and some of their LinkedIn posts, to get them to increase the limit, but to no avail. So it's time to take a different approach. Would it be feasible for TDM to rename long materials? The rendering system would have to intercept and replace calls to the original names, or something like that. I'm not sure if that would be an easy thing to implement or if it would set off a chain of complex events or coding etc. Another possible approach could be a material ID sytem, so in Blender the material name could be WoodPlanks_4ACFB987B, which would correspond to something like TDM\long\path\to\material\WoodPlanks That might even be beneficial for shorter material names, as even they are not user friendly to look at in some interfaces.
  7. I don't visit here much, so I only just read about this. My condolences to grayman's family and friends.
  8. This was posted by Azaran on TTLG:
  9. Hi OrbWeaver. Each time I load Blender, for your ASE and LWO addons the console lists a load of warnings about properties that should be annotations. It doesn't say why, just that they should be. Warning: class <class name> contains a property which should be an annotation! ... assign as a type annotation: EXPORT_OT_ase.filter_glob assign as a type annotation: EXPORT_OT_ase.filepath ... assign as a type annotation: EXPORT_OT_ase.option_scale Fortunately all that's necessary is to change the = to a : and the console loses a lot of clutter.
  10. This looks a bit like the steam robot: https://prestonservices.co.uk/item/antique-working-steam-plant/
  11. I've been using Blender 2.80 for a while now. One of the good features is the ability to edit multiple objects at the same time. It's often useful to have vertices from different objects lined up, and it's especially useful when doing UV mapping with a single material for all objects because overlaps can be avoided.
  12. The Material Manager seems to be working. http://forums.thedarkmod.com/topic/19196-blender-tdm-material-manager-plugin-updated-to-version-280-blender-280-update/
  13. I think it's working. I got a texture loaded and assigned. Updating the screenshots meant I had to test the other features (e.g. overly long material names, duplicate materials etc) and the results were what I expected. I also gave the Material file extractor a test to make sure the zip (pk4) system still works, and it seems fine. https://github.com/RSoul82/Blender-TDM-Material-Manager
  14. It feels like the ability to load textures is close. The existing code still finds material slots. Each slot seems to contain the actual material (i.e. mat = slot_name.material). In case the user has turned off nodes, I use the code mat.use_nodes = True to ensure they're turned on. if mat.node_tree.nodes.find('Image Texture') == -1: will check if there isn't such a node, in which case it needs to be added node_tree.nodes.new("ShaderNodeTexImage") adds an image node That's it for now. Why does the day have to end when I'm getting somewhere?
  15. Thanks. I've added your changes to my file (on GitHub). Notable changes from 2.79 to 2.80: The code for checking object visibility has changed Reading mtr files would crash with one particular file, so I did something to do with encoding. Now that I've got going and we're over the UI hurdle I'm happy to continue. So far I've made the assumption that the the texture is assigned via a material node called 'Image Texture' (the code checks for the file path not just the texture name).
×
×
  • Create New...