Fatal Error when loading CSS in SDK

[BlankJones]

Fatal Error:

Model models/props_wasteland/controlroom_filecabinet002a.mdl not found

and models/error.mdl couldn't be loaded

I'm trying to load a decompiled version of a map I was working on but i've never encountered this before. I changed the game configurations, moved around the files, reset and re downloaded but still nothing. Any suggestions?

[Mors]

The SDK is incompatible with SteamPipe games such as CS:S.

[BlankJones]

As of recent? Why wasn't I informed! *stack of letters behind chair*

Well great i'm just going to have to re texture then. Thanks c:

[Mors]

[QUOTE=BlankJones;40548652]As of recent? Why wasn't I informed! *stack of letters behind chair*

Well great i'm just going to have to re texture then. Thanks c:[/QUOTE]

Nono. You can unpack the CS:S content, put it in the HL2 folder, then load HL2 as your mod.
That's what I do.

Problem solved.

[Mozartkugeln]

Have you tried the obvious (restarting the SDK, restarting Steam, refreshing game content, veryfing tool cache, etc.)? This usually works for me when I get this error.

[Mors]

[QUOTE=Mozartkugeln;40549226]Have you tried the obvious (restarting the SDK, restarting Steam, refreshing game content, veryfing tool cache, etc.)? This usually works for me when I get this error.[/QUOTE]

[QUOTE=Mors Quaedam;40548418]The SDK is incompatible with SteamPipe games such as CS:S.[/QUOTE]

[BlankJones]

[QUOTE=Mors Quaedam;40549024]Nono. You can unpack the CS:S content, put it in the HL2 folder, then load HL2 as your mod.
That's what I do.

Problem solved.[/QUOTE]

I did that actually, still yields the same results.

[Mozartkugeln]

[QUOTE=Mors Quaedam;40549274][QUOTE=Mozartkugeln;40549226]Have you tried the obvious (restarting the SDK, restarting Steam, refreshing game content, veryfing tool cache, etc.)? This usually works for me when I get this error.[/QUOTE]

[QUOTE=Mors Quaedam;40548418]The SDK is incompatible with SteamPipe games such as CS:S.[/QUOTE][/QUOTE]

1. I'm able to map for CSS perfectly fine.
2. This error was present [I]long[/I] before the file system migration, so it's only natural to assume that it can be fixed the usual way.