after updating the game, now the game itself does not read the signature of the mods that were encoded (obfuscate), although the DSUtils utility writes that the signature has no errors. because of this, mod assemblies now break and it is impossible to play with signature verification
- Operating System
- Windows 10 x64
and not obfuscate mods have problem with signature. for example JSRS not reading signature after update.
that were encoded (obfuscate)
Weirdly manipulated files with the target of making them unreadable for pbo tools are obviously not officially supported. So them breaking is not an issue.
the problem is not with hacking, but with signatures of encoded and non-encoded files. and if bis advertises a utility (Mikero tools) on the wiki with a paid part for encoding, then they support this question
and if bis advertises a utility (Mikero tools) on the wiki with a paid part for encoding, then they support this question
1st BIS is a company making military simulators and they are completely unrelated to this feedback tracker. This is the BI feedback tracker.
2nd encoded files, with the sole purpose of messing with pbo tools, stretching the bounds of what is accepted as valid syntax, is not supported obviously. PBO obfuscation is made to break pbo unpackers, and oh wonder.. It breaks Arma's own pbo unpacking for signature checking.. How weird! It does exactly what it wanted to do!
3rd BI doesn't advertise anything on the wiki, The wiki is open for everyone, the page about Mikeros tools was created by... Mikero, not BI, and no they don't support PBO obfuscation.
In any case, BI is aware of this bug, they made a Twitter post and on the Arma III Discord, they said that they dealt with this problem in the day.
PBO obfuscated or not, there is a problem with the signatures check and it will be solved.