µTorrent reporting incorrect numbers peers and seeds

[Stone]

you have to look at the ones that say "in swarm"

The other values are the internal peer cache

Then how can it be that this "internal peer cache" is lower than "in swarm" values after few weeks of downloading torrent?

[Pongu]

Dear Firon

We seem to be going arround in circles..... and missing the point that µTorrent realy does report incorrect numbers of peers and seeds.

May I compile screen shots and some http request / response logs to enable you to get to the bottom of the issue ?

As I have posted before, TorrentSpy gets it right every time..and my Tracker does indeed send the correct info.

It was sorta important as on our forum µTorrent is the recomended client and I wanted our members and staff to be able to see accurate (to the last scrape) numbers at a glance.

[Firon]

It behaves differently (not really incorrect) for any started torrents, but stopped torrents do show the "proper values" (so long as you turn on bt.scrape_stopped)

[Pongu]

Thank you for the prompt reply Firon

I will examine a few stoped torrents later tonight... but in the mean time, I wonder if you could please define "It behaves differently", as I would (and I'm sure many others would also) love to be able to understand the reasoning process that µTorrent uses.

[Firon]

I believe for started torrents, in the listview, it shows the number of seeds/peers in the internal peer cache, unless the scrape values are larger than the internal peer cache values, in which case it shows the scrape values.