Differences between a car and a tank

[Thunderbird 0]

Hi,

The purpose of this post is to understand and figure out what exact lines do differentiate a Car from a Tank in BIS configs.

Since, I'm getting some serious troubles to replace BIS Strykers by our Bradley Models.

---------------------------------------

BIS Strykers are inherited from 'cars' [Makes sense as Strykers get wheels].

Whereas our Bradleys are inherited from tanks [Again, makes sense as Bradleys get tracks].

---------------------------------------

So, during the replacement process, adding

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

Simulation = tank;

To the class strykerbase (The class which is supposed to host the replacement).

Isn't enough to complete the replacement as the bradley is recognized as a simple MG Car (like UAZ with DsHK... or a mounted Hummer).

And results with No working Tracks (Not animated)/ Muzzleflash in wrong place/ A huge exhaust smoke.

As you can see below:

Therefore, do you know what lines do make a Car becomes a Tank or a Tank becomes a Car/ Of course, in terms of configuration.

These lines are supposed to simulate the wheels of the Stryker:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

memoryPointExhaust = "exhaust_start";

memoryPointExhaustDir = "exhaust_end";

memoryPointTrackFLL = "tyreTrack_1_1l";

memoryPointTrackFLR = "tyreTrack_1_1r";

memoryPointTrackBLL = "tyreTrack_1_2l";

memoryPointTrackBLR = "tyreTrack_1_2r";

memoryPointTrackFRL = "tyreTrack_2_1l";

memoryPointTrackFRR = "tyreTrack_2_1r";

memoryPointTrackBRL = "tyreTrack_2_2l";

memoryPointTrackBRR = "tyreTrack_2_2r";

Disabling them and substuting them by Bradley tracks definitions, doesn't help at all.

In this way:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

memoryPointTrack1L = "Stopa LL";

memoryPointTrack1R = "Stopa LR";

memoryPointTrack2L = "Stopa RL";

memoryPointTrack2R = "Stopa RR";

memoryPointExhaust = "exhaust_start";

memoryPointExhaustDir = "exhaust_end";

memoryPointTrackFLL = "";

memoryPointTrackFLR = "";

memoryPointTrackBLL = "";

memoryPointTrackBLR = "";

memoryPointTrackFRL = "";

memoryPointTrackFRR = "";

memoryPointTrackBRL = "";

memoryPointTrackBRR = "";

Therefore, any help or enlighten advice to figure out this issue would be much appreciated.

Edit: Things were so easier to handle with OFP since there was 1 main config with everything centralized in one place, heh.

Regards,

TB

[franze 196]

Moving to ArmA:Configs & Scripting.

[Big Dawg KS 6]

Well since the Strykers are all derived from class Car, they inherit all the properties of a wheeled vehicle.

It might be best just to redefine the whole Stryker class hierarchy (and base it off a tracked class).

[Thunderbird 0]

This was the first option tried here but it didn't work as the new 'class strykerbase: tank' defined via an external new replacement '.pbo file' can't get rid of some elements of BIS Default \wheels\'class strykerbase: car'.

Therefore, It is absolutely needed to locate some exact config lines to disable within 'class strykerbase: car', in order to ensure that the new 'class strykerbase: tank' would not inherit from \wheels\'class strykerbase: car' hard-coded lines.

Regards,

TB

[Gargantua 0]

Quote[/b] ]Therefore, do you know what lines do make a Car becomes a Tank or a Tank becomes a Car/ Of course, in terms of configuration.

it's simple.

simulation

all other bugs are due to bad model.cfg (you missed some bones or sections)