Jump to content

F1yer

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

 Content Type 

Posts posted by F1yer

    Refund

    in Payment and Activation

    Posted

    Thats my issue one of my issues if a gig of ram was required for online play then they should have put that in the requirements for lockon 1.1, I realize that if ram is the issue there is no software fix for it. But maybe next time they will state that a 1 gig of ram for online play.

     

    Its eighter 1 gig of ram (faster loadingtime during mission entering) or changing the timeout-settings in the Config.lua on both server and client. Its your choice, but the same issue.

    Refund

    in Payment and Activation

    Posted

    remember that this changes have to be done on the SERVER as well!! So when you join a server on HL, my guess is that you have about 1% chance to hit one that made these changes. For now at least till others start using these changes as well. Dont think 500 or 600 makes any difference.

     

    And what is the problem with 0 ping???? I really still dont see what the problem with that is. As long as you can join without lag, a ping of 0 is something visual and not a real problem. When you get a ping of over 300 or 400, now that's a problem! :)

    Refund

    in Payment and Activation

    Posted

    So am i not going to get any support for this issue?

     

    You already did but for your lag of reading here you go and PLEASE READ the message on the bottom!

     

    Originally Posted by Han

    May be this will help:

     

    MP timeouts may be tune in

    D:\11-fr-2\Config\network\config.lua

    gameTimeout = 10;

    pingPeriod = 1;

    maxPacketSize = 500;

    playerName = "noname";

    idleTimeout = 120;

     

    Rise these parameters for a server and client (timeout kick may be caused both - from a server and from a client).

     

    After testing with several online players with the same props I actually KNOW this will help!)

    What we tried is putting the gameTimeout to 600 and idleTimeout to 600. All players that had the problem could now play without problems.

×
×
  • Create New...