Source Modding Community SDK Petition

[joe_rogers_11155]

i was told that if i ever, EVER ... aw fuck it never mind. steam is down and im bored

[DrFeelGood]

Well, as I stated, my IRC room is avaliable...

[windlab]

I'm now getting:

Unable to connect to server. Server may be offline or you may not connected to the internet.-101
Unable to connect to server. Server may be offline or you may not connected to the internet.

EDIT: Back online


I have updated the original post to better reflect the current issues with the SDK, and what could be done to improve the situation.

Please share your opinions and give suggestions!

[DrFeelGood]

Steam is backup for me, but I havent tried the community page yet

[joe_rogers_11155]

say!! maybe you could put some notes up about how Valve can improve steam too

[jgoodroad]

as long as they make it so people with the hamster-powered computers don't get left behind in the dust...
CURSE YOU PEOPLE WHO CAN MAP FOR L4D!

CURSE YOOOOOOOOOOOOOOOOOOOOOU!

[source-maps]

CURSE YOOOOOOOOOOOOOOOOOOOOOU!

I lol'd

anyway, 600 $ and you have a new pc.. work for two months @ a shitty job and it's yours

[windlab]

Could those of you that are members of other Source modding forums please bring this up on them?
Just quote the original post, or say something of your own along similar lines, but make sure to link to:

this thread - http://www.interlopers.net/forum/viewtopic.php?f=22&t=33491
and
the SDK Improvement Group - http://steamcommunity.com/groups/fix_the_sdk

Remember this is a group effort, and it's time more was done than individual forum complaints about SDK issues.

[Varsity]

I think we should be petitioning Valve to release the source code needed to create new in-game tools (Particle Editor, Filmmaker, etc). Working within Source itself would make creating a new level editor a lot easier.

[Noodles]

I think we should be petitioning Valve to release the source code needed to create new in-game tools (Particle Editor, Filmmaker, etc). Working within Source itself would make creating a new level editor a lot easier.

No, I think we're asking too much there. Valve want the monopoly on those, they aren't exactly going to release the Film-maker stuff when they know they can hold it in reserve to use later (when tf2 audience drops low, bring out the Meet the Pyro/Meet the Medic and Bam! tf2 enthusiasm instantly increases).

Or am I just being too cynical...

[Plague]

I think we should be petitioning Valve to release the source code needed to create new in-game tools (Particle Editor, Filmmaker, etc). Working within Source itself would make creating a new level editor a lot easier.

No, I think we're asking too much there. Valve want the monopoly on those, they aren't exactly going to release the Film-maker stuff when they know they can hold it in reserve to use later (when tf2 audience drops low, bring out the Meet the Pyro/Meet the Medic and Bam! tf2 enthusiasm instantly increases).

Or am I just being too cynical...

No one appears to remember Gabe saying that they don't do MtT vids for nothing.
He specifically stated that each video is to make examples of what can be done. I.E. Spy's was for heavy story, Heavy was recycled VA stuff ect ect ect.

We will most likely see it one day released publicly.

Also releasing that code, which would be mostly just giving away the Source engine code, is out of the question.
That would give you the ability to no longer be constrained to Valve's tools and while good for what we want it means Valve has no leeway on us.
When a company has nothing to entice you with... they are out of the business.
BUT the introduction of a plugin scripting language would be realistic and very helpful.

[Varsity]

Releasing the code that would allow us to make new tools does not have to mean releasing the code to the Filmmaker. Why anyone would suggest that Valve are reluctant to release source code I don't know...

[Plague]

Film maker yes, I was talking about giving the

I think we should be petitioning Valve to release the source code needed to create new in-game tools

Which would require elements of the Engine code.

Edit:
Gonna start kicking old group since no one wants to pay attention.
Here ya go if you guys ever get to it. http://steamcommunity.com/groups/fix_the_sdk

[Armageddon]

I still want a fix for my arrow keys in the material editor. I hate using 'z' cam.

[reepblue]

I still want a fix for my arrow keys in the material editor. I hate using 'z' cam.

Personally, I got use to it. I now use Z cam all the time. But ever since the Mac updates, Hammer for me has more and more issues. Not just with Vrad, but how about Hammer just crashing when you click on an entity after 2 hours of it open? Or how about yellow lines all over your screen when you first open the vmf? I turn auto updates off now for my SDK and have a back-up of the files just in case. I used to look forward to any updates to the SDK, but now I fear that Hammer will not open for me but everyone else.

Also, as I'm not such a coder, I had a harder time creating a Source mod then I did say a year ago. I remember doing 2 or so things to make it compile and work. But the last time I did it a week or so ago, I had to do a full operation.

You would expect the Source SDK to be the best tools to use, but its just patches over patches. A patch to fix one issue causes another issue so they patch it with a patch that fixes that issue but screws something else up, etc.