Jump to content

Firon

Established Members
  • Posts

    28,757
  • Joined

  • Last visited

Everything posted by Firon

  1. Could you try running 3.1 to see if your CPU use improves? Active cpu 4-11 Active scrolling cpu 45-55 running background cpu 1-4 cpu: intel core 2 duo T5400 Yes' date=' it does improve a lot, especially when not active and running in the background but the trackers I'm using still not accept 3.1. reversed back to 3.0 and wait for 3.1 become stable and accepted in my trackers :/ p/s: just out of curiosity, does utorrent uses that much resources for scrolling or it just happens to a big list of Japaneses torrents?[/quote'] Could you try 2.2.1 to see if it works better in terms of CPU usage? Just to know for sure. http://download.utorrent.com/3.0/utorrent-2.2.1.exe Would you be willing to try some test builds later to give us more info about what's consuming so much CPU?
  2. The listview in 3.0 is very slow, honestly. It's something we need to deal with. But we've put a fair amount of time already into trying to improve CPU usage. We've got more work ahead of us though.
  3. If you want DHT to not be disabled, then uncheck "Disable DHT when turning off" in the Scheduler optioons.
  4. Do you have multiple monitors? If so, it will show up on the wrong display. If not, then it's probably just broken.
  5. Can you be a bit clearer on what the problem is exactly? Is the sorting order being reset on restart? Or is it that torrents are showing up in the wrong categories?
  6. Same here http://i287.photobucket.com/albums/ll157/yaitanes/tt-478.png how do I upload resume.dat here? box.net? edit: herehttps://anonfiles.com/cdn/1319119081911.zip Could you try running 3.1 to see if your CPU use improves?
  7. It's a poisoned torrent. Find another one.
  8. TEX is practically useless, honestly. The DHT coupled with peer exchange will find you all the same peers. And we'll still fix some of those 3.0 issues. We've already been working on some of them (poor performance with lots of torrents for example).
  9. Windows uses memory for caching. Don't stress about it.
  10. Don't worry about it. It's just your client preventing itself from connecting to itself.
  11. µTorrent Mac 1.5 is now officially stable! The final build is in the first post.
  12. So after like 2 or 3 minutes, the speeds picked up considerably?
  13. Not all beta users are being given this build. But all existing 3.0.1 users should be offered the update to the newest build.
  14. Does it mean we have to uninstall TransCode and let client download and install new version? It's supposed to happen automatically.
  15. There's a new 3.1 build out now with some fixes, mostly oriented towards Plus. We also redid our transcoder completely for improved quality and better device compatibility. We'll eventually have high quality profiles for more devices, but currently we're trying to get it to work on a large swath of devices.
  16. New 3.1 up with a lot of bugfixes! For the plus users, we've also redone the way transcoding works and it should be MUCH more compatible with the various supported devices.
  17. 64-bit gets us very little. There will eventually be a stable version, but it doesn't really make the app faster, and we can't really take proper advantage of the extra RAM (and you're better off letting the OS do the caching anyway).
  18. If your entire machine is hanging, that is not a µTorrent issue. It's as much responsible for crashing your machine as your browser would be. You should make sure you're on the latest drivers and check that the machine isn't overheating.
  19. The default has always been disabled. But you can change it to enabled yourself. It doesn't really help unless your ISP throttles torrents.
×
×
  • Create New...