Skip to content

Reboot after using raw controls can make cooked controls flicker to 0 [BUG] #2857

@nuggreat

Description

@nuggreat

Strange bug with locked throttle, boot file, and core reboot.

  1. launch a craft with a kOS core.
  2. create a file with this code in it
PRINT "just rebooted".
WAIT 1.
PRINT "locking throttle".
lock throttle to 1.
WAIT 0.5.
PRINT "setting control fore to 1".
SET SHIP:CONTROL:FORE TO 1.
WAIT 1.
PRINT "setting control fore to 0".
SET SHIP:CONTROL:FORE TO 0.
WAIT 1.
PRINT "setting control fore to 1".
SET SHIP:CONTROL:FORE TO 1.
WAIT 1.
PRINT "setting control fore to 0".
SET SHIP:CONTROL:FORE TO 0.
WAIT 1.
REBOOT.
  1. set your new file to be the cores boot file
  2. reboot the core by typing REBOOT. in the terminal.

This will cause the THROTTLE will flicker to 0 for one tick about 2 ticks after the SET SHIP:CONTROL:FORE TO .` executes.

The THROTTLE will only flicker the first time SHIP:CONTROL:FORE is set after the reboot.

EDIT: further testing shows that you don't need the file to be a boot file the kOS core must simply have been rebooted before the file executes.

EDIT2: Bug only appears to exist in kOS v1.3.x though I only tested 1.3.1 I assume it shows up in 1.3.0. It does not occue in kOS v1.2.1. All testing was done in KSP 1.10.1 with both Breaking Ground and Making History installed, no other mods where installed.

EDIT3: Originally found by user Angel-0a on reddit

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugWeird outcome is probably not what the mod programmer expected.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions