Not a bug Signal Logic in relation with Turrets is bugged

Discussion in 'Archive (Read Only)' started by japp_02, Jan 30, 2022.

  1. japp_02

    japp_02 Commander

    Joined:
    Feb 11, 2021
    Messages:
    525
    Likes Received:
    200
    Build:
    1.72 3647

    Mode
    :
    All modes or Creative only

    Reproducibility:
    Always

    Type:
    Triggers, Sensors

    Summary:
    Signal logic leads to wrong results with Turrets when they are not concerned.

    Description:
    Even if no signal logic is programed for the Turrets, the turrets in the Custom definition wll always swtich to middle position and therefore consume energy if you program a signal which is not related to turrets like:
    On/Off > xxxxx > OFF (for example xxxxx = PowerSave). In order to keep turrets switched off I need to do this manually every time. The turrets in the Custom section should remain off if off, and on if on, because the signal logic I defined is not related to them.

    Steps to Reproduce:
    1) Define 'Turrets' in P > Main > Custom; have all turrets in turret group linked to Custom. Switch turrets OFF.

    2)
    Define PowerSave in P > Main > Signals with the purpose to shut off Thrusters and Manual Weapons (I would also shut off the Turrets but I don't for the scope of showing the bug,).

    3)
    In P > Signal Logic you set a) for each thruster: PowerSave > Follow > Invert; b) for each Manual Weapon: PowerSave > Off.

    As you can see, turrets are not concerned wtih the steps 2) and 3) above.
    Now switch PowerSave ON and OFF and you will see the Custom Turret switch in middle position instead of remaining OFF. Problem with that: It will consume energy and I need to always switch the turrets off, the entire PowerSave becomes FUTILE.
     
    #1
    Last edited: Jan 30, 2022
  2. japp_02

    japp_02 Commander

    Joined:
    Feb 11, 2021
    Messages:
    525
    Likes Received:
    200
    Possibly NOT a bug but a mishandling of the signal logic menu.

    I didn't consider that I removed a Custom definition of 'Turrets' in P > Main > Custom, by just renaming it to 'Custom1' as it was before, but this doesn't remove a possible link to Custom1; in the same vessel where I did all this signal logic, in the Device section, I have to check ALL groups to see if they don't link anymore to wrong Custom shortcuts, which I didn't above. I have found 2 constructors linked to 'Custom1' which I didn't change to '--', this could explain why re-defining the 'Turrets' in the same slot shows the error described above.

    In short, I must redo the procedure above to assure Reproducability. Please stay tuned for my result which I will publish here.
     
    #2
    Last edited: Jan 31, 2022
    Pach likes this.
  3. japp_02

    japp_02 Commander

    Joined:
    Feb 11, 2021
    Messages:
    525
    Likes Received:
    200
    Ok, until I see clearly > NOT a bug. I will start a question in the General Discussion to know more about Signal Logic in this case.
     
    #3
    Hummel-o-War likes this.

Share This Page