U4RedaolNowdEht

Thanks again Wxhere , I will be looking forward to 1.34x64. I will report back about the scheduler shortly.

Okay , I tried on W8 with all anti(s) disabled fresh install of BC 1.33 x64. With stock options , nothing altered but the Proxy option and required info typed in. Same issue and I literally don't want to DL behind my IP directly so I would have to downgrade to what works for me(1.28x64). Until a working version is released hopefully soon.

Oh sorry , I didn't mean it automatically closed after I hit apply. I just didn't state that I hit OK after apply, Sorry for the misunderstanding, Since you don't have this issue I'm starting to think it might have something to do with my security apps blocking BitComet from storing key strokes i.e anti-logger. Although 1.28 - 1.32 x64 worked fine. I will test on a newly installed W8 partition since not much will be affected... and report back.

Response by number- 1. After I entered the requested info in Proxy option I click apply, the window closes. Then I attemp to refresh and WAN IP doesn't change. 2. Yes. 3. Yes , it still shows Socks 5 as Proxy type selected. For the IP box is empty and Port section shows a 0. I'm not sure why this issue occurs. From your results the issue seems specific to my use, I didn't encounter this with ver. 1.32 x64 and under. 4. It is empty after these conditions ~> A). I hit apply after info is entered and window closes. I then reopen the Proxy setting box. B ). After ^A^ but without reopening the Proxy settings. Instead I restart BC , then I'd check WAN IP which states the ISP IP. In other words the previous settings as far as Proxy IP & Port didn't stick and/or attempt to connect to Proxy settings thus real IP displayed by default. Even though Socks 5 is selected(based on what was entered for Proxy use and what's left see ^3^. C).I start the torrent after ^A^ & ^B^ but I input the IP & Port again and select Socks 5 , apply/ ok. Try to refresh WAN IP, it shows real IP. 5. My O/s is W7 x64, language in BitComet x64 english and C:\Program Files\BitComet is the installation location. 6. Understood. Thanks.

Okay , I have BC 1.33 x64 installed and with the same settings as the previous working version i.e 1.28 x64, I enter the IP, Port and select Sock 5 apply, then right click the IP address which displays the WAN bottom right. I hit refresh so the Proxy IP will be reflected as WAN. The entered info is gone when I go back in options / proxy , I try to enter the IP:Port info I always use again. Everytime I refresh to reflect the Proxy IP it just revert back to my ISP IP. Hope this is the description you were looking for. Thanks..... as this is the main issue with the latest. The bandwidth limit not being respected continued through versions after 1.28 x64. I also use CheckMyTorrentIP to make sure the correct IP is being used and reflected..

Thank you. As for problem 1 I'll play with BC 1.33 a little more.I did take into account that I didn't really see any reports about it. So I guess I have to go through the settings more carefully to see if I didn't set something properly. As for problem 2 I'll test that too as I wait for your update. Thanks again, I love this software it's better than all the others in my opinion.

I signed up just to post about two issues that need to be fixed in this version and all the BitComet.releases after ver. 1.28 x64. Problem .1 When you set the bandwidth limits in schedule option and it's activated, the limits aren't respected. Meaning BC runs the torrent(s) without limit, even when the master limit is set. I've tried every new release and the problem persist so I had to downgrade back to 1.28 the version that worked perfectly. Problem .2 This issue/bug is with the latest version, it doesn't allow you to use a proxy which is a big issue given the current situation in the US. I would enter thr IP:port and Socks 5, hit apply and then refesh the IP. I go back to try a different IP:Port when the previous information is missing. So BC reverts to using your real IP at any given, even when BC is restarted and/or set to start with Windows. Previous versions didn't have this issue.... as far as retaining the VPN/Proxy info so BC can be refreshed with the input values.