- This topic has 12 replies, 3 voices, and was last updated 3 years, 3 months ago by
.
-
Posts
-
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/i0cr1bf4Thank you.
Here is another link to the LogFile since the one I posted before expired.
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.
Here is what I mean:
Old LogFile (good): https://ufile.io/o8kf9eok
with SHA2(process & path) and in game SHA2(dll & path).New Logfile (problem): https://ufile.io/7uqnu1ez
without SHA2(process & path) and very few DLL detected.Here is what I mean:
Old LogFile (good): https://ufile.io/u6p98sby
With Process (SHA2 & path) and in-game DLL (SHA2 & path)New LogFile (bad): https://ufile.io/uyr4kzp1
Still without Process and very few DLLs detected.
Here is what I mean:Old LogFile (good): https://ufile.io/u6p98sby
With Process (SHA2 & path) and in-game DLL (SHA2 & path)New LogFile (bad): https://ufile.io/uyr4kzp1
Still without Process and very few DLLs detected.
The following is about CrossFire on the latest MOSS version: 5,0,6,0
-MOSS is not logging active processes before the game launch properly and the DLL logging seems quite limited compared to old versions (before 5,0,3,0).
Here is what I mean:
Old LogFile (good), [before version 5,0,3,0]: https://ufile.io/u6p98sby
—Processes before game start (SHA2 & path) = OK
—in-game DLLs after launch (SHA2 & path) = OKNew LogFile (BUG), [after latest updates]: https://uploadfiles.io/a5mh1xob
—ONLY crss.exe and wininit.exe detected before game launch.
—in-game DLLs detected are fewer than in older versions. (not 100% sure about this)Another example to explain what I mean:
Screenshot of OLD (GOOD) Logfile: https://ufile.io/8x1opvut
Screenshot of NEW (BUG) Logfile: https://ufile.io/fgm9hzdkI can’t reply with my other account on these forums anymore i dont know why so i made a new one “goodcupadmin2”
The following is about CrossFire on the latest MOSS version: 5,0,6,0
-MOSS is not logging active processes before the game launch properly and the DLL logging seems quite limited compared to old versions (before 5,0,3,0).
Here is what I mean:
Old LogFile (good), [before version 5,0,3,0]: https://ufile.io/u6p98sby
—Processes before game start (SHA2 & path) = OK
—in-game DLLs after launch (SHA2 & path) = OKNew LogFile (BUG), [after latest updates]: https://uploadfiles.io/a5mh1xob
—Only crss.exe and winlogon.exe detected before game launch.
—in-game DLLs detected are very few compared to older versions. (I am not 100% sure about this)Another example to explain what I mean:
Screenshot of OLD Logfile: https://ufile.io/8x1opvut
Screenshot of NEW Logfile: https://ufile.io/fgm9hzdkHere is what I mean:
Old LogFile (good): https://ufile.io/u6p98sby
With Process (SHA2 & path) and in-game DLL (SHA2 & path)New LogFile (bad): https://ufile.io/uyr4kzp1 version (5,0,5,0)
Still without process (no SHA2 & no path) and very few in game DLL detected.
- You must be logged in to reply to this topic.