rugas

Not the biggest deal, but still: when peer doesn't keep "connection" constantly, but periodically goes away and returns, "Uploaded" column gets reset to 0 on each "reconnection": Observed on 3.3.1.29335. In earlier versions (3.2.3) it used to keep cumulative amount for each IP address.

So' date=' I suggest that you try to reproduce the good behavior I see... maybe by using my settings below? ... Btw, this is w/o upload limit: http://thumbnails104.imagebam.com/24010/3d8f9f240095442.jpg I have tried, and you know what? With settings_331_1M.dat copied to replace the original settings.dat the good behavior is observed with 3.3.1, all peers are having nice big U's. Trick is certainly not in "basic" pages, like Bandwidth, Bittorrent or Queueing - since I've changed settings there back to my liking. I'm not in condition right now to analyze all in Advanced, but because I had initially installed 3.3 on new Win8 system, it's for sure one of settings in that section which differs from defaults.

I confirm that this problem exists with 3.3: Looks fine here (3.3.1/29213). The only problem I can see is - unbalanced allocation of speed - mainly - to one peer. As I understand it this is due to semi broken upload limiter handler. W/O setting an upload limit - all looks fine... http://thumbnails104.imagebam.com/24007/7b8a33240064716.jpg With 3.3.1 I have the same problem as with 3.3... So - it's even worse: it's harder to fix the problem if it's not easily reproducible

Yeah' date=' confirm this. 3.3, 3.3.1 used only one slot per torrent when seeding (only one flag "U"). Please, fix this) For example: [url']http://dl.dropbox.com/u/56667031/1.png http://dl.dropbox.com/u/56667031/2.png I confirm that this problem exists with 3.3: 1. I set "Number of upload slots per torrent" to 40. 2. 20 peers are connected to a seeding torrent. 3. Of them only one has big U flag and receives from my client. 4. The rest have small u flag (they want to receive, but my client refuses to send to them). As soon as I quickly replace 3.3 with 3.2.3 (just stopping client, overwriting exe file and restarting, so all the settings are the same), the problems is solved: all 20 peers on the same torrent have big U flag and receives from my client. Going back to 3.3 in the same manner reproduces the problem. And switching again to 3.2.3 immediately solves it.