Page MenuHomeFeedback Tracker

Datalink config properties do not work correctly on soldier type units
Feedback, NormalPublic

Description

When using any of these config entries (or a combination of them) in the root config class of a unit:

ReportRemoteTargets = 1;
ReportOwnPosition = 1;
ReceiveRemoteTargets = 1;

The expected behavior is for the unit to spawn with selected Datalink components turned on by default, whether the unit is spawned with EDEN or Zeus or in Warlords.

However, when this is applied to man type units it does not work, the unit will spawn with all datalink components turned off.

A temporary hack was found by placing the entries inside class AttributeValues:

class AttributeValues 
{
ReportRemoteTargets = 1;
ReportOwnPosition = 1;
ReceiveRemoteTargets = 1;
};

The unit will spawn with the attribute correctly set in EDEN, however it still won't have the components enabled when spawned via Zeus or Warlords.

Details

Severity
Minor
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
Config
Additional Information

This is used in the Expeditionary Forces Creator DLC, so a fix would be appreciated.

Event Timeline

Chairborne renamed this task from ReportRemoteTargets config property does not work correctly on soldier type units to Datalink config properties do not work correctly on soldier type units.
This comment was removed by dedmen.
dedmen added a subscriber: dedmen.Wed, Nov 13, 8:52 AM

These config entries are only read on Transport vehicles.
On people, they do have the entry in engine, but its always initialized to false, and never read from config.

Vanilla never sets these parameters on non-transport vehicles, so this shouldn't change any existing behavior.

dedmen changed the task status from New to Feedback.Wed, Nov 13, 9:30 AM

With EF CDLC release