Search found 48 matches
- Thu Jan 25, 2024 8:58 am
- Forum: Announcements
- Topic: [3.0.0.13] XDCC Catcher (PRO)
- Replies: 0
- Views: 887
[3.0.0.13] XDCC Catcher (PRO)
Today we release v3.0.0.12 of XDCC Catcher PRO with the following changes : Fixed: Several "Search on" functions. Fixed: XML parsing in 64bit. Fixed: uPNP issue in combination with multiple NICS. Fixed: Streamlined used font in all dialogs. Fixed: Exception when deleting, adding and removi...
- Wed Jan 10, 2024 8:22 am
- Forum: Technical support / Bugs
- Topic: Reverse DCC (uPNP)
- Replies: 0
- Views: 1043
Reverse DCC (uPNP)
I detected a problem with uPNP (Reverse DCC) when multiple nics are available (for example when you have VirtualBox VirtualBox). This (and other issues) will be fixed in the upcoming 3.0.0.13 release.
- Mon Sep 25, 2023 10:52 am
- Forum: Technical support / Bugs
- Topic: [3.0.0.12 Basic] No networks / servers, and Exception when adding
- Replies: 1
- Views: 1891
Re: [3.0.0.12 Basic] No networks / servers, and Exception when adding
can you please send me the debug.log file you'll find in the program folder?
Probably your server file contains incorrect data.
Probably your server file contains incorrect data.
- Wed May 10, 2023 7:08 am
- Forum: Technical support / Bugs
- Topic: refresh filter timer bug still
- Replies: 8
- Views: 10334
Re: refresh filter timer bug still
Thanks for reporting. Can you just let me know which filtering was enabled?
I'm currently testing the filtering on bots and can't simulate this particular issue.
Was the filter enabled using a 'Search on Bot', 'Channel' or 'Network' as i just fixed an issue there with the autorefresh.
Thanks!
I'm currently testing the filtering on bots and can't simulate this particular issue.
Was the filter enabled using a 'Search on Bot', 'Channel' or 'Network' as i just fixed an issue there with the autorefresh.
Thanks!
- Sun Apr 16, 2023 9:30 am
- Forum: Technical support / Bugs
- Topic: Fix for Reverse XDCC
- Replies: 5
- Views: 7840
Re: Fix for Reverse XDCC
Hi,
The Bot in the 1stt and 3rd example is sending its local ip (192.168.x.x) instead of his/her public ip.
The second bot i'll do a test myself.
The Bot in the 1stt and 3rd example is sending its local ip (192.168.x.x) instead of his/her public ip.
The second bot i'll do a test myself.
- Thu Mar 16, 2023 5:06 pm
- Forum: Technical support / Bugs
- Topic: Fix for Reverse XDCC
- Replies: 5
- Views: 7840
Re: Fix for Reverse XDCC
Thanks. Can you also check the folder in which you installed Catcher? There should be a file called debug.log. Can you find the lines related to those reversed xdcc transfers? I’m interested to see which ip and port the bots were sending over.
Thanks!
Thanks!
- Sun Feb 26, 2023 9:14 am
- Forum: Technical support / Bugs
- Topic: refresh filter timer bug still
- Replies: 8
- Views: 10334
Re: refresh filter timer bug still
Can you see if after a resfresh, the correct filter is applied? So, you changed the filter parameters and you click on the big 'Filter' button correct? Only when you click on that button, the filter will be updated and refreshed. When you wanted filtering, at the top it said "Filter (enabled)&q...
- Fri Feb 10, 2023 5:35 am
- Forum: Technical support / Bugs
- Topic: refresh filter timer bug still
- Replies: 8
- Views: 10334
Re: refresh filter timer bug still
i'm going through the searchfilter code to find what might be causing this.
So if i understood correctly, you entered the search filter and clicked on 'filter' and all of the packs just kept on being displayed?
So if i understood correctly, you entered the search filter and clicked on 'filter' and all of the packs just kept on being displayed?
- Sat Dec 31, 2022 5:25 am
- Forum: Technical support / Bugs
- Topic: Fix for Reverse XDCC
- Replies: 5
- Views: 7840
Re: Fix for Reverse XDCC
Can you please post the error you get related to reverse xdcc?
- Sat Dec 31, 2022 5:24 am
- Forum: Technical support / Bugs
- Topic: refresh filter timer bug still
- Replies: 8
- Views: 10334
Re: refresh filter timer bug still
Did you modify the search filter after you clicked on 'search' ?
The autorefresh will use the filter param as they were when you click on search. When you make any changes after this, you'll have to restart the search. I'm still thinking about a better way to implement this.
The autorefresh will use the filter param as they were when you click on search. When you make any changes after this, you'll have to restart the search. I'm still thinking about a better way to implement this.