Source SDK Possibly Corrupt

Discussion in 'Mapping Questions & Discussion' started by mitterdoo, Jan 6, 2013.

  1. mitterdoo

    mitterdoo L1: Registered

    Messages:
    9
    Positive Ratings:
    0
    Hello. I have made one map before and maybe you've probably seen it. But let's not get into that. I'm working on this push map and I just started working on it again. But the first thing I noticed when I opened Source SDK was the game list. Team Fortress 2 was missing.

    I searched for a fix and I made a temporary configuration of TF2. I tried to edit the map but the grid was unresizable, too big, and I couldn't see selection boxes. I changed the engine to Source Engine MP and then it was fixed. Then I got back to work on my map. I got some mapping tips from my friend. Then when I tried to compile, the Compile Process Window would freeze when it starts running vvis.exe.

    I tried compiling a different map. Even a simple hollow box with a skybox outside would not work. I learned that most people experiencing this issue with one map would check their process menu on the Task Manager and find "vvis.exe" taking up about 90% of the CPU. On my computer, it runs at absolute zero percent.

    Not even my experienced mapping friend couldn't figure out why this was happening. But I think the problem may be the engine I'm using. Switching it to 2009 would cause the grid issue. It might be the configuration I'm using. But I can't figure out if it is or not. Here are the settings for the temporary TF2 config:

    Game Configurations
    Game Data Files:
    $SteamUserDir/sourcesdk/bin/orangebox/bin/tf.fgd
    Cordon Texture: tools/toolsskybox
    Game Executable Directory: $SteamUserDir\team fortress 2
    Game Directory: $SteamUserDir\team fortress 2\tf
    Hammer VMF Directory: $SteamUserDir\sourcesdk_content\tf\mapsrc

    Build Programs
    Game Executable: $SteamUserDir\team fortress 2\hl2.exe
    BSP Executable: $SteamUserDir\sourcesdk\bin\orangebox\bin\vbsp.exe
    VIS Executable: $SteamUserDir\sourcesdk\bin\orangebox\bin\vvis.exe
    RAD Executable: $SteamUserDir\sourcesdk\bin\orangebox\bin\vrad.exe
    Compiled Map Directory: $SteamUserDir\team fortress 2\tf\maps


    Thank you for reading this entire post and I hope you can help.
     
  2. Shanghai

    Shanghai L6: Sharp Member

    Messages:
    394
    Positive Ratings:
    217
    Have you gone through the motions yet? Before you go deeper into the realm of troubleshooting, I suggest that you first try resetting your game configurations (via the Source SDK menu), validating your Source SDK content (Steam Library > Tools > Right-click Source SDK > Properties > Local Files > Verify Integrity of Tool Cache) and TF2 content (Steam Library > Right-click Team Fortress 2 > Properties > Local Files > Verify Integrity of Tool Cache). If neither of these work, back up your mapsrc folder (steamapps/YOURNAME/sourcesdk_content/tf/mapsrc) and uninstall / reinstall Source SDK (Tools > Right-click Source SDK > Delete Local Content...).
     
  3. Seba

    aa Seba DR. BIG FUCKER, PHD

    Messages:
    2,363
    Positive Ratings:
    2,365
    I'm confused; you made a TF2 config under Source 2009? You're supposed to use the Source Engine MP version, that's what TF2 runs on. Using any other engine version will screw up your TF2 maps.
     
  4. mitterdoo

    mitterdoo L1: Registered

    Messages:
    9
    Positive Ratings:
    0
    I have validated the Source SDK. Team Fortress 2 keeps validating every time I start it for the first time on my Steam session. I actually reinstalled Source SDK to see if the TF2 configuration would pop back up in the list, but I guess I'll try again.

    No I made a TF2 configuration. It doesn't ask about the engine. And before I got back to work on this map, editing the map worked perfectly fine on Source Engine 2009.

    EDIT:
    I can't seem to uninstall Source SDK. I tried uninstalling from Steam. Then I tried deleting the folders and files. A process was still "using it." I checked my process list and I found a ton of vvis.exe programs running from my impatience (don't talk about it please.) I couldn't end them, no errors or anything. I can't restart my computer because it takes 5 minutes to actually get to the login screen, then about 10 to actually warm up and settle down. I just defragmented the game cache though. I can't test it until I spend literally 20 minutes verifying the game cache of TF2. I'll edit as soon as I test it.

    Also this might be useful information. My friend compiled the map perfectly fine with lighting and everything. I also have my launch options set as:
    Run BSP: Normal
    Run VIS: Fast
    Run RAD: Fast

    EDIT 2:
    Nope. I can't compile a map still.
     
    Last edited: Jan 6, 2013
  5. mitterdoo

    mitterdoo L1: Registered

    Messages:
    9
    Positive Ratings:
    0
  6. Egan

    aa Egan

    Messages:
    1,307
    Positive Ratings:
    1,488
    Well, what do you want us to say? There is a problem obviously with your vvis file, you can't delete it at the moment. So close everything SourceSDK related, see if you can end processes for vvis, if you can then go and uninstall SourceSDK and reinstall it - if you cannot end the process you can wait 15 minutes to restart your computer again.

    After SourceSDK reinstalls, only use Source Engine MP for mapping TF2. If somehow you still get the issue, maybe try compiling through VBCT instead. (google that if you don't know what it is.)
     
    • Thanks Thanks x 1
  7. mitterdoo

    mitterdoo L1: Registered

    Messages:
    9
    Positive Ratings:
    0
    Well, actually, I managed to do that after the bump and before your post. But this is the method that I used, only I deleted vvis and vrad (also causing the problem if vvis is disabled) then validated cache. This is close though. This problem has been resolved.
     
  8. Seba

    aa Seba DR. BIG FUCKER, PHD

    Messages:
    2,363
    Positive Ratings:
    2,365
    For future reference, Mitter didn't have TF2 under the Source Engine MP category in SDK; this was fixed by resetting game configurations (one of the buttons in SDK).