[Rejected] Rat not interacting with the server over time.

Suicideking

New member
May 3, 2017
7
0
0
47
I wanna say first that I really like this manager and it's layout. The problem I have is that it stops interacting with the server over the course of a day. When I log on to the server after RAT has been running it stops responding at some point. The manager says it's connected but there is no response in the game. The server message doesn't show up on log in and there is no response to commands. On the manager it side it stops trying to get information from the server and I have to shutdown and restart the manager for it to start interacting again. I currently rent from Blue Fang, if that might have any bearing on the issue.
 
Hmm, I'm not sure. I've left mine going for weeks and I haven't heard of this problem otherwise. But, that doesn't mean there isn't a problem. ;)

I wonder if there is some sort of connection timeout being enforced at your host, and RAT isn't detecting the disconnect. It should though... But from what you're saying, it sounds like RAT is still connected, but is just "frozen". Does the RAT interface respond to your mouse clicks, etc? Meaning, is RAT frozen, or is it just no communication to/from the server?

What version of RAT are you using?
 
No, it doesn't freeze, it seems to think it's still connected. I can type commands into the console and such, but it doesn't actually communicate with the server. Disconnecting and then reconnecting doesn't work either, I have to shut it down and then restart RAT for it to work. I'm currently using v 1.10.7
 
I fixed some memory leak issues in the experimental version that I think might be the cause of the issue you are having. I can't be certain however. But that version has MANY changes and fixes the version you are running does not. Its up to you, but I'd recommend using the Experimental version (its just the alpha of the alpha really. heh) and see how it works for you.
 
OK, so I installed and am currently running the experimental version. It's an improvement but after about 20 hours it stopped interacting with the server. Except this time, when I manually sent a server message it sprang back to life. I didn't have to restart the program, but it didn't register any activity when I logged on to the server prior to that and I didn't get a server message. Also, this is unrelated to my issue, but it doesn't detect that I have alloc fixes installed.
 
Don't know if you're still watching this thread, but I still have the same issues. Tonight I started up the server manager and restarted the server. Within two hours RAT stopped interacting with the server. Are there timer settings for how often RAT requests information from the server? I'll send a gettime request or some info grabbing command, and while the initial request doesn't register, it seems to kind of fire up the server manager and it connects to the server and gets the server information. The same information that it requests upon initial connection. Then the next command works. So I'm wondering if there are timing settings, in RAT, that determine the intervals between the information requests? Or, is there anyway, or reason, that RAT could go into an idle state?
 
I'm still here, I just haven't had time to dig into RAT recently. However, there is nothing that should cause it to time out like that, in fact, as you mentioned the gettime command happens I think every 60 seconds. It sounds like your host is killing or otherwise stopping the connection, and RAT doesn't notice (it should). But if that were the case, I'd expect RAT to still be attempting to send.

Do you have any thing on your PC, like in power options, that might turn off the network card or whatever after X idle time? Honestly, this is just a weird one and I'm not sure what it is. It seems like some sort of sleep state or something that is never woken from. Also, you might try posting on the RAT thread on the 7D2D official forums. There are some folks there that are pretty good and might have some suggestions. That way your problem gets a little more exposure to people that might be able to also help. I'm trying here, but like I said, this isn't "normal" problem in that nothing appears to be broken, etc.