µTorrent 3.0 "Falcon" (32-bit) alpha 25207

[DreadWingKnight]

Did you actually fully close down 2.0.4 first?

[thatsaabguy]

Did you actually fully close down 2.0.4 first?

....oh.

I'm a dolt. Worked fine, when I did that. Yeah. I'm a just crawl back up under my rock now, thanks...

[mrMan01]

@mrMan01: As I understand it, µTorrent 3.0 requires HTTP cookies to be sent now.

Thanks Utima that was the problem,

I changed my script to this (which gets the list of active torrents back).

Code is powershell

$port = "80"

$server = "server"

$user = "Guest123aHjp87dw"

$pass = $null

$utorrentUrl = "http://$server`:$port/gui/"

$webClient = new-object System.Net.WebClient

$webClient.Headers.Add("user-agent", "PowerShell Script")

$webClient.Credentials = new-object System.Net.NetworkCredential($user, $pass)

$result = $webClient.DownloadString($utorrentUrl + "token.html")

[string]$cookies = $webClient.ResponseHeaders["Set-Cookie"]

if ($result -match ".*<div[^>]*id=[`"`']token[`"`'][^>]*>([^<]*)</div>.*")

{

$token = $matches[1]

$webClient.Headers.Add("Cookie", $cookies)

$result = $webClient.DownloadString($utorrentUrl + "?list=1&token=" + $token)

}

[highlatency]

Global download limit still doesnt work

If i set it drops well below the assigned rate

fix please?

[avatarl]

Any ETA on when 3.0 becomes stable and replaces the 2.x builds?

[Hyosung]

^Uhh... 2.2 only JUST became the new Stable build.

3.0 Hasn't even come out of Alpha stage and you're asking for a Stable ETA?

Dude... wrong post...

"It'll be out when it's out"

No need to ask about an ETA on releases.

[funkydude]

Curious if one of the devs (or someone) could explain why I still need a TCP port open when I force UDP only? Could uT be smart about this and check that my transport is set to UDP only, and as so, only map a UDP port?

[ktetch]

With b22941, I'm seeing a lot of 'yellow' in the pieces.

It's starting pieces and not finishing them. I'm talking, near the end of a torrent, if it's got 1100 x512kb pieces, we'll have 20mb to go, and 150 pieces to go, all partly downloaded, with just a chunk or two left. It then takes forever to hit endgame mode, if ever.

[Dexter_prog]

I noticied that it uses the upload priorities differently. I have like 10 or 15 torrents seeding and it would only seed from one or 2, while uTorrent 2.x seeds from all of them. Is is a new feature? I couldn't find anything in the options to disable it

[Firon]

New 3.0 up.

[Hyosung]

Thanks for the update, quite a big change log there. Keep it up.

[fowl]

- Feature: restart application after reboot caused by windows update / install if OS supports.

Woo, you did my idea!

I suppose now I'll have to try the brave new world of 3.0 alpha instead of the relative comfort of 2.2 to test it out... =)

[zdnko]

The Bandwidth Allocation context sub-menu don't works properly:

Selecting Low it switch to Normal

Selecting Normal it switch to High

Selecting High it switch to ??? (in Bw.Alloc you can see: About: %sPublisher: %SRelease Date....)

bye

[Firon]

- Feature: restart application after reboot caused by windows update / install if OS supports.

Woo, you did my idea!

I suppose now I'll have to try the brave new world of 3.0 alpha instead of the relative comfort of 2.2 to test it out... =)

Hey, it was a good idea.

[Dexter_prog]

I noticied that it uses the upload priorities differently. I have like 10 or 15 torrents seeding and it would only seed from one or 2, while uTorrent 2.x seeds from all of them. Is is a new feature? I couldn't find anything in the options to disable it

Anything on this?

[sydlexius]

The Bandwidth Allocation context sub-menu don't works properly:

Selecting Low it switch to Normal

Selecting Normal it switch to High

Selecting High it switch to ??? (in Bw.Alloc you can see: About: %sPublisher: %SRelease Date....)

bye

I'm seeing this same issue as well. Additionally, RSS downloads are also starting off in "High" priority for me.

[Switeck]

I noticied that it uses the upload priorities differently. I have like 10 or 15 torrents seeding and it would only seed from one or 2, while uTorrent 2.x seeds from all of them. Is is a new feature? I couldn't find anything in the options to disable it

That was the special upload slot global choker method added by alus. uTorrent v2.2 betas had this as well, but it was removed and replaced with the older upload slot handler from v2.0.4 in v2.2 stable release because of this and other problems with it.

[Dexter_prog]

I noticied that it uses the upload priorities differently. I have like 10 or 15 torrents seeding and it would only seed from one or 2' date=' while uTorrent 2.x seeds from all of them. Is is a new feature? I couldn't find anything in the options to disable it[/quote']That was the special upload slot global choker method added by alus. uTorrent v2.2 betas had this as well, but it was removed and replaced with the older upload slot handler from v2.0.4 in v2.2 stable release because of this and other problems with it.

Hmm, so will it continue being a part of 3 or will it be removed?

[Switeck]

If it remains, it will be greatly improved. My guess is it will be removed.

[123459]

xp sp3

ut2.2.1

ut3.0

Why?

[highlatency]

Sustained 50% CPU usage by utorrent since the last upgrade to 23217 Falcon :mad:

[Switeck]

123459,

I can't see your uTorrent settings to tell why.

[123459]

bt.tcp_rate_control false

diskio.coalesce_write_size 16777216

net.max_halfopen 10 (tcp.sys patched to 20)

net.utp_initial packet_size 5

net.utp_packet_size_intrval 9

net.utp_receive_target_delay 400 (adsl)

net.utp_target_delay 400 (adsl)

line is maxed out(4mbit down/1.8 up) but ping and speed are unstable - overloaded isp

adsl router un bridge mode(connection established wia raspppoe), mtu 1492

if you want - another time resolutions (2.2 only, 2.2.1 seems to upload unstable):

http://hotimg23.fotki.com/a/94_178/50_72/1s.png

http://hotimg23.fotki.com/a/94_178/50_72/5s.png

http://hotimg23.fotki.com/a/94_178/50_72/5m.png

http://hotimg23.fotki.com/a/94_178/50_72/30s.png

[Switeck]

Disk Cache is told to remove old blocks from the cache...so it may only stay near max *IF* uploading to many peers at once. That would be somewhat torrent-dependent and even luck-of-the-draw time-based as demand rises and falls on individual torrents.

[123459]

But, when uploading aggresively in 2.2 all ok. And without clearing, cache trashing very fast.

Can i manually specify cached piece aging time?