plugin enable/disable changes are not saved

Discussion in 'Bug Reports' started by Stefan_L_01, Oct 5, 2019.

  1. Stefan_L_01

    Stefan_L_01 Registered

    Joined:
    Nov 18, 2012
    Messages:
    345
    Likes Received:
    161
    Since latest update, the enabled changes are not written into the CustomPluginVariables.JSON.

    Change in options / plugins enabled state of a plugin -> go back (or race, doesnt matter) -> leave rf2 -> start again -> like before. Also timestamp of CustomPluginVariables.JSON does not change, so change is not written back.
     
  2. Stefan_L_01

    Stefan_L_01 Registered

    Joined:
    Nov 18, 2012
    Messages:
    345
    Likes Received:
    161
    ok i think I was able to identify the reason: It´s the DAM plugin running in Data rate = 5.
    Is it possible that when a plugin does not exit in time, and the process is killed somehow, the json saving is skipped?
     
  3. ADSTA

    ADSTA Registered

    Joined:
    Nov 19, 2011
    Messages:
    1,316
    Likes Received:
    896
    @Lazza may be able to help you concerning the DAM plugin.
     
  4. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    6,578
    Likes Received:
    2,450
    This conversation has already started to move to the DAMPlugin thread, and will probably move to a private conversation if some more diagnostics are required.

    In terms of the last question here, a plugin is 'asked' to shutdown during the game exit process, and can stall that process indefinitely (the game just waits for the plugin to finish). So a hung or busy plugin will make the game sit there and be unresponsive. If the user explicitly ends the process, or clicks on the window and Windows itself reports that the app is unresponsive and the user clicks to close the program, the game will generally not save the various config files.

    As far as my plugin goes, during game exit it searches for old unconverted log files and converts them, but it only builds those that match the current channel config. So it's possible with data rate on 5 it's finding a number of logs, while there are no matching with the rate on 3. Also logs with the full data rate (5) tend to be larger and take longer, plus one or more of them might be broken and causing the plugin to actually hang (or cause a bug that means the plugin can take a number of minutes to finish what it's doing).
     
    ADSTA likes this.

Share This Page