so last night I decide to make a small custom prop for tf2. Nothing special, but it was the first model I'd tried to compile since the orangbox release. I'd forgotten that it had to be compiled in the orangebox/bin folder, so I was puzzled at the errors being thrown up.
After a bit of googling I realized my mistake, and set about the model compile with renewed enthusiasm. The enthusiasm, however, was short lived. The compile window threw up more errors, but this time it also gave some possible solutions. Great, I thought, it's only a matter of resetting the game configs in the sdk menu. But nope, that didn't seem to do a damn thing, so I tried one of the other possible solutions, which was to run vconfig to let the tools know what game I was compiling the model for. Vconfig laughed in my face when I tried running it, telling me that steam.dll couldn't be found. So I said 'feck this', hammer is my friend, I'll go back to playing with him.
Imagine my surprise when hammer crashed with one of those 'referenced memory can't be read' errors. This didn't help with the slowly growing bald patches on each side of my head, but a steam restart would fix everything. Wouldn't it? Hah!, no such luck. Everything that had been saved in hammer before I reset the game configs would open, but only for a few seconds. Then my firewall would ask if hammer could access the net. Whether I allowed it or not, hammer would then crash with the same error. If I started a new .vmf, then there was no problems. I could save, exit hammer, restart and reload the new .vmf
The only clue that I had was in my windows start menu. I found that it it didn't point to the correct folder, prog files/valve/steam, but to an older install, in prog files/steam. So, thinking there may be some sort of confusion between some old and new registry entries, I decided to uninstall the one in the start menu. Selecting the uninstall option brought up the dialogue box that has the nice little picture of a torch (flashlight to some) swaying away gently, with the almost hypnotic reasurance that it would find unwise.exe (or msi or something, but you get the picture). Anyway, I got pissed off waiting, and just riight clicked the steam entry on my start menu and deleted it. I know it's not the best thing to do, but by this time I didn't think it would make anything any worse. I decided a nights sleep would help me to make some sense of it all.
So, a new day dawns, with very few ideas on how to go about resolving my woes. One thing that I thought of trying was updating my vid drivers. I've been using ati's ver7.8 for a while now, because anything newer would crash tf2 games with a 'could not create d3d device' error. The last ones I'd tried were ver7.11, so I had a look to see if there were some more recent ones available. I found there were, but a couple of hours later, after all the hassle of uninstalling 7.8 and installing 7.12 (ati drivers are a pain) I found that the d3d device error was still there, so I had to go through the proccess again, reverting back to 7.8
At this point, there was little else for me to do other than uninstalling steam. I moved all of the custom content out of the steam dir, as well as all of the gcf's, and proceded to uninstall everything else.
Now, and this is the bit that really puzzles me, is that once steam was re-installed, and I'd run tf2 once to create a gameinfo.txt, when I tried to load any previously saved file in hammer, the exact same error was still there. wtf??? I can make new .vmf's, but I can't open any old ones or hammer dies??? I had to walk away from it, or the next hammer that was getting installed in my pc would have been straight out of a joiners bag. bah!
After a nice cup of tea, I decided to install and uninstall steam from both of the previously used dirs, hoping that if there was any conflict, that that would clear it up. I was less thorough with backing up my files this time, and forgot to save the tf2 gcf's. No great loss, but I'm still waiting on the game to download again before I can test it all out. ~90% atm, so it shouldn't be long.
I really wish my pc could feel pain, then I'd know exactly what to do.
i eat paint