[WIP] Fairmile B Motor Launch

[vdr1981]

Originally Posted by gap

What about that?

From my experience, one 3D model (gr2 or dat) = one paint , if rendered in the same scene (area). I cloned a number of dat units using S3D editor in order to bypass this problem.

Solution with roster cfg files can work pretty well in case of units which will probably wont ever be rendered in the same area, for example some British and German generic freighter, used by both nations...

[gap]

Originally Posted by vdr1981

From my experience, one 3D model (gr2 or dat) = one paint , if rendered in the same scene (area). I cloned a number of dat units using S3D editor in order to bypass this problem.

Solution with roster cfg files can work pretty well in case of units which will probably wont ever be rendered in the same area, for example some British and German generic freighter, used by both nations...

Yes, we already agreed on that, but my question was relative to a different (though related) topic. Please re-read my remarks on it:

Originally Posted by gap

...despite the fact that we can have any number of textures set in the cfg file, only the first three texture definitions are actually seen in game as early, middle and late war camouflages, set in GroupTypesDefs.cfg as 0, 1 and 2 respectively.

This is a bit disappointing because roster texture definitions have start/end dates and frequency settings, suggesting a random texture assignment based on in-game dates. Those settings can as well be the clue of an unfinished feature (as it is common in SH games), but before discarding them, has anyone tried setting the camouflage parameter to -1 and seeing if such a setting forces the game to use more that three textures and to apply date and frequency parameters?

[vdr1981]

Originally Posted by gap

Yes, we already agreed on that, but my question was relative to a different (though related) topic. Please re-read my remarks on it:

Can't really comment that. It needs to be tested...

[gap]

Originally Posted by vdr1981

Can't really comment that. It needs to be tested...

Okay. I think that that might be worth some tests since the same principle might also apply to sensors and armaments...

[kapuhy]

Guys, a quick question: is it possible to make flag smaller? (without changing the size of flags on other ships of course). The huge default flag simply doesn't fit the flagpole on such a small boat.

[gap]

Originally Posted by kapuhy

Guys, a quick question: is it possible to make flag smaller? (without changing the size of flags on other ships of course). The huge default flag simply doesn't fit the flagpole on such a small boat.

If you opted for the dat format, I think that you have no control on the flag size other than the naming of the flag node:

cfg#FLG = war ensign, large
cfg#FLS = war ensign, small
cfg#FLGC = civil ensign

It is likely that the same naming convention applies to GR2 units too, but chances are that the flag size of granny-format units can be fine-tuned further by using bone trasform (scale) data. My suggestion is you to have a look into this mod . By comparing its modded files with stock ones, you can easily understand how uekel achieved his smaller flags.

[kapuhy]

Originally Posted by gap

cfg#FLG = war ensign, large
cfg#FLS = war ensign, small
cfg#FLGC = civil ensign

Weird... I just tried it and the flag size stays about the same (roughly 1,5 times as high as the flagpole). It might be shorter horizontally with #FLS but I'm not sure.

Another minor thing I've noticed with the flag is that while it moves around with flagpole as ship bounces on waves, it doesn't seem to tilt accordingly, so with bigger waves you can see flag edges moving away from the flagpole.

(and yes, I've tried simplier .dat import through s3ditor first, though I still intend to try doing a gr2 version as well. This way I'll learn how both available editors work)

If I can't get the flag smaller, I'll probably just lower the yard (is this the correct English term?) a bit to accomodate for bigger flag.