Users who are viewing this thread

media_evil

Recruit
It happened so that M&B is one of the few games that I can run on my current machine at reasonable frame rate. After installing Warband and playing for a couple of hours like in good old days I decided to buy a new weapon - War Hammer. It happened to be broken, and unfortunately, the latest patch does not fix it, so I ended up getting into the Warband modding to fix the thing. Then I thought that it would have been cool if War hammers and some other items were usable in two modes: hammer and beak, so I added that (via WSE). At the end, I started creating a mod before I even realized it.

Now about this thread. I want to get certain features implemented and I am certain that I would be able to get it done, but I am not ready to commit too much time to learning all peculiarities of modding tools. I just want to get this done ASAP and play. Among the features:
  • balance, as close to native as possible [✓]
  • alternative modes for some weapons (balanced) [✓]
  • deployable pavise shields with proper UI interaction dialog and IA support [WIP]
  • shield bash [haven't looked at it yet]
  • new, balanced, chest armors, based on models from this mod [✓]
  • new, balanced, helmets, based on models from this mod (involves adjusting compatible vanilla meshes to prevent clipping) [✓]
The main threat to the balance is coming from helmets that should be granding some extra body protection. Add armor modifiers (e.g. 'Lordy') on top of it and you will understand why it is a problem. I am looking into ways to overcome this without changing armor rate of troops.

So what is this thread about: I have questions. Not terribly much, but more that I feel comfortable asking on forums. On the other hand, I don't want to spend weeks of my life to come to those answers that someone more experienced can give in minutes. All this essentially boils down to either starting such thread of to give up on modding.

What would I give back? Credit? I can make the whole thing public on github (once I make sure that TaleWorlds and authors of some other resources are cool with it).
 
Last edited:

media_evil

Recruit
Now I am working on remodelling ~34 native helmets that seem compatible with meshes from this mod. Among issues that I encountered is the one that causes some helmets to look transparent in openBRF. Any ideas why? Any recommendations regarding generation of LoDs for new meshes?
 

Eärendil Ardamírë

Subforum Moderator
WBWF&SM&B
  • deployable pavise shields with proper UI interaction dialog and IA support [WIP]
shield bash [haven't looked at it yet]
Among issues that I encountered is the one that causes some helmets to look transparent in openBRF. Any ideas why? Any recommendations regarding generation of LoDs for new meshes?
Check the material and texture entries and which format the texture has (should be DXT1). Lods can be created with OpenBRF.
 

media_evil

Recruit
Hi. I've seen both pavise implementations and shield bash implementation. I am going to iterate on both to make them playable (though here I would probably have most of questions). Regarding transparent models from the screenshot: that is how i see some models when I open Warband/CommonRes/helmets.brf, (e.g. spiked_helmet_new). It is unclear to me which texture path to use or which preparations are required prior to opening a standard .brf. Any more ideas?

I tested everything in native (untouched) module.
 
Last edited:

Eärendil Ardamírë

Subforum Moderator
WBWF&SM&B
Uh, I can see all Native resource in a normal way, there are no transparent models for me (except the heraldic armours). Can you make a screenshot of what see and write down which OpenBRF version you use?
 

Red Serf

Sergeant Knight
Are you perchance using windows 10? I have the same issue with that texture (helmets_b) showing transparent in openbrf but fine in-game.
My solution was to edit the dds file itself in my Warband folder, just saving it as DXT1 format as suggested by Earendil, after using tools to remove the weird transparency from it.
 

media_evil

Recruit
Ok. It was a looong night. I have adjusted ~30 helmet meshes in blender. Unfortunately I don't know how to edit UVs in blender, so I ended up editing meshes only, trying to make sure that I don't distort them too much (however multiple times I wanted to add polygons here and there).

the result looks OK.
Are you perchance using windows 10? I have the same issue with that texture (helmets_b) showing transparent in openbrf but fine in-game.
My solution was to edit the dds file itself in my Warband folder, just saving it as DXT1 format as suggested by Earendil, after using tools to remove the weird transparency from it.
Yes. I am running win10. About your solution:
- could you briefly explain to me what DXT1 format is, or maybe give some links?
- how exactly do you remove "weird transparency"?
- why some textures are .dds and they look fine in openbrf?
- why all transparent helms have _new suffix at the end?

Common question: what exactly is the order in which resources linked in module.ini are loaded?
 

Eärendil Ardamírë

Subforum Moderator
WBWF&SM&B
Common question: what exactly is the order in which resources linked in module.ini are loaded?
Textures -> Materials -> Meshes
- could you briefly explain to me what DXT1 format is, or maybe give some links?
DXT1 is basically a dds file format for textures.
- how exactly do you remove "weird transparency"?
Convert the dds with Gimp or such to a dxt1 dds texture.
- why some textures are .dds and they look fine in openbrf?
Because they are probably stored as DXT1 textures already
- why all transparent helms have _new suffix at the end?
TW developers added some few times new assets to the game, you can also find brf files with "new" in the name.
 

media_evil

Recruit
Textures -> Materials -> Meshes
Did I get it right that resources that are loaded first (at the top of module.ini) shadow everything that follows?

Now I am writing a script that would generate records for new types of helmets for module_itmes.py. The idea is that versions padded with leather, gambeson, aketon, and hauberk offer a small increase to head and body armor rating, but also increase the weight, difficulty and price. The resulting stats of armors however should not exceed the stats of the strongest items of corresponding type.

Also. I updated to the latest version of the openbrf which solved the problem with transparent textures.
 
Last edited:

media_evil

Recruit
I mean if after load_resource declaration in module.ini there is another declaration that loads some resource with the same name, the first declaration will prevail. Consider the following structure:

Code:
// brf_a.brf 
  texture_1
 
// brf_b.brf 
  texture_1
  texture_2

// module.ini
load_resource = brf_a
load_resource = brf_b

// What game loads
  texture_1 (brf_a) // becase texture_1 from brf_a was encountered first and shadows texture_1 from brf_b
  testure_2 (brf_b) // because testure_2 wasn't shadowed
 

media_evil

Recruit
that loads some resource with the same name

that loads another .brf containing a resource with the same name* (see snippet in my previous comment).
 
War Hammer. It happened to be broken
What is wrong with it?
hammer and beak
You mean two-handed and polearm?
Among the features
I advise you not to spend time on making your mod but to make use of already-published mods which have all the features you mentioned.
So what is this thread about: I have questions. Not terribly much, but more that I feel comfortable asking on forums. On the other hand, I don't want to spend weeks of my life to come to those answers that someone more experienced can give in minutes. All this essentially boils down to either starting such thread of to give up on modding.

What would I give back? Credit? I can make the whole thing public on github (once I make sure that TaleWorlds and authors of some other resources are cool with it).
Modding is very time-consuming so you may make use of many OSP/ LSP mods to begin with (https://forums.taleworlds.com/index.php?threads/list-osp-lsp-modifications.377920/). That way you will save lots of time and spare yourself unnecessary trouble you would have if you started with less-polished codebase. Make sure to credit OSP/ LSP authors after you have finished your mod.
that loads another .brf containing a resource with the same name* (see snippet in my previous comment).
Use OpenBRF's function to scan a module for errors, that should give you a fresh look at what should be improved.
 

media_evil

Recruit
What is wrong with it?
Was not able to do side attacks.
You mean two-handed and polearm?
No. Polearm (blunt) / polearm (piercing)
I advise you not to spend time on making your mod but to make use of already-published mods which have all the features you mentioned.
I am not happy with the implementation as it is. So I either forget it and quit or do something with it.
Modding is very time-consuming so you may make use of many OSP/ LSP mods to begin with (https://forums.taleworlds.com/index.php?threads/list-osp-lsp-modifications.377920/). That way you will save lots of time and spare yourself unnecessary trouble you would have if you started with less-polished codebase. Make sure to credit OSP/ LSP authors after you have finished your mod.
Will definitely check as a reference. Credit will certainly be given to anyone who helped directly or indirectly.\

Regarding load order and "shadowing". ATM I don't have any issues with loading resources. I just discovered that it is a thing and wanted someone more competent to confirm this. Today've been learning about UV maps in blender. I wanna add some more polygons to those chainmail helmets. The script for generating item entries is also finished now.
 
Top Bottom