bpmaxorz

Member
 View profile  See their activity

  • Content count

    4

  • Joined

  • Last visited

Posts posted by bpmaxorz

  2. Posted

    Ah... now we're getting somewhere. Thanks, guys ;)

    I'm sure you can see how this might be a problem for some folks, particularly when having only a single busy source. It can be hours sometimes to re-attain a slot.

    Now... would adjusting the "Delay when sending $PSR" up or down make a difference in this situation? Or maybe something else I can do in settings to reduce the instances of slot loss?

  3. Posted

    Now that's a great explanation... thanks Muscle and Crise! :)

    But (there's always a but) ...the crux of my point was this:

    I use Strong and PW daily, and I have never seen an episode of the slot loss behavior in either of those clients, and I emulate in those, too. In Apex, I will lose a slot (as shown in that video) once every 15 minutes or so.

    So what is the difference between these clients? Why does Apex do that and not the others?

  4. Posted

    I would be "matt", in this case.

    They just don't understand how it works.

    Yeah, there's the pause, but neither 1 nor 2 seconds, it's only a few miliseconds. I'm just guessing that this user has never counted how long the pause is and only says "it's 1-2 seconds"

    also the phrase "you can easily lose that slot" is false. You can lose your slot only when you are not connected, but during this pause you are not disconnected and your slot is still held. I'm just guessing that this user has never lost slot in this situation and only says "you can".

    You are right, B_M....I don't fully understand how it works... I'm not a developer. I just call it like I see it.

    The guess that I've "never counted how long the pause is" would be wrong.

    The other guess that I have "never lost a slot" would also be wrong.

    And I can prove it.

    I made it a point before posting to make proof of "matt's" statements. I made screen recordings of the very things noted in that small hub. In the screen recordings, there are both 2-3 second pauses between segments (according to the client) , and a longer pause that lead to a slot loss. I welcome and encourage the developers to view my .avi screen recordings of the things mentioned at the top of this thread.

    Before I get deemed as a trasher of the client, I want to point out that I currently run a 4 yr old hub, I know how to forward ports (otherwise, my hub wouldn't run), and I am not a noob. I am a veteran user of PW, Strong, and CrZ. The whole reason this thing came up is... none of the other clients ever exhibited the behavior outlined above. Apex has. That's it. I'm not here to bash or tarnish something that has obviously been carefully worked. I care about your effort, therefore, I speak.

    Hopefully one of the dev. team will glance once again at this thread, and be curious enough to inquire with me about the screen recordings that I took the time and effort to make for the benefit of all. Most of all, I'd like Big Muscle to see the recordings... just so a guy I respect BIGtime doesn't think "matt" is an idiot. ;-)