Project

General

Profile

Bug #25873

KAL -1000 Play position action group does not work as intended

Added by dnbattley 7 months ago. Updated about 1 month ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
Robotics
Target version:
-
Start date:
07/31/2020
% Done:

0%

Version:
Platform:
Linux
Expansion:
Breaking Ground
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

The KAL-1000 "play position" action group behaves unexpectedly: when connecting one KAL to control another KAL via the play position it seemingly connects the relative play position of both KALs rather than accepting the input of the control. Thus, setting one KAL "controller" to set another KAL "subordinate" to e.g. position 0 it instead plays subordinate from 0->1 in tandem (i.e. not respecting the play speed or track length of subordinate) with the play position of controller. Changing controller priority has no effect. Editing KAL in flight has no effect. The value of the "play position" setting has no effect.

The effect can also be daisy-chained (e.g. Controller sets play position of subordinate, which in turn sets play position of "additional", and all three KALs will play through in tandem when controller is activated).

To recreate, simply add two KALs, using one to control the play position of the other. The effect is recreated in both the VAB editor (by "scrolling" through the controller play position) and in flight.

History

#2 Updated by dnbattley 4 months ago

Since this bug has not been confirmed, I assume it was not immediately clear what the issue is, so add pictures:

Here are two KAL's. The upper KAL (A) is set to determine the play position of the lower KAL (B)

However, as can be seen from the pictures, moving the play position of KAL A is causing the play position of KAL B to vary exactly with the play position of KAL A, and not with the SET VALUE of the play position within KAL A's editor (which would be the expected behaviour)

#3 Updated by [email protected] about 1 month ago

Confirmed:
Now i noticed this bug when i actually needed it. I can't put this on confirm state, some update on this site?

Also available in: Atom PDF