[X] My Assistant

how do i do that? will it cost money?

Google VPS and take your pick. Yes.

what version? do i need to install it?

firefox version. just check firefox infos.

firefox version. just check firefox infos.

51.0.1 (32-bit)

51.0.1 (32-bit)

uhu. currently tenboro is busy on a crusade against that particular version. check his twitter for more details. you may try with a rollback to v50, if possible. if the thing you mentioned started a few days ago, that may be the cause

No, hentaiverse has nothing to do with the HTTPS issue. I'm pretty sure it's just ordinary ping issues.

Anyway, didn't 51.0.1 fixed the problem 51.0.0 had? I still have Firefox 50, waiting to update.

oh, alright. sorry (IMG:[invalid] style_emoticons/default/heh.gif)

Just had a thought with the ping thing ...

if you go to cmd and do

CODE

ping -n 100 hentaiverse.org

then wait a good while (it does 100 pings instead of the normal 4 or so to have some bad pings in there as well)

then get your average ping in ms, add 150ms to that (should be around that to process HV requests serverside, can't find the exact value i had written down somewhere)
then multiply that value with ( 1 + (packetloss-percent / 50) )
then add 10ms for browser rendering time
and then divide 1000 by the resulting value you should get a pretty good guess as far as your maximum average t/s might actually be ...

So an example for me

CODE

avg rtt = 45ms
packetloss = 2%

45 + 150 = 195
195 * ( 1 + ( 2 / 50 ) ) =
    195 * 1.04 = 202.8
202.8 + 10 = 212.8
1000 / 212.8 = 4.7

So my theoretical max avg t/s would be 4.7, IF i wouldn't have to do script stuff and a little wait for round ends and so on, so that's about another 5ms each turn and 50ms each round...
With avg 8 turns per round that gets up to (50 + 8 * 10) / 9 = 130 / 9 = 14.4 ms added to each turn, so ...
227.2ms each avg turn, then add initial render time of about 50ms each round, that adds another 5.5ms avg, so 232.7ms avg ... which yields about 4.3 t/s ... which would still be above the 4t/s max value ...

With brainless 1H i actually was able to get up to 3.9 t/s in FSM RoB. The additional time gets added from buffing and healing.
With Imperil mage that went down to 3.4 t/s for the additional imperil > check if imperiled > repeat until all is imperiled before starting the hover-whacking. (for IW, GF or regular arenas that goes down to 2.2t/s as there is a lot more to imperil and more waiting for rounds to end)

Can anyone cross-check if i'm in the right ballpark here with their values? (IMG:[invalid] style_emoticons/default/happy.gif)

CODE

avg rtt = 83ms
packetloss = 0%

83 + 150 = 233
233 * ( 1 + ( 0 / 50 ) ) =
    233 * 1 = 233
233 + 10 = 243
1000 / 243 = 4.1 t/s ~ 4.0 t/s

math says i should reach turn cap as well. i love math (IMG:[invalid] style_emoticons/default/wub.gif)

...

Test done, medium ping: 249ms right now, 0 packet loss.
So 1000/(249+150+10+15)=2.35 t/s

Hey, seems about right (IMG:[invalid] style_emoticons/default/smile.gif)

math says i should reach turn cap as well. i love math (IMG:[invalid] style_emoticons/default/wub.gif)

I still don't understand what is the problem with your connection...

This post has been edited by gianfrix94: Feb 4 2017, 20:09

btw, with alt.hentaiverse i have 46ms average. hmmm...

[edit]: and 2.15 t/s on a quick 7 round arena (IMG:[invalid] style_emoticons/default/ohmy.gif)

This post has been edited by Scremaz: Feb 4 2017, 20:11

Just had a thought with the ping thing ...

48ms average, 0% loss, ~4.81 t/s max
With imperil I get around 2.5-3.0 t/s in normal arenas, SG ones can go up to ~3.5 t/s, FSM RoB sometimes reaches the full 4 t/s.

btw, with alt.hentaiverse i have 46ms average. hmmm...

[edit]: and 2.15 t/s on a quick 7 round arena (IMG:[invalid] style_emoticons/default/ohmy.gif)

Test alt more, maybe you'll be able to play decently (IMG:[invalid] style_emoticons/default/ohmy.gif)

I still don't understand what is the problem with your connection...

neither do i. but guess i'll do a PF T&T with alt.hv just to check if it is stable enough.

Test alt more, maybe you'll be able to play decently (IMG:[invalid] style_emoticons/default/ohmy.gif)

my thoughts exactly.



btw, net experts: does the fact that alt may potentially work better for me than regular hv say anything?

This post has been edited by Scremaz: Feb 4 2017, 20:15

btw, with alt.hentaiverse i have 46ms average. hmmm...

[edit]: and 2.15 t/s on a quick 7 round arena (IMG:[invalid] style_emoticons/default/ohmy.gif)

hentaiverse.org is a bit crappy today from Italy (depends on routing, usually they are very close).
I more or less have the same values (HV felt a bit slower than usual)

This post has been edited by Sapo84: Feb 4 2017, 20:18

my thoughts exactly.
btw, net experts: does the fact that alt may potentially work better for me than regular hv say anything?

The routing? Try tracert.

This post has been edited by gianfrix94: Feb 4 2017, 20:21

hentaiverse.org is a bit crappy today from Italy (depends on routing, usually they are very close).
I more or less have the same values (HV felt a bit slower than usual)

For some zone of Italy, but not for me.

btw, with alt.hentaiverse i have 46ms average. hmmm...

[edit]: and 2.15 t/s on a quick 7 round arena (IMG:[invalid] style_emoticons/default/ohmy.gif)

I found it best to test t/s on FSM or TTnT ROB's as it's just 1 round and you don't have other things interfering there.

btw, net experts: does the fact that alt may potentially work better for me than regular hv say anything?

Just did a traceroute that way, for me alt has 3 hops less and seems to be in a different data center, i think, so pretty sure it's a routing thing on your ISP side. (i even go through a totally different IX on the way to alt, peering ftw ...)

The routing? Try tracert.

Just did a traceroute that way, for me alt has 3 hops less and seems to be in a different data center, i think, so pretty sure it's a routing thing on your ISP side. (i even go through a totally different IX on the way to alt, peering ftw ...)

already posted a few days ago. here you are though:

CODE

hentaiverse.org [94.100.24.93]

  1     1 ms    <1 ms     1 ms  192.168.2.1
  2     *        *        *     Richiesta scaduta.
  3     *       21 ms    21 ms  xxx.xxx.xxx.xxx
  4    25 ms    22 ms    22 ms  xxx.xxx.xxx.xxx
  5     *       31 ms    30 ms  xxx.xxx.xxx.xxx
  6     *        *        *     Richiesta scaduta.
  7     *       29 ms    28 ms  et7-3-0-51.milano51.mil.seabone.net [195.22.196.169]
  8     *       29 ms    28 ms  ntt-verio.milano51.mil.seabone.net [93.186.128.157]
  9     *       59 ms    54 ms  ae-0.r24.amstnl02.nl.bb.gin.ntt.net [129.250.3.178]
10     *       86 ms    91 ms  ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
11     *       63 ms    61 ms  ae-0.swiftway.amstnl02.nl.bb.gin.ntt.net [81.20.64.62]
12     *      233 ms   229 ms  251.17.100.94.static.swiftway.net [94.100.17.251]
13   284 ms   286 ms   281 ms  93.24.100.94.static.swiftnoc.com [94.100.24.93]

alt.hentaiverse.org [81.171.14.120]

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     *        *        *     Richiesta scaduta.
  3     *       20 ms    21 ms  xxx.xxx.xxx.xxx
  4    25 ms    30 ms    21 ms  xxx.xxx.xxx.xxx
  5     *       31 ms    24 ms  xxx.xxx.xxx.xxx
  6     *        *        *     Richiesta scaduta.
  7   258 ms   292 ms   268 ms  racc.milano50.mil.seabone.net [195.22.213.218]
  8     *        *       48 ms  fiberring.amster51.ams.seabone.net [195.22.213.25]
  9     *        *        *     Richiesta scaduta.
10     *       48 ms    47 ms  po-1004.ce02.ams-01.nl.leaseweb.net [37.48.95.203]
11    48 ms    46 ms    52 ms  81.171.14.120

IPs nearest to my location have been censored for privacy reasons, but between the two servers they differed only for the last triplets.
either way, seems both requests reach Milan here in italy, then paths are quite different...

For some zone of Italy, but not for me.

showoff (IMG:[invalid] style_emoticons/default/dry.gif)

I found it best to test t/s on FSM or TTnT ROB's as it's just 1 round and you don't have other things interfering there.

i'd gladly do that, but i'm sitting at 2 tokens atm (IMG:[invalid] style_emoticons/default/heh.gif)

already posted a few days ago. here you are though:

CODE

hentaiverse.org [94.100.24.93]
8< --- snip --- >8
  8     *       29 ms    28 ms  ntt-verio.milano51.mil.seabone.net [93.186.128.157]
  9     *       59 ms    54 ms  ae-0.r24.amstnl02.nl.bb.gin.ntt.net [129.250.3.178]
8< --- snip --- >8

alt.hentaiverse.org [81.171.14.120]
8< --- snip --- >8
  7   258 ms   292 ms   268 ms  racc.milano50.mil.seabone.net [195.22.213.218]
  8     *        *       48 ms  fiberring.amster51.ams.seabone.net [195.22.213.25]
8< --- snip --- >8

Noticed that for regular HV you're switching backbones here.
And for alt.HV you're staying with the same carrier.

Also, checked and milano50 and milano51 seem to be in the same location/interchangable

i'd gladly do that, but i'm sitting at 2 tokens atm (IMG:[invalid] style_emoticons/default/heh.gif)

TBH i also just had the 5 when this came up to test (IMG:[invalid] style_emoticons/default/heh.gif)