Experimental disables my Wireless Connection. - Rust

I have others that are reporting the same and want to bring this to attention of Garry. When I exit Rust experimental it takes my wireless out instantly. I can not do a recover as it says that it cannot find the proxy. It does not disable the wireless function and it shows that it is enabled. The only fix for me is to restart the computer. I really hope this can be resolved as I posted it weeks ago on the reg forums and others had this issue as well. Thanks and look forward to the future of Rust. P.S. I have not tried flushing dns or releasing my ip as it's faster to just restart.

Hi, Which Windows version are you on (Vista/7/8, 32/64bit)? I could try and see if I can reproduce the issue you're encountering. I assume this is only happening when connected via WLAN?

I am running Win 8.1 64 bit on a killer 1202 wireless. This is the only game it happens to and only on experimental. It only started happening after the eac was enabled come to think of it.

Thanks for the Windows version. This may sound like a bit silly test, but could you test the following: 1. Start Rust experimental to game. 2. Without closing game, start the calculator program that comes with Windows. 3. Wait 1-2 minutes, then close game. Does the wireless still break?

Already reported in bugs section. [url]http://facepunch.com/showthread.php?t=1413273[/url] Zombie, I have the same card/os. I dont run killer drivers though as they are bloatware/useless. You have to disconnect from the server from the main menu and then exit. Else what you describe happens. To fix run the auto network troubleshooter.

Well I have to say that closing with the calc running worked, very weird indeed. I am not using the killer software as that's what is bloatware with the services. As I stated that running the auto troubleshooter does not work. As long as it's in the bug section then I am happy as they will get it sorted out. Thanks guys for the info and workarounds.

Thanks for your reply, Zombiewarpig! This helped us narrow down where the issue might rely, and confirmed something I though was happening. We will fix this issue within the next EAC update. Meanwhile I'm afraid that you will have to use this workaround. We hope to release this update very soon.

I'm a bit curious, could you share a hint about why the calculator tricks works? I'm aware you cannot share the EAC secrets, just a hint is enough. does the calculator trigger a library load that is needed to make eac work properly? is there a safe mode that is enabled when the calculator is launched?

When a new process is spawned, the operating system goes through a chain of initialization procedures of setting up the environment for the process, refreshing file and memory caches, and so forth. By starting a new process after game, the same pipeline was ran again. I was suspecting that something in there could be the culprit, and this test confirmed it. :) I hope the explanation made any sense. Basically, there's no safe mode or magic related to calculator itself. You can trigger the same work-around with e.g. notepad or any other process. Calculator was a safe choice to suggest, as its a simple program that we will also have, allowing us to reproduce an identical scenario on our system of the same Windows version.

Glad I could help and very happy eac is involved this time around:)