Trigger
10-10-2003, 09:58 PM
Day of Defeat 1.0 utilizes sub-models to a large extent in order to save filespace, while this has proven to make things much more difficult for player modelers, it can have some interesting applications for the custom community.
It is just such an application I intend to propose to you here. Weapon models include several sub-models for sleves from each team, each team has their own sleve model that is called up when they use a weapon, regardless of which weapon they are using.
All the weapons include German sleves, and either American or British sleves, but none of the default models have all three. This is not a matter of code, but rather one of saving space. It is entirely possible to recompile a weapon model with all three sleve models included and it will work perfectly in game.
This is also true for weapons like the pistols, which don't have seperate sleve models at all, it is possible to delete the cuffs that are included in the model, and compile using standard sleve sub-models instead.
The applications of this are two fold: First, the custom weapon in question could be used to replace any weapon, regardless of which team uses them, at the descretion of the end-user simply by renaming it. It certainly increases the options people have, if, for example, they'd rather have that spiffy new Thompson replace the Sten instead of the default American Tommy. The second application is that pistols could be reorigined with far fewer limits than would be otherwise possible. I always thought the pistols were a little too close to the screen, anyway, it's like he's holding it up to his cheek.
However, I digress from my original theory, which is this: If it's possible to have sleves change depending on which team is using the weapon, how hard would it be for the weapon to change as well? The applications, I'll admit, are limited, and there are problems with the idea. A few limitations would be that the weapons would still only have one p_model, and, most notably, they would have to share animations.
The possibility is there though, and could be used to make subtle alterations to weapons or to replace them entierly with a weapon that is operated similarly. I'll leave it to the custom community to decide wether the idea is worth looking into, what should be done with it, or if it's even possible.
Have at you!
It is just such an application I intend to propose to you here. Weapon models include several sub-models for sleves from each team, each team has their own sleve model that is called up when they use a weapon, regardless of which weapon they are using.
All the weapons include German sleves, and either American or British sleves, but none of the default models have all three. This is not a matter of code, but rather one of saving space. It is entirely possible to recompile a weapon model with all three sleve models included and it will work perfectly in game.
This is also true for weapons like the pistols, which don't have seperate sleve models at all, it is possible to delete the cuffs that are included in the model, and compile using standard sleve sub-models instead.
The applications of this are two fold: First, the custom weapon in question could be used to replace any weapon, regardless of which team uses them, at the descretion of the end-user simply by renaming it. It certainly increases the options people have, if, for example, they'd rather have that spiffy new Thompson replace the Sten instead of the default American Tommy. The second application is that pistols could be reorigined with far fewer limits than would be otherwise possible. I always thought the pistols were a little too close to the screen, anyway, it's like he's holding it up to his cheek.
However, I digress from my original theory, which is this: If it's possible to have sleves change depending on which team is using the weapon, how hard would it be for the weapon to change as well? The applications, I'll admit, are limited, and there are problems with the idea. A few limitations would be that the weapons would still only have one p_model, and, most notably, they would have to share animations.
The possibility is there though, and could be used to make subtle alterations to weapons or to replace them entierly with a weapon that is operated similarly. I'll leave it to the custom community to decide wether the idea is worth looking into, what should be done with it, or if it's even possible.
Have at you!