Rust Bug - Client Already In A Context Menu. Wait. - Rust

Ever since the early Feb patch I can't play Rust on my laptop...the odd thing is that it's just my laptop. It works on my desktop, the GF's laptop, the work laptop, the work desktop. But my laptop (ASUS G55 w/Windows 7) will not run it. It keeps throwing this error and it makes it so I cannot play the game. It's really odd because I can't interact with anything once the bug occurs but I'm still "online" because the chat windows update just fine. At the end of the video when I suicide, you can see my backpack show up on the bed where I spawned in at. So for whatever reason it's not updating my position when I move. I'll post this in the bug section too, but I'm hoping it'll get more attention here from the community in case there is a fix. [video=youtube;yK8RvPQJBt4]http://www.youtube.com/watch?v=yK8RvPQJBt4&feature=youtu.be[/video]

Bump because I really wanna play =/

Yeah happening to me as well. I have no idea how to fix it. Once it does the "Client already in a context menu. Wait" It kicks me out the game and takes like 5mins to go back into the server. This is happening to everyone on my server. Also Rust is using high CPU when running, my server owner and i are thinking the last patch caused a memory leak. Something is clearly wrong. I hope they fix it soon! [IMG] [url]http://steamcommunity.com/sharedfiles/filedetails/?id=241464088[/url] [/IMG]

How long does it take to happen? For me its instant and no matter what I do I can't play at all.

Giving it it's daily bump.

Daily bump, seeing who else is having this issue.

Another daily bump, sorry. Just trying to keep it on the first couple pages.

Bumpy bump bump

keep happening for me aswell, but i just keep reconnecting

restart helped me yesterday :) but im sure u tried that :D

We restarted the server and i also restarted my comp and it still does it. Also i noticed its everyone on my server thats having the same issue. Also its completely random and you have no clue when it will happen. Sometimes its seconds after log in sometimes its a hour or more. Its completely random. Also now rust crashes every time it does that error. The server its self isn't crashing, just the game. My server owner and I have been tinkering with the plugin's to see if its those causing the game to lag. We went vanilla for a few and it stopped. Once we turned on the plugin's it was back. Also we had changed decay, so we also think that's the issues we have over 20,000 items placed in our world it was normal decay and we changed it to 7days with out log in before the house decays, and than it lagged rly bad and so now we changed it to its default setting. It doesnt seem to of helped. So im really begining to think its either rust or the plugin's. Im not completely sure which.

It's been a while and Rust has been fine for me for 3 weeks...but it started again today and now I can't use my laptop to play Rust anymore...it happens every time. I haven't changed anything, installed anything, uninstalled anything. It worked this morning, went out for the day, booted the PC to play some and boom...it's busted.

Still doing it, it's been a week now...can't play Rust on my laptop and only on my laptop. Just did it again out of the blue.

Bumping this again in hopes someone knows something...I miss Rust =/

What happens if you switch to the experimental branch, or the dev branch? It's in Rust's properties, in the Betas tab.

almosttactful and iPrize who is hosting the server? Never had that issue from anyone on our server.

I get this issue on every server, from what I can tell so far I don't get it on the experimental branch

Weird. Well, I'm not trying to say that nobody cares about helping you, but the old branch isn't being updated anymore, so unless someone figures out a fix to the problem that doesn't require Rust itself being changed (e.g. there's a driver problem, or a file got corrupted somewhere, or something) the old version isn't going to see this bug fixed. At least it doesn't happen to you on experimental.

Yeah, I'm not worried about it at this point. Odd thing is, it started working again yesterday so hopefully it'll last this time until patch haha :)