Page 1 of 6 12345 ... LastLast
Results 1 to 10 of 55

  Click here to go to the first Developer post in this thread.  

Thread: [Answered] "Wrong Signature" - v2 Signatures and BAF/PMC

  1. #1

    [Answered] "Wrong Signature" - v2 Signatures and BAF/PMC

    I have enabled v2 signatures on my server, which is running OA with BAF and PMC full versions. I connect with my client, which also has BAF and PMC full versions. After a few minutes in game, I am consistently kicked (and banned in the ban.txt file) for "Wrong signature for file ....." where the file is either a BAF or PMC file (it's not consistent).

    I am using Steam to install the content for both, and have done a Verify Cache multiple times to ensure everything is fine. If I switch back to version 1 signatures, I don't get the error / kick / ban.

    Please see bug report on Dev Heaven at #21861
    Last edited by Dwarden; Jul 6 2011 at 16:10. Reason: Added DH bug report link

  2. #2

  3.   Click here to go to the next Developer post in this thread.   #3
    what ^ he want to say, if You host dedicated server, make sure YOU don't have ANY installed DLC on it ...

    only DLClite needed for dedicated server

  4. #4
    Well, I don't think that's causing my problem. I've run the server fine with the "full DLC" with v1 signatures and there hasn't been a problem. What's strange is that it appears to actually detect corruption on the client side, as others can connect and play fine with the server set to v2 signatures. They don't get kicked/banned.

    I removed the DLC on the server. Still get the kick/ban.

    I deleted the BAF and PMC folders under OA. Then I relaunched OA to get it to reinstall BAF and PMC. Still get the kick / ban. It doesn't happen to others, though.
    Last edited by Focher; Jul 1 2011 at 07:56.

  5. #5
    I have now confirmed this happening to me on two different machines (home and a work machine). I seriously doubt it's corruption because I would also get kicked with v1 signatures if that were the case, but it only happens with v2.

  6. #6

    Client Details

    Client BAF and PMC file list with MD5 hashes
    Spoiler:

  7. #7

    Server details

    Server IP: games.apmea.net

    Server file list with MD5 hashes
    Spoiler:

  8. #8
    Been away a few days and since Focher has the same issue and posted details in here rather than the other thread I will post my details here.

    @Focher, hope you don't mind that I added my details here but thopefully it will help us get it sorted, also to prevent you getting banned all of the time change your server.cfg file to have:
    Spoiler:


    The servers are all uploaded from disk copies of A2+CO and NO PMC/BAF files installed on them.

    IP's of servers:
    217.146.93.75 - main public server
    217.146.85.231 - locked training/match server
    217.146.85.233 - mission/script testing server

    Server MD5 hashes (only listed folders I thought relevant):
    \Keys\
    Spoiler:

    \Expansion\Keys\
    Spoiler:

    \Common\
    Spoiler:

    Client MD5 hashes:
    \Keys\
    Spoiler:

    \Expansion\Keys\
    Spoiler:

    \BAF\
    Spoiler:

    \PMC\
    Spoiler:

    \Common\
    Spoiler:


    I can provide any other details as necessary to try and nail the problem as a few other server admins that I have talked to have the same issues and their MD5 hashes match mine.

    Additional information added:
    server.cfg (or at least the equivalent file)
    Spoiler:
    Last edited by BearBison; Jul 6 2011 at 20:39. Reason: More information

  9. #9
    We have the same issues running the Linux server. (Our old Windows server also had the issue as well with 1.59.)

    I compared the MD5 hashes to a retail version of the game as well and there were no differences. Both .bikey files are present as well. The full BAF and PMC data is not installed.

  10. #10
    same problem here with v2 enabled on dedicated CO server with no mods

Page 1 of 6 12345 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •