• Rust not responding at main menu
    3 replies, posted
Hi Guys, I have never been able to play rust experimental (now the main rust) since it came out. The problem is that after I reach the main menu, the wolf will move as if everything is running fine (I can change language ect.) but only for about 10 seconds, then everything freezes and I need to shut rust down from the task manager. I won't even be able to get to the main menu again after this until I restart my PC (just get to a black screen which closes automatically) I have reinstalled both rust and EasyAntiCheat but this hasn't fixed the problem. Please help me especially that rust "experimental" is now the main rust . Thanks :D Specs: Intel i7-3770 GeForce GTX 660 8GB RAM 2TB HDD OS: Windows 7 Home Premium 64-bit [B]EDIT:[/B] Ok so this just got weirder :suicide: I left it at not responding for about 30 mins, when I came back the UI vanished but the wolf was now animated again!
+1 I have same issues [editline]1st October 2014[/editline] [B][I]HELP PLEASE..[/I][/B]
Is there no fix for this? Must we just wait it out? Any response would be appreciated thanks.
Here is the end of my output.txt file: ========== OUTPUTING STACK TRACE ================== 000007FEFD5B940D (KERNELBASE) RaiseException 000007FEE4A11158 (mono) set_vprintf_func 000007FEE4A1117C (mono) set_vprintf_func 000007FEE4B5E824 (mono) mono_set_defaults 000007FEE4B2AB51 (mono) mono_debugger_run_finally 000007FEE4B2F2BD (mono) mono_jit_thread_attach 000007FEE4B49912 (mono) mono_set_defaults 000007FEE4B317DC (mono) mono_set_defaults 000007FEE4B32538 (mono) mono_set_defaults 000007FEE4B32EBA (mono) mono_set_defaults 000007FEE4B334E5 (mono) mono_set_defaults 000007FEE4B33578 (mono) mono_set_defaults 000007FEE4B2B787 (mono) mono_debugger_run_finally ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 000000000FE81A50) ERROR: SymGetModuleInfo64, GetLastError: 'A dynamic link library (DLL) initialization routine failed.' (Address: 000000000FE81A50) 000000000FE81A50 ((<unknown>)) I'm guessing that is where the problem lies but I don't know how to fix it.
Sorry, you need to Log In to post a reply to this thread.