Archived

This topic is now archived and is closed to further replies.

ludde

µTorrent 1.5 released

Recommended Posts

I think they also should specify OS, and all security and

network related programs/drivers they may use.

Share this post


Link to post
Share on other sites

what does use more bandwhidt DHT or PXE?

i guess DHT would as it has to keep the connections to the network and the peers, but i cant be too sure about it

Share this post


Link to post
Share on other sites

The large fonts tweak is 99% perfect, it just needs one last touchup.

On the 'downloaded' bar, if it's 100%, the 1 overlaps the end of the bar.

Share this post


Link to post
Share on other sites
The large fonts tweak is 99% perfect, it just needs one last touchup.

On the 'downloaded' bar, if it's 100%, the 1 overlaps the end of the bar.

What is the large fonts tweak ?

I don't see any way to change the font...

Share this post


Link to post
Share on other sites

well, people have different size set on font in windows,

which can look bad in programs that can't adapt to it.

Share this post


Link to post
Share on other sites

PEX's bandwidth use is fairly trivial (though it can add up depending on the swarm size, huge 1000 peer swarms might make quite a bit of a difference), DHT is higher in general, but not that high.

Share this post


Link to post
Share on other sites

At my dads, i get an error when opening a torrent file.. Unable to load .torrent file...

Anyone an idea how to correct this prob.

Share this post


Link to post
Share on other sites

Nope, none of the above..

When i save torrent to disk, then open it with a dubble click, it works. But directly opening from an internet link doesn't work.

Fault in utorrent i gues.. 1.4 worked fine.

Share this post


Link to post
Share on other sites
Nope, none of the above..

When i save torrent to disk, then open it with a dubble click, it works. But directly opening from an internet link doesn't work.

Fault in utorrent i gues.. 1.4 worked fine.

Actually, I have encountered that - and it is due to how the tracker's web page is designed.

Try some other sites.

Share this post


Link to post
Share on other sites

i love to see now in all torrents iam downloading and seeding the huge amount of 1.5 users. not really thought that so few people used the beta´s in the past only to wait for the next "stable" version. so i appreciated the release to introduce encryption etc. to the wider public ;) thumbs up

Share this post


Link to post
Share on other sites

dear nTorrent developers, I'm running the largest italian bittorrent community (a village), and we have a problem.

The problem is BitComet. But The solution is not nTorrent because is still missing the udp protocol.

So I'm seriosly thinking about a BitComet tracker wide ban, this because this shity client (also in version 6.3) flood the tracker, distrupt first release superseed launches, announces itself as a new peer entry and many (too many) other nasty things. But for many reasons is an essential need for our community that a client use also udp protocol. nTorrent does not.

I hoped that 1.5 version implemented udp (like azu and BC).

So the question is, UDP protocol will be implemented? There is a beta version where we can help testing the UDP protocol?

Thanks you for writing the definitive BC killer.

Share this post


Link to post
Share on other sites

It's still on the backburner, but chances are, it won't be implemented, since the UDP tracker specs are braindead (the reason for which I'm unsure, but I'm just echoing what Firon's said before).

Share this post


Link to post
Share on other sites
TheDude is right, Lynx: it has to do with your web browser and your OS, not with your BitTorrent client.

Yep, TheDude and Nightshift, both are wright ( i think) i found where the problem lies.

It has to do with the temporary internet files.

I deleted the cookies and Temp internet files. (i think Temp internet files is the prob.) Then it worked again.

Funny is that i have encountered this several times when updating uTorrent.

So, maybe for the FAQ Firon, When getting an error that utorrent is unable to open the .torrent file, try deleting temporary internet files and restart the browser. This worked for me on 3 pc's so far.

lynx

Share this post


Link to post
Share on other sites

I was just going trough advanced settings and I noticed one thing I can't understand. This setting has propably been there for a long time, I just havent noticed it before. "bt.convert_to_fast_pct controls the percentage of pieces that get converted into fast mode, which are only requested from fast peers (unless no fast peers are available for that piece) to increase throughput and prevent block stalls." Any gain by tweaking this value to some direction?

Share this post


Link to post
Share on other sites

i apologize if this has been covered before, but does anyone have a recommendation on lazy.bitfield with PEX? Should i leave lazy.bitfield to true? Do any combinations have an adverse effect?

Thanks

Share this post


Link to post
Share on other sites
dear nTorrent developers, I'm running the largest italian bittorrent community (a village), and we have a problem.

The problem is BitComet. But The solution is not nTorrent because is still missing the udp protocol.

So I'm seriosly thinking about a BitComet tracker wide ban, this because this shity client (also in version 6.3) flood the tracker, distrupt first release superseed launches, announces itself as a new peer entry and many (too many) other nasty things. But for many reasons is an essential need for our community that a client use also udp protocol. nTorrent does not.

I hoped that 1.5 version implemented udp (like azu and BC).

So the question is, UDP protocol will be implemented? There is a beta version where we can help testing the UDP protocol?

Thanks you for writing the definitive BC killer.

If you are the running the site I think your running then it doesn't matter if uTorrent supports UDP trackers as I'm able to announce to the tracker via http. So I'm all for the system wide ban.

Share this post


Link to post
Share on other sites
If you are the running the site I think your running then it doesn't matter if uTorrent supports UDP trackers as I'm able to announce to the tracker via http. So I'm all for the system wide ban.

I think he would like UDP-support because it is (said to be) more efficient. If you have a large bt-tracker, all those tcp/http connections take their toll. Just thinking of the difference between UDP and TCP (no clue how UDP-tracker-support is implemented) I can image that a HTTP (TCP) tracker needs a lot more beef than a UDP one.

Most trackers I know have issues with crashing and downtime. Not sure why, but I can imagine that it a flood of tracker-connections (when something hot gets posted or people switch on BT en mass) over HTTP/TCP will crash the tracker or lock up the box entirly.

Share this post


Link to post
Share on other sites

As if a UDP flood will be any easier on a tracker than a Synflood.

UDP Tracker falls under "Frequently Rejected Requests"

Requiring UDP Tracker support in the clients and banning BitComet is basically restricting yourself to 1 mainstream and 1 obscure client.

Share this post


Link to post
Share on other sites

I would say, yes, but I guess it depends on the network-equipment, OS and tracker-software as well. TCP-connections are slow compared to UDP, so at any given time, you would have more active connections (at least, without knowing the exact implementation, that is what I expect). But UDP comes with it's own issues of course. I personally support HTTPS-connectons :-p

A serious flood/spike of either will probably crash/DoS both UDP and TCP trackers.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.