Page MenuHomeFeedback Tracker

Community Terrain Dust Effect Conflict (+= for nested arrays)
New, NormalPublic


The current configuration structure for linking terrain surface types (CfgSurface entries) to particle effects that are created when entities move over it is not patchable through addon files.

Currently as it stands the CfgVehicles classes Car, Tank, Air and Man have two parameters, rightDustEffects[] and leftDustEffects[], which are arrays. These arrays contain nested arrays that are pairs of cfgSurface classnames and their linked particle effects.

This array cannot be extended by community addons, thus creating a problem where there can only ever by one addon loaded that redefines these arrays to inject their own surface definitions.

The config operator "+=" would be the way to go here, however that operator can not extend arrays with nested arrays:

rightDustEffects[] += { {"Nested","Array"}}; // Does not patch the array.

The easiest fix to solving this here would be expanding the += operator to allow adding nested arrays to the array-parameter. This would not cause any issues with backwards compatibility.

Alternative Solution:
Changing the config structure of this into subclasses:

class rightDustEffects
    surfaceClassname = particleEffectClassname;
class leftDustEffects
    surfaceClassname = particleEffectClassname;


Operating System
Windows 10 x64
Operating System Version
Steps To Reproduce

No repro steps needed, this is a config structure issue.

Additional Information

Event Timeline

Mondkalb created this task.Jul 3 2018, 9:53 AM
Mondkalb edited Additional Information. (Show Details)Jul 3 2018, 9:58 AM
Uro added a subscriber: Uro.Jul 5 2018, 11:31 AM
nomisum added a subscriber: nomisum.Jul 6 2018, 9:54 AM
rizon02 added a subscriber: rizon02.Jul 6 2018, 4:14 PM
Cosmo added a subscriber: Cosmo.Jul 6 2018, 8:57 PM
Uro added a comment.May 4 2019, 1:35 AM

Any updates on this issue from Bohemia?
This has been on the issue tracker for almost a year and not even acknowledged by BI for something that would be a relatively easy fix and require minimal work on their end.

Having an un-appendable array like this is pretty backwards when someone is looking to enhance terrain surfacing by adding unique definitions for their terrains and particle effects.
Adding this feature would enable community authors to append this array without having to over-write the default Arma 3 values - which is super bad practice and would affect any other mods loaded.

I brought up that exact same issue in Mnišek... :/