Jump to content
SubSpace Forum Network

Recommended Posts

Posted

i will be making this semi-public soon, to a handpicked group of individuals to assist me in fixing bugs and being a general second set of eyes for things i havnt seen.

it will be like that for an undetermined period of time, and after that i will probably making this completely open to the public.

there will probably be a period after that where i will be updating in a way that ignores possible contributions from outside sources due to rapid development, in which updates should be sent directly to me.

after that, people will be able to make changes in the exact same way they would to the asss core currently.

  • Replies 58
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Posted (edited)

UPDATE:

core modules loaded: fuck it check modules.conf
total source files to date: a bunch

DEMO ATTACHED TO THIS POST

next modules to write: encryption game physics


i forgot to mention that this one is interactive:
up down left right f1 f2



.

sscpreview2.zip

Edited by Cheese
Posted

3:Cheese!>  first message ever recieved by my new client:
3:Cheese!>  You have been disconnected because of lag (no data).
3:Cheese!>  X_x
3:Cheese!>  had to do it byte by byte on an ascii table :(

 

 

lol

Posted

 Cheese!> ?lag -v
SSCclient: s2c ping: 0 0 (0-0) (reported by client)
SSCclient: c2s ping: 10001 9993 (0-10000) (from position pkt times)
SSCclient: rel ping: 27 34 (0-336) (reliable ping)
SSCclient: effective ping: 2515 (average of above)
SSCclient: ploss: s2c: 0.00 c2s: 0.00 s2cwpn: 0.00
SSCclient: reliable dups: -nan%  reliable resends: 0.00%
SSCclient: s2c slow: 0/0  s2c fast: 0/0
SSCclient: avg bw in/out=32/4  ignoringwpns=100%  dropped=0
SSCclient: bwlimit=10382 b/s, burst 2048 b
SSCclient: lag too high to play
SSCclient: lag too high to carry flags or balls
I {0} [Cheese!] command to [sSCclient]: lag -v
   Cheese!> ?lag
SSCclient: avg ping: 2514  ploss: s2c: 0.00 c2s: 0.00
I {0} [Cheese!] command to [sSCclient]: lag

 

 

 

no, i think its averaging things, and its using a default of like 10000 or something?

 

ive got this in the keepalive
    pos.time=current_ticks();

Posted

   Cheese!> ?lag
SSCclient: avg ping: 18  ploss: s2c: 0.00 c2s: 0.00
I {0} [Cheese!] command to [sSCclient]: lag
   Cheese!> ?lag -v
SSCclient: s2c ping: 0 0 (0-0) (reported by client)
SSCclient: c2s ping: 0 0 (0-0) (from position pkt times)
SSCclient: rel ping: 31 36 (0-696) (reliable ping)
SSCclient: effective ping: 18 (average of above)
SSCclient: ploss: s2c: 0.00 c2s: 0.00 s2cwpn: 0.00
SSCclient: reliable dups: -nan%  reliable resends: 0.00%
SSCclient: s2c slow: 0/0  s2c fast: 0/0
SSCclient: avg bw in/out=121/16  ignoringwpns=0%  dropped=0
SSCclient: bwlimit=6920 b/s, burst 2048 b
I {0} [Cheese!] command to [sSCclient]: lag -v

 

 

 


$$$$$$$$$$

Posted

it seems the downside to that is this:


    isnewer = TICK_DIFF(pos->time, data->pos.time) > 0;
    /* only copy if the new one is later */
    if (isnewer || isfake)

 

 

now what the fuck am i supposed to do :\

  • 2 weeks later...
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...