LK,

I think I understand your question, and your quite correct in that I've not made this too clear -

this feedback is good! I may have said 'rescaling' in my reply to a previous post. If so, my

apologies for poor terminology.

Let me try to explain like this (a bit long-winded for your specific question LK but I'm thinking

in terms of documenting something I've overlooked so please bear with me!). If it does'nt answer

your question let me know.


Object and figure-image sizes in BIF's
--------------------------------------

Any generic-unit folder contains BIF image-rectangles for both figure-images and weapons/shields.

Considering these image-rectangles we see 3 things -

1) the size of all figure-images are ALWAYS constant to each other
2) the size of all shield images are also constant to each other, but not always constant to the

size of the figure-image that will 'carry' the shield.
3) the size of all weapons images are NOT constant to either each other (ie: other weapons

images) or the figure-images


Considering 2) above we see that in the generic-unit plate for Peasants the single shield image

defined looks fine (in terms of size) in respect of the figure images within that BIF.

Now look in the generic-unit plate for ChainHlm. We see 5 shields, and some of them are certainly

NOT good (in respect of size) for the figure-images defined on that plate.

Does it matter? Absolutely not! As any shield image is always positioned by virtue of the

parameters (4 sets of xy-coords for each corner of the shield) defined for an

action/camera-angle/frame in an action-object-line, the size of the original image in the BIF is

not important. In other words, a shield image is CONSTANTLY BEING RESIZED during animations.

You can make a shield image 10 times larger than the figure-image in the BIF (if it would fit!).

It matters not one iota!


Two points to note for shield images -

a) the shields.txt file within a generic-unit folder only contains parameters defining the

image-rectangle.

b) a shield image can only ever represent that specific shield image. It CANNOT represent any

other object.


Considering 3) above we see that (in any generic plate) the weapons images appear to be somewhat

'erratic' (in terms of size) relative to the figure-images defined on any plate. Far more so than

shield images.

Note: a weapon image in a BIF may serve to represent many different weapons. It CAN represent

other objects (weapons).


Two points to note for weapons images -

a) the weapons.txt file within a generic-unit folder contains parameters defining the

image-rectangle, and also 2 more parameters that serve to define the size of the weapon (relative

to the figure-image). Let's call these 2 parameters the 'weapon scaling parameters'.

b) a weapons image can represent multiple weapons, by virtue of the 2 'extra' parameters for

weapons referenced in a) above . It CAN represent any object that differs only in terms of size.

For example, a spear weapon may also be used to represent a pike - a poleaxe weapon may also be

used to represent a 'hand axe', etc, etc, etc.


The two stages of object scaling
--------------------------------

We can now say, in terms of object images -

- a shield image represents a single specific shield; full stop!
- a weapon image may represent multiple weapons (accomplished via the last 2

weapon-scaling-parameters as defined in the weapons.txt files).


Therefore, before any figure-image is rendered (with it's weapon/shield/mount) a rescaling

process must take place ONLY IN RESPECT OF WEAPONS, before the actual positioning of weapons and

shields relative to a figure-image frame can take place.

Hence, the MTW engine must consider 2 stages in respect of object scaling, and must 'ask itself'

the following questions -.

Stage 1: Do any weapons require rescaling, in respect of their size relationship with the

figure-image, in order to portray a different type of weapon. Should a weapon image really

portray a spear or a pike (sizewise)? Let's check the last 2 parameters of the appropiate line in

the weapons.txt file. If we have to rescale, let's do it now before the second stage (which

allows for positioning as opposed to size!). We can ignore shield images - they can only ever

represent 1 image (and hence don't have the same last 2 parameters that weapons images have for

rescaling).

Stage 2: Ok, any weapons that may have been resized are now THE CORRECT SIZE, IN TERMS OF A

SPECIFIC WEAPON OBJECT THEY ARE INTENDED TO PORTRAY, AND IN RELATIONSHIP WITH THE FIGURE-IMAGE.

Now let's look at how the weapons and shields objects require positioning on the figure-image,

via the action-object-sets and action-object-lines in order to change the perspective of these

objects, if necessary, for any frame in the movement-cycle.