DrHack Posted August 14, 2011 Share Posted August 14, 2011 I've recently bought a copy of GRAW2 in a "bargain-bin" but could find no fix for this major show-stopping problem, despite hours of searching. After a lot of diagnostics and testing I have created this fix. If the old lags around here already know about this then "..please move on, this is not the thread you are looking for..". Navigate to your "Ghost Recon Advanced WarFighter 2" folder. Edit the "context-standalone.xml" file and add the following line: <threaded_renderer value="false" /> What baffles me is how Ubisoft distributed a game that simply failed as a dedicated server. Weird.. Enjoy! Quote Link to comment Share on other sites More sharing options...
Rocky Posted August 14, 2011 Share Posted August 14, 2011 Have you managed to prove this? Quote Link to comment Share on other sites More sharing options...
DrHack Posted August 18, 2011 Author Share Posted August 18, 2011 Have you managed to prove this? Yes, I wouldn't have posted otherwise, but try it for yourself. My server was losing around 200Kb/second, so nearly 700Mb/hour/per player. If you run up (from memory, I normally use a linux desktop) the windows Task Manager (Ctrl-Alt-Del) and tab to 'Performance' or 'Processes' you can monitor the server memory usage. Mine stays stable at around 400Mbytes usage now, whereas before the graw2-dedicated.exe would crash with 'out-of-memory' errors after a certain time, depending on, obviously, player count and server memory. Quote Link to comment Share on other sites More sharing options...
Rocky Posted August 18, 2011 Share Posted August 18, 2011 Have you managed to prove this? Yes, I wouldn't have posted otherwise, but try it for yourself. My server was losing around 200Kb/second, so nearly 700Mb/hour/per player. If you run up (from memory, I normally use a linux desktop) the windows Task Manager (Ctrl-Alt-Del) and tab to 'Performance' or 'Processes' you can monitor the server memory usage. Mine stays stable at around 400Mbytes usage now, whereas before the graw2-dedicated.exe would crash with 'out-of-memory' errors after a certain time, depending on, obviously, player count and server memory. Cool, I'll add this info to the FAQ. Thanks. Quote Link to comment Share on other sites More sharing options...
struth__ Posted August 13, 2012 Share Posted August 13, 2012 I’m trying it now, I hope your right, this could have made big difference for hosting co. orsom Quote Link to comment Share on other sites More sharing options...
JohnTC02 Posted August 19, 2012 Share Posted August 19, 2012 I can confirm that this fix does work. I've been using it on my dedicated server for a while now and had no memory leak related crashes since adding the line to my context-standalone.xml. I should mention that I'm using a dual core laptop as a dedi so I don't know if this would work the same on a true paid for server, but I see no reason why it shouldn't. Quote Link to comment Share on other sites More sharing options...
struth__ Posted August 20, 2012 Share Posted August 20, 2012 Not only can I confirm this fix works... But it works with multiple instances and versions on the same server, in that: <threaded_renderer value="false" /> will not interfere with multiple instances of the SADS setting up on a new thread if it’s available. I run 4 GRAW2 servers in the same 4 core virtual machine. all 4 SADS are more stable then ever before Awesome work DrHack I wish you were around with this fix 4 years ago Quote Link to comment Share on other sites More sharing options...
Rocky Posted August 25, 2012 Share Posted August 25, 2012 Well it took me a while, but htis info is now in the FAQ. Thanks Dr, wherever you are, Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.