Episode II era Source SDK

[Furyo]

For those wondering when the next SDK update will be, here is as good an official answer as we can get at this point:

On 10/15/07, Mike Durand wrote: It's a little bit complicated, but hopefully I can explain it well. CS:S (along with DoD:S and HL2MP) are going to be migrated to the new engine over the next couple of months. Until then you should *not* merge in the new SDK code as it will not work with the old engine. Once we convert the three MP games you *will* want to create a new version of the mod using the updated SDK source code. Makes sense? Sorry I can't be more specific about exactly when the games will be converted to the new engine. Mike

You will have the option of still using SDK Base which will still be linkedto the Ep1 engine or you can base your mod on the new app IDs for Ep2, Portal, or TF. We will probably make a new SDK Base that uses the Orange Box engine too.

So at this point, we're talking of "months", which is as good as saying "soon"

[Zeta]

so much for same day.

[Nexus]

Yeah.. what is the new engine?

[Mr. Happy]

Until then you should *not* merge in the new SDK code as it will not work with the old engine.

This is a little ambiguous to me. Sounds like you'll be able to create a mod using the new codebase prior before you can update your mod's old codebase. So we heard supposedly Oct 30th for an SDK update (which of course was never going to happen) so...we'll be able to map for TF2, Portal, EP2 and make SP mod's using the Ep2 steamappid on the 30th (ya right) and later on down the line Base will be updated

but there will be two versions of base...

and they are releasing the new client/server source before updating base...

god dammnit I just can't wait to explain this to dozens of confused newbs

[Zeta]

Hi List-

I'm shooting for an update that includes the updated tools this week or early next. After that I will work on an update that includes the new game DLL code and I am hoping that it will be available in beta by the end of the month.

I'll let you guys know if I run into any problems that invalidate these timeframes.

What they should of had.

The original qoute is based on him telling people that Valve are probably gonna phase out the old SDK Base(this is only relevant to coders) so you should try and merge your code with the new code base that will be out soon as quickly as possible.

[Bluestrike]

hmm I tought they were going to keep sdk base updated.

Well nice to see they are adding the support for multicore also to css and dods.

Oh I also read somewhere a while ago they were not gonna make the multicore support availeble to mods.

[Pongles]

Oh I also read somewhere a while ago they were not gonna make the multicore support availeble to mods.

Well, if *all* the multicore stuff is in the engine support - I guess they could roll-out a different engine on Source SDK Base - but then what would the mods do that use the app ID's from CS:S and DoD? hrmm.

If there is an exposed API for multi-core tech in the SDK, e.g. some kind of manager thing, then they would have to start branching code here there and everywhere - and the whole SDK code rollout becomes even more cumbersome than it already is >_<.

This whole thing starts to make think scripting in engines is a good idea >_< (easier for legacy support etc etc).