This shows you the differences between two versions of the page.
arma3:port-arma-2-vehicles-general [2017-12-28 15:42] snakeman created initial page. |
arma3:port-arma-2-vehicles-general [2018-01-02 03:58] snakeman added gunner config/proxy info. |
||
---|---|---|---|
Line 32: | Line 32: | ||
Tank Sound Replacements: | Tank Sound Replacements: | ||
- | <code> | + | <code cpp> |
soundServo[] = {"A3\Sounds_F\vehicles\armor\noises\servo_armor_comm", 1, 1, 30}; | soundServo[] = {"A3\Sounds_F\vehicles\armor\noises\servo_armor_comm", 1, 1, 30}; | ||
soundGetIn[] = {"A3\Sounds_F_EPB\Tracked\noises\get_in_out", 0.56234133, 1}; | soundGetIn[] = {"A3\Sounds_F_EPB\Tracked\noises\get_in_out", 0.56234133, 1}; | ||
Line 39: | Line 39: | ||
Tank Optics Replacements: | Tank Optics Replacements: | ||
- | <code> | + | <code cpp> |
gunnerOpticsModel = "\A3\weapons_f\reticle\Optics_Gunner_02_F"; | gunnerOpticsModel = "\A3\weapons_f\reticle\Optics_Gunner_02_F"; | ||
or commander with \A3\weapons_f\reticle\Optics_Commander_02_F | or commander with \A3\weapons_f\reticle\Optics_Commander_02_F | ||
Line 46: | Line 46: | ||
Artillery Optics Replacements: | Artillery Optics Replacements: | ||
- | <code> | + | <code cpp> |
gunnerOpticsModel = "\A3\Weapons_F\acc\reticle_Mortar_01_F.p3d"; | gunnerOpticsModel = "\A3\Weapons_F\acc\reticle_Mortar_01_F.p3d"; | ||
</code> | </code> | ||
Line 61: | Line 61: | ||
You need to comment out or replace these from arma2: | You need to comment out or replace these from arma2: | ||
- | <code> | + | <code cpp> |
driverAction = "AH1Z_Pilot"; | driverAction = "AH1Z_Pilot"; | ||
driverInAction = "AH1Z_Pilot"; | driverInAction = "AH1Z_Pilot"; | ||
Line 67: | Line 67: | ||
They do not work, you cannot get in to your vehicle if you have incorrect driverAction etc configs.\\ | They do not work, you cannot get in to your vehicle if you have incorrect driverAction etc configs.\\ | ||
Tank actions: | Tank actions: | ||
- | <code> | + | <code cpp> |
driverAction = "driver_apctracked3_out"; | driverAction = "driver_apctracked3_out"; | ||
driverInAction = "driver_apctracked3_in"; | driverInAction = "driver_apctracked3_in"; | ||
Line 77: | Line 77: | ||
Truck actions: | Truck actions: | ||
- | <code> | + | <code cpp> |
driverAction = "driver_Truck_02"; | driverAction = "driver_Truck_02"; | ||
getInAction = "GetInMRAP_01"; | getInAction = "GetInMRAP_01"; | ||
Line 84: | Line 84: | ||
Static actions: | Static actions: | ||
- | <code> | + | <code cpp> |
gunnerAction = "gunner_static_low01"; | gunnerAction = "gunner_static_low01"; | ||
gunnerAction = "gunner_standup01"; | gunnerAction = "gunner_standup01"; | ||
Line 93: | Line 93: | ||
It is very important to get your base inheritance class correct if you have many vehicles which inherits. Don't try to fix one vehicle at the time, TEST with one vehicle but fix your BASE inheritance class first. | It is very important to get your base inheritance class correct if you have many vehicles which inherits. Don't try to fix one vehicle at the time, TEST with one vehicle but fix your BASE inheritance class first. | ||
+ | |||
+ | Aircraft or helicopter gunner proxy needs to be how the chracter is positioned, then you need config.cpp properties for the turret which this gunner mans: | ||
+ | <code cpp> | ||
+ | gunnerAction = "pilot_Heli_Transport_01"; | ||
+ | gunnerInAction = "pilot_Heli_Transport_01"; | ||
+ | </code> | ||
+ | |||
+ | If you leave out the config so its wrong (for example from arma2) then gunner will take basic standing pose / animation. Also if the gunner proxy is wrong, the gunner of course takes the pose / animation which looks off to such gunner. |