MOSS Logfile bug after update when set to CrossFire

What is Moss ? Forums Bugs MOSS Logfile bug after update when set to CrossFire

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #5187
    goodcupadmin
    Participant

    Hello,

    After the new MOSS update (version: 5,0,4,0) MOSS no longer logs the processes or the dll’s in the final logfile when the game is set to CrossFire.

    MOSS captures processes along side SHA-256 as well as paths as intended if I select “Generic Game” (ofc no dll logging since there is no specific game selected).

    But when set to CrossFire I get a log without process or dll logging (except for the process statistics summary at the end).
    It looks like this: https://ufile.io/i0cr1bf4

    Thank you.

    #5188
    goodcupadmin
    Participant

    I do not know if this could be happening to other games as well since I only use MOSS with CrossFire.

    • This reply was modified 1 month, 4 weeks ago by goodcupadmin.
    #5191
    goodcupadmin
    Participant

    Here is another link to the LogFile since the one I posted before expired.

    https://ufile.io/lrci844y

    #5192
    ADM_nohope
    Keymaster

    oops , get the update 🙁

    #5193
    goodcupadmin
    Participant

    Got the update (5,0,5,0) but:

    Still does not capture processes with SHA-256 and path.

    DLL logging seems quite limited compared to before (before 5,0,3,0).

    For example, I remember profapi.dll being detected every time before, that is no longer the case.

    #5199
    ADM_nohope
    Keymaster

    you were allowed to start moss after the game , it’s now fixed

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.