Rexxenexx 0 Posted May 11, 2010 (edited) So when I run the dserver with build70256 and start a mission with my client comp it says "Wait for host" (this is at the slot selection then press "OK" to start the mission). I'm looking at the dserver taskmanager and it shows the exe pinning one processor -of two- to 100%. It hangs when the Console reads "Reading mission...". Closing the Console window doesn't close the process either, you need to end task. This is new since the previous build. Anyone else get this? ---------- Post added at 06:36 PM ---------- Previous post was at 06:25 PM ---------- Shazbot! -exThreads=1 works! I've never used that command in my life, I just saw it in the poll below and thought it might mean "extra threads"? Time to read up! ;) but the games are loading now. Before when starting the exe would work one processor now it does both like the previous build. Edited May 11, 2010 by Rexxenexx Share this post Link to post Share on other sites
gunterlund21 10 Posted May 11, 2010 As a matter of fact I am getting the same thing. I had to terminate the process and the mission never started. Share this post Link to post Share on other sites
Rexxenexx 0 Posted May 11, 2010 -exThreads=3 is working good for me. Performance between 1-3 is not much but 3 seems to start out with more FPS using #monitor. Share this post Link to post Share on other sites
killswitch 19 Posted May 11, 2010 I've seen the same thing - if you run the 70256 dedicated server "normally", the symptoms when trying to load a MP mission are what the first post describes. Adding -exThreads=1 solved it, and apparently 3 works aswell. Share this post Link to post Share on other sites
VictorFarbau 0 Posted May 17, 2010 Same here on our dedicated server and it would only load correctly when using "-exThreads=1". All other values would make the machine hang. VictorFarbau Share this post Link to post Share on other sites
CarlGustaffa 4 Posted May 17, 2010 We run with "-exThreads=3" without issues. But either when I or the server (forgotten which of us) didn't have the option set, it would freeze the server, and clicking on the close button on its window would close it but the threads remained. Share this post Link to post Share on other sites
spoogevac 10 Posted July 6, 2010 Stupid question but to what file do i add the line "-exThreads=1" part? Share this post Link to post Share on other sites
CarlGustaffa 4 Posted July 6, 2010 The shortcut which you use to start the server, in the target line. Might be other ways. Share this post Link to post Share on other sites
spoogevac 10 Posted July 6, 2010 Im using 7 64bit, dunno if that makes any diff Sever hangs saying waiting for host as soon as i click the go button. Was perfect before i ran 1.07 patch :( Share this post Link to post Share on other sites
spoogevac 10 Posted July 7, 2010 Did that and it fixed it, runs fine now thanks all. Share this post Link to post Share on other sites
sbsmac 0 Posted July 12, 2010 Good news- seems to be fixed with server 72018. Share this post Link to post Share on other sites