Change Details

Problem in the BIS_fnc_planeEjectionFX, this is a part of the Arma 3 ejecting ability included into **core functionality** for all jets Problem presents in all MP scenarios with eject-supported jets See YT video [[ https://youtu.be/oTQuJYS0VbM | how this designed in SP, and how it in MP ]] I tested on a dedicated server with two players. The player who was on the ground found problems in (//`a3\functions_f_jets\functions\ejection\fn_planeEjectionFX.sqf`//): # The 3D sound from the ejection seat does not work, which it should play (//Line 53 in script//) # Omitted params in say3D code part, thus the required maximum sound audibility distance (1400m) is dropped to 100m (//as default for say3D//) # Three particle effects (//1 lightpoint and 2 particlesource//) in script do not work I can suggest the following solutions: **1.1** Remote Execute the say3D **1.2** Write the parameters that the sound should have (they are in //CfgSounds// → //Plane_Fighter_01_ejection_ext_sound//) **1.3** Result (Line 53) → form `_ejectionSeat say3D _ejectionSoundExt;` to **`[_ejectionSeat, [_ejectionSoundExt, 1400, 1, false, 0]] remoteExec ["say3D"];`** **2** the `createVehicleLocal` in particle effects code was swhitched to **`createVehicle`** (Lines 59-71) After these changes, the 3D sound will work, this 3D sound will be audible at the correct distance and particle effects will work, check this [[ https://youtu.be/0YN9Ar65Vow | YT video after changes in MP Dedi server ]]

**BIS_fnc_planeEjectionFX** function is a part of the Arma 3 ejecting ability included into **core functionality** for in vanilla This function is executed on the **client side of the pilot**, used commands //createVehicleLocal// and //say3D// do not work correctly when this function is executed by MP players See YT video [[ https://youtu.be/oTQuJYS0VbM | how this designed in SP, and how it in MP ]] I tested on a dedicated server with two players. The player who was on the ground found problems in (//`a3\functions_f_jets\functions\ejection\fn_planeEjectionFX.sqf`//): # 3D sound will not be trigger for other players # Take a look at the this 3D sound maxDistance option from config (CfgSound→Plane_Fighter_01_ejection_ext_sound): **`maxDistance=1400`;** But say3D does not repeat these parameter when executed in a script i.e. the maxDistance parameter is auto reset to default - [[ https://community.bistudio.com/wiki/say3D | 100m (see BIKI) ]] value. So the audible distance will not be as designed # Three particle effects `_fxLightSource`, `_fxSmokeTrailSource`, `_fxSmokeSource1` are creating by **local** comand, given that the script itself is executed on the pilot's client, no one will see these particle effects I can suggest the following solutions: **1.1** Remote Execute the say3D **1.2** Write the parameters that the sound should have (they are in //CfgSounds// → //Plane_Fighter_01_ejection_ext_sound//) **1.3** Result (Line 53) → form `_ejectionSeat say3D _ejectionSoundExt;` to **`[_ejectionSeat, [_ejectionSoundExt, 1400, 1, false, 0]] remoteExec ["say3D"];`** **2** the `createVehicleLocal` in particle effects code switch to **`createVehicle`** (Lines 59-71) After these changes, the 3D sound will work, this 3D sound will be audible at the correct distance and particle effects will work, check this [[ https://youtu.be/0YN9Ar65Vow | YT video after changes in MP Dedi server ]]

Problem in the **BIS_fnc_planeEjectionFX, this** function is a part of the Arma 3 ejecting ability included into **core functionality** for all jetsin vanilla Problem presents in all MP scenarios with eject-supported jetThis function is executed on the **client side of the pilot**, used commands //createVehicleLocal// and //say3D// do not work correctly when this function is executed by MP players See YT video [[ https://youtu.be/oTQuJYS0VbM | how this designed in SP, and how it in MP ]] I tested on a dedicated server with two players. The player who was on the ground found problems in (//`a3\functions_f_jets\functions\ejection\fn_planeEjectionFX.sqf`//): # The# 3D sound from the ejection seat does not work, which it shouldwill not be trigger for other play (//Line 53 in script//)ers # Omitted params in say3D code part,Take a look at the this 3D sound maxDistance option from config (CfgSound→Plane_Fighter_01_ejection_ext_sound): **`maxDistance=1400`;** But say3D does not repeat these parameter when executed in a script i.e. the maxDistance parameter is auto reset to default - [[ https://community.bistudio.com/wiki/say3D | 100m (see BIKI) ]] value. thus the required maximum soundSo the audibilityle distance (1400m) is dropped to 100m (//will not be as default for say3D//)signed # Three particle effects (//1 lightpoint and 2 particlesource//) in script do not work`_fxLightSource`, `_fxSmokeTrailSource`, `_fxSmokeSource1` are creating by **local** comand, given that the script itself is executed on the pilot's client, no one will see these particle effects I can suggest the following solutions: **1.1** Remote Execute the say3D **1.2** Write the parameters that the sound should have (they are in //CfgSounds// → //Plane_Fighter_01_ejection_ext_sound//) **1.3** Result (Line 53) → form `_ejectionSeat say3D _ejectionSoundExt;` to **`[_ejectionSeat, [_ejectionSoundExt, 1400, 1, false, 0]] remoteExec ["say3D"];`** **2** the `createVehicleLocal` in particle effects code was swhswitched to **`createVehicle`** (Lines 59-71) After these changes, the 3D sound will work, this 3D sound will be audible at the correct distance and particle effects will work, check this [[ https://youtu.be/0YN9Ar65Vow | YT video after changes in MP Dedi server ]]