We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
I'd be interested to know if this is showing up in v1.15.0 (or later).
Hi! Just ran into the std::bad_cast error in W11, on v1.24.8. Was running Cloudflare WARP (basic). Disabling it fixed it.
Oops, sorry about that. Wrong forum. This is for SDIO. I was using SDI Lite.
Edit: Just read that SDI Lite could have malware on it? Brb, purging my PC.
I think (Pressure on "think") I've found a possible cause and fix:
Based on me trying to ping tracker•opentrackr•org in PowerShell, which is seen in "trackers.txt" in the SourceForge code (This forum wasn't all that keen on letting me post a link to that code page), it returns "Request timed out." when pinging with IPv6, but replies correctly to the pings when pinging with IPv4.
So accordingly, that particular tracker should be removed from trackers.txt and optionally be replaced with another tracker; open•demonii•com and exodus•desync•com seem to ping correctly with IPv6 to me.
(Additionally, share•camoe•cn doesn't seem to work at all when pinging, even when pinging with IPv4.)
I've removed the cn tracker from the list. Other than that, I'm not aware that SDIO v1.15 is having any issues.
I seem to still have problems as of 1.15.1, unfortunately:
zip up the logs and postI seem to still have problems as of 1.15.1, unfortunately:
Does it happen every time without fail?
As far as I can tell, yes. Every time the program tries to load an index from some sort of external source.
The sole exception I've noticed, is if the entire 40 GB-ish package sets are first downloaded with e.g. BiglyBT, in which case (If any drivers are detected user-end at that point) the drivers can be installed.
OK. Do you want to run a test build for me and go through the motions so it can log the bug?As far as I can tell, yes. Every time the program tries to load an index from some sort of external source.
The sole exception I've noticed, is if the entire 40 GB-ish package sets are first downloaded with e.g. BiglyBT, in which case (If any drivers are detected user-end at that point) the drivers can be installed.
Yes, I do.
https://www.glenn.delahoy.com/downloads/sdio/DEBUG_1152813.zipYes, I do.
add the following to sdio.cfg:
-verbose:4096
this puts it in debug mode and writes a lot of extraneous stuff to the log that will hopefully point me in the right direction.
I think I've got the -verbose:4096 type logs now (The attachment).
While I notice in the log that the torrent URL is apparently set to HTTP instead of HTTPS, I'll of course leave it up to you to analyse the log file(s) as a whole.
