NS minimizes upon server connect

Cattlecruiser00Cattlecruiser00 Join Date: 2002-11-03 Member: 6486Members, Constellation, Reinforced - Supporter, Reinforced - Shadow
in Tech Support
My NS has worked jsut fine until recently. Now, whenever i try to connect to a server, the moment it reaches the load screen, my NS automaticaly minimizes and i'm sent back to the desktop.

For those of you who've experienced this problem b4, when you minimize NS at this crucial moment, the game will start flickering once you're in the server and you can't see anything. Bringing down the console will stop the flickering, but it is impossible to play the game with the console always down. Please Help!
Off Topic Disagree Agree Awesome

Comments

  • WyzcrakWyzcrak Pot Pie Aficionado Join Date: 2002-12-04 Member: 10447Forum Moderators, Constellation, NS2 Playtester, Squad Five Blue
    Strange.

    Does it happen if you create a local server?

    Do you have any apps you can kill and try again to reproduce the problem?
    Off Topic Disagree Agree Awesome
  • SariselSarisel .::' ( O ) ';:-. .-.:;' ( O ) '::. Join Date: 2003-07-30 Member: 18557Members, Constellation
    This happened to me before too. It had something to do with programs I had running in the background. Did you install any new programs recently? If this is a recent development, the best bet is always to see what has changed and possibly revert to an early PC state.
    Off Topic Disagree Agree Awesome
  • AndosAndos Join Date: 2003-10-17 Member: 21742Members
    I would suspect firewall software or something like that. Try look through your list of running processes and look them up on Google to see what they are doing and disable some you don't need. Will also speed up your system in some cases (not always).
    Off Topic Disagree Agree Awesome
  • Cattlecruiser00Cattlecruiser00 Join Date: 2002-11-03 Member: 6486Members, Constellation, Reinforced - Supporter, Reinforced - Shadow
    edited June 2007
    Thanks guys, thats exactly what needed to be done. The tricky part was finding the new commands that caused it.

    Using " Run: msconfig " seemed to do the trick.
    Off Topic Disagree Agree Awesome
Sign In or Register to comment.