It’s Been Fun.
It didn’t work. After completely removing any trace of Source Filmmaker from my machine, after completely reinstalling and starting again, it still doesn’t work.
Whenever I try to load up anything more complicated than the basic TF2 models and maps, SFM just dies and crashes without warning, or error messages. The only change made to my laptop was that I’m now running Windows 10, there’s been no hardware changes (if anything the machine’s running quicker because of the reformatting done before the upgrade). SFM worked last week, now it doesn’t.
I don’t blame you really, but I want to advertise other guys to DO NOT plan to use it on a laptop, SFM was never a friend of laptop and it will never be ! NEVER ! And oh, maybe it’s working for some of you, nice, but keep a alternate solution in case off (A 5 years old desktop do it fine!).
To come back at your case it doesn’t seem to be a Windows 10 issue at all. I use SFM with two W10 computers and nether had an issue. A lot of friend is running it fine also.
The general problem with desktop is drivers, and as manufacturers don’t care about updates you have not much chance to get some drivers updates for W10. But it seem to be not your issue at all or you won’t be able to start SFM or load a map at all.
You problem (working partially, some models work, some don’t…) is often something related to conflicts inside SFM, like textures, settings, rigs, models or something else inside thousand of files… I’ve see bugged models doing this sort of thing and even more.
I think your already try to cleanup all custom models from your usermod folder (or moved them elsewhere for tests). But did you think about workshop ? Maybe you didn’t subscribe to any items recently but it also push updates. I recommend you to create a empty steam account, moving all the sfm workshops folders elsewhere and start SFM with this empty account. Then test with a few custom models and see if the problem is already here.
(You can also remove all your workshop subscriptions and delete related folders if you don’t care about them)
As you said it worked the last week, you can try to do a system restore to a date before the problem appear. But this is a sort of last resort because it doesn’t seem to be a system related issue.
(via nightb0y)
