Lemma Soft Forums

I started with Ren'Py as she was already into yaoi o_o so I don't know about how much of a prude she originally was...

Off the top of my head, one possible reason for this is that you're saturating your line with the upload, and breaking the TCP stack in your router or modem somehow.

An internet connection is basically comprised of two channels - the upstream and the downstream. One sends information to the internet, the other takes information from the internet. The curious thing is that they are commonly different speeds - for regular web browsing you only ever need to send enough information out to request the right page - the URL, your address, any request parameters - and the web server then knows enough to send that data - a much larger amount - down to your computer. So it's quite common for the upstream to be a tiny fraction of the speed of the downstream, because most people don't need to send stuff up.

However, when you're uploading something, say to the RAA, you're using up all of the available upstream for your upload, so there's little space for other traffic. The thing about TCP connections (e.g. those connections to websites, or to download files) is that they are kind of self-aware, they track whether the connection's open or not from end to end by monitoring the packets that go by. Your router will have to convert your single internet IP address into potentially multiple local-network addresses (because you can have more than one PC on the same internet connection) so it has to intercept and translate the TCP connection by a process known as 'NAT'. However, when you're saturating your upstream with a big file upload, sometimes the keepalive packets for other TCP connections (e.g. your requests to other websites) will get lost and those connections will break.

In a robust system, this isn't a problem - it just means that you can't browse the web while you're uploading a big file because you won't get any results (or the response will be very slow). I'm guessing that your router perhaps isn't that robust, though, if the trouble persists after the download finishes - it seems possible that it still thinks it's got these half-open TCP connections and it's refusing to start any more until they've been cleared (this is not an uncommon approach), but for whatever reason it's not marking them as dead and clearing them out. Windows won't be able to report any problem, because as far as it's concerned the connection is between itself and the router, and that connection's working fine - it's the connection between the router and the internet which has the problem.

- Developer Version (Unarchived for those who wanted to take a peek at how I do things)
- Code will have umm... helpful comments (Developer Version)

Expect:
- Totally remade GUI (Thanks Mr E for the Japanese Text)
- Compact and optimized
- More animated thingy
- More (subject to change without prior notice)
- Developer Version (Unarchived for those who wanted to take a peek at how I do things)
- Code will have umm... helpful comments (Developer Version)
- Sylvie, Banong and Every character to be voiced by none other than yours truly (subject to change without prior notice)

"POOF" (Disappears)