Did you expect it to work 100% at this early stage? I would suggest to refrain from toying with it as it won't work as you expect it will at this moment.
An update on the post-SteamPipe SDK
- Thread starter Jethro
- Start date
Did you expect it to work 100% at this early stage? I would suggest to refrain from toying with it as it won't work as you expect it will at this moment.
wareya
L420: High Member
- Jun 17, 2012
- 493
- 191
I don't know if this is a bug or a configuration issue..
but the brushes don't show up when you try to paint alpha on displacements.
This will cause hammer to crash...
you have to copy steamuser/sourcesdk/bin/filters/ (the whole directory) to common/Team Fortress 2/bin; so that the directory Team Fortress 2/bin/fliters exists
s0da72
L2: Junior Member
- Jan 11, 2013
- 74
- 32
Thanks, copying the fliters over to common/Team Fortress 2/bin; corrected the problem.
When i have opted in to the sdk beta whenever i get invited to an mvm lobby im getting the message to update the game and cant join. I have to opt out again to be able to play but that also removes hammer. How to prevent that?
woodx
L1: Registered
- Dec 29, 2012
- 44
- 22
sorry guys, but I still can't make my hammer work.
I have loaded beta, than edited game configurations (set path to common/team fortress 2/tf),
changed hammer options to:
(game data files: base.fgd; halflife2.fgd; tf.fgd)
but when i load a map, i see this:
and than it closes.
I have loaded beta, than edited game configurations (set path to common/team fortress 2/tf),
changed hammer options to:
(game data files: base.fgd; halflife2.fgd; tf.fgd)
but when i load a map, i see this:
and than it closes.
Fish 2.0
L6: Sharp Member
- Nov 22, 2012
- 324
- 262
IDK about you but if i played a map that crashed clients, rendered improperly, or failed to have basic functionality like a "New" button, i wouldn't accept "But its only in beta" as an excuse.
duppy
L1: Registered
- Feb 16, 2012
- 35
- 8
If you downloaded the beta sdk, you don't have to edit the Hammer Options...at least I didn't. From your screenshot it looks like you specified too many FGD files, and you just need to have one. Here's folders and files I have set for the "Game Configurations" tab of the options
Code:
Game Data files:
$SteamUserDir\Team Fortress 2\bin\tf.fgd
Game Executable Directory:
$SteamUserDir\Team Fortress 2
Game Directory:
$SteamUserDir\Team Fortress 2\tf
Hammer VMF Directory:
$SteamUserDir\Team Fortress 2\content\tf\mapsrcThe "tf.fgd" file automatically includes all the other FGD files it needs, so that's why you only need to tell it to use one FGD file.
Side note...I got Boojum Snark's FGD working, so instead of using "tf.fgd", I replaced it with "tf-abs.fgd". To get that working though, you need to copy all the necessary materials and models to "tf/custom/whatever/" (and make a VPK file if you want).
I'm not sure if changing your Hammer options will fix that scheme file error, but really, you should not have to modify those folder paths to get it working.
How do you get custom files to work? Mine are in Team Fortress 2/tf/materials. Hammer isn't picking them up, my custom textures don't show up right.
s0da72
L2: Junior Member
- Jan 11, 2013
- 74
- 32
Valve has put out some additional information that might help those who are still having issues with the beta.
http://forums.steampowered.com/forums/showthread.php?t=3119389
https://developer.valvesoftware.com/wiki/SDK_Installation
http://forums.steampowered.com/forums/showthread.php?t=3119389
https://developer.valvesoftware.com/wiki/SDK_Installation
- Jul 31, 2011
- 872
- 1,021
You could also be a pro like me and just not launch TF2 until the SDK functions again.
No launch = no Steampipe conversion = fully functional SDK
I can't compile but that's how I roll motherfucker.
No launch = no Steampipe conversion = fully functional SDK
I can't compile but that's how I roll motherfucker.