I need help ASAP! Whenever I try to start up steam or convert a custom texture It says that "cannot find filesystem_steam.dll" I'll load up a pic in a second.
matter in fact.. I just looked in my bin folder and ALL MY FILES ARE GONE! lol this sux ass.. excuse my language =p i just tried reloading up the sdk kit thing and nothing happend. plz help
ok never mind I somehow managed to fix it.. I'm still missing all my files in the bin directery but I can run stuff now. but say I didnt fix it I am very disapointed in the lack of help here.. for as much knowledge that goes on around here their is not very much help given.
You posted at 3am mate. People go to sleep at like 12 and wake up at about 10-11 nowadays. Don't blame the system. I know the answer but and if you'd waited just 3 hours more you would've got it.
This happened me yesterday too. I am making a map for HL2 so I took the dll from the HL2 bin folder and pasted it into the SDK bin folder and it worked.
You have to run it THROUGH steam... not using a shortcut.
Go to steam, run the SDK and then click hammer. It then should work. If not, find the file using windows search, then copy and paste it to where it should be.
ah people posted lol.. I feel sorry for you fearian. I wish I knew how I fixed it and I could tell you. anyway at my time when I posted It was about 11/12 oclock.. what time does the forum run on?
I get that error occasionally, too and I think I have finally figured out the pattern.
If there's been a Steam or SDK update, you cannot launch any of the editing tools, like Hammer, HLMV etc from a desktop shortcut. You MUST launch them from the Steam menu, which seems to copy the dll's back into their proper place. Sometimes you have to close and restart Steam to get it fixed.
So, if you get this error, try this:
1. Close and restart Steam
2. Launch the tool of your choice from the Steam menu
3. Once done with the tool, you can then use any other shortcuts you have made to launch it again, until Valve releases another update.
Probably not 100% accurate, but it's worked for me for the past 3 months and I haven't ever had to resort to reinstalling the SDK.