|
Notes |
|
|
|
|
Are you running server with SAF? |
|
|
|
|
|
If so, you will have to reupload SAF and new key to server and make sure all clients are up to date. It was updated twice today under the same version number but different keys. There was a mistake in upload process. |
|
|
|
|
|
|
|
|
We cannot reproduce this issue. All signatures seem to check out and we have not heard about any issues from large groups that we know, who tend to update instantly.
Please reinstall and verify local cache of all server addons and keys and then verify the clients. |
|
|
|
|
|
I have. It worked fine until the 0.4.3.1 update went live. I've seen loads of comments on your workshop page expressing the same issue. |
|
|
|
|
|
We are currently trying to reproduce this, but so far no luck. |
|
|
|
|
|
Tried reverting back to 0.4.3 and it works without any issue, every signature checks out. Will be using this until I see an update on this topic |
|
|
|
|
I ran another local test, all seems to pass:
https://pastebin.com/tjr4SYKt [^]
That makes 2 independent tests verified so far.
we are waiting for a confirmation from a large server project we are associated with. |
|
|
|
|
|
It was the rhsusf_c_hemtt_a4.pbo.rhsusaf.0.4.3.1.bisign that was the first in the list to fail for me. I know there were others but I can't remember which ones there were |
|
|
|
|
|
Can you please send rpt? server and client? |
|
|
|
|
|
will do tonight when I come home from work |
|
|
|
|
Just had a confirmation that a large server had 90 players yesterday evening with sig checking enabled and running on 0.4.3.1.
I am more and more under the impression that everything is ok on our end. |
|
|
|
|
|
|
|
|
|
I don't have time at the moment to do bug testing. Using 0.4.3 works fine for me so I'm going to stick with it |
|