Command Console unable to Command (only reads) - UE 5.5

[SLGY]

As per Unreal Engine section ReadMe, I'm implementing use of the Command Console (instead of having hardcode every additional input/output parameter I need into the UE plugin itself):

But the Command Console doesn't seem to be having any effect on the flight model in game. I'm able to input and read every FCS command, but it simply doesn't do anything to the aircraft flight model when running.

So I went back and redownloaded reference app, compiled+ran it (I'm using UE 5.5, overcame the toolset issues etc, and have it running perfectly - until I make these below edits with Command Console). Here's the default flight control node setup (which runs each Event Tick):

Now, for example, I remove the Set->Commands nodes and start with a Command Console node just to do Aileron command input (with fcs/aileron-cmd-norm - which is read and write) I input the same normalised signal from before and have a print node to see the live output from the Command Console.

The result is that the aileron doesn't move (both animation and the flight model) but the output from the Command Console still gives the correct aileron demand that I input with the game pad? Note: it's not just an animation issue, I've done this with all the other inputs connected to the old Set->Command function and the inputs work with the Set->Commands node setup, but nothing works with the Command Console.

Am I missing something in how the Command Console function is intended to operate?

[gallonmate]

The Reference App has the main aircraft controls hardcoded and is being updated every simulation step using the variables directly from Commands, as seen in the Blueprint. Commands is being copied via c++, regardless of the blueprint code, immediately before every simulation step, so it overrides any values you set outside of using the Commands variable.

You can use the Commands variable that already exists in the blueprint and update those values as needed. There's no need to use the Command Console Node for those controls. Although if for some reason you do not wish to use the Commands structure variable for the main controls, then you can edit the plugin in c++, by commenting out/deleting the controls you wish to override. Below is a section of code that sends the Commands values to JSBSim. The first one is for the Ailerons:

jsbsim/UnrealEngine/Plugins/JSBSimFlightDynamicsModel/Source/JSBSimFlightDynamicsModel/Private/JSBSimMovementComponent.cpp

Lines 593 to 605 in 318c804

	void UJSBSimMovementComponent::CopyToJSBSim()
	{
	// Basic flight controls
	FCS->SetDaCmd(Commands.Aileron);
	FCS->SetRollTrimCmd(Commands.RollTrim);
	FCS->SetDeCmd(Commands.Elevator);
	FCS->SetPitchTrimCmd(Commands.PitchTrim);
	FCS->SetDrCmd(-Commands.Rudder); // Rudder
	FCS->SetDsCmd(Commands.Rudder); // Steering
	FCS->SetYawTrimCmd(-Commands.YawTrim);
	FCS->SetDfCmd(Commands.Flap);
	FCS->SetDsbCmd(Commands.SpeedBrake);
	FCS->SetDspCmd(Commands.Spoiler);

[SLGY]

Thanks, that's explained everything now. It seems the intent of making the Command Console was only to access inputs/outputs that aren't already in the Commands struct. After I hardcoded a number of different parameters to make a relatively complex aircraft HUD, I saw that the Command Console (mentioned in the ReadMe) would save me having to do that each time - but I made the mistake of making a new aircraft from scratch based solely on the Command Console.
Anyways, now I know what options I have moving forward. Thanks again.
Is it worth tagging the relevant person to update the UE readme section to make this clearer maybe?