#BMS Source Engine SDK?

1 messages · Page 1 of 1 (latest)

snow orbit
#

Its been over 10 years since the game launched. Big source engine modifications and the game although pushed to its source limits have a lot of potential for mods. But a lot of it is locked behind closely guarded source code modifications.

With SDK a lot of door would open, you could change the way game works something you cannot do now.
One of these things a lot of people still on demand is proper VR mod. While Crowbar Collective FAQ say it would need to redo a lot of levels and meshes we can clearly see looking at HL2 VR that its not the case at all.
While yes, guns, UI and motion sickness tools would be implemented it has already ben done by Flat to VR team. And as of today its stands as Overwhelmingly Positive on steam reviews.

Yes this is despite the props are way to big for actual VR perspective but I don't see anyone complaining.

I do not see why Crowbar Collective would not give access to portions of the source code to Flat to VR team to make a mod like HL2 VR. I'm pretty sure there were people that would love to work on it, they have dedicated branch for BMS VR but of course its riddled with bugs because it runs on old BMS build using HL2 EP2 VR mod.

And so I urge Crowbar collecctive to consider this. Coming from modders to modders there's nothing worse when you have something you love, you could improve or change but you can't because your hands are tight and people who have will to do it don't see a sense in it.

Among other things that SDK would enable for modders to do.

merry escarp
#

This is difficult to become real legally. Black Mesa is made using proprietary source code from Valve. You can read this https://partner.steamgames.com/doc/sdk/uploading/distributing_source_engine for some info.
Based on what I know about the copyright law and the documents I have read, I can say that Valve can make exception for Crowbar Collective, by allowing only to them using their part of proprietary source code for server and client (both needed for SDK similar to Source SDK).
But there are 2 major issues:

  1. Crowbar Collective's current priorities are very different from the wishes of Black Mesa's fans. Their main focus is developing the new game, while Black Mesa is supported by around 3 programmers in their free time when they want, all the programmers are focused on fixing some current major game issues and improving some stuff. Some bigger stuff (for example, 64-bit is kinda planned and the new ui rework) is far away for now.
  2. Overall, there is no guarantee that Valve will give this approval (it will take some time for them). This makes the first major issue even more major.

Any hopes ? Everything depends directly on the Crowbar Collective programmers, no email for Valve - no hopes.
To be honest, I have no idea how aware they are of this issue, because it is mentioned around 2-3 times by them.

Somebody can also add that it's a difficult task to make SDK out of client and server source code, and yes, you're right, but it also depends on their wants. Usually, you won't feel any difficulty if the task in front of you is doable if you are willing to put in enough effort.

Alternatives ? Not too much to be honest. We can interact with some stuff on server using SourceMod + MetaMod, you can do a lot of cool things, but the client code is still closed (so no new weapons or ui elements).
VR can be done by using reverse engineering (as it was done for Portal 2 and l4d).
We also have some tools for mapping, etc.

#

Rather, the main problem remains the lack of feedback from developers, only HECU Collective can report issues. SourceCoop and other devs are forced be quiet.
It's sad, because if they could listen some other modding groups, we would have less hacky and buggy coop, and Opposing Force remake would become possible, because all we need is asking on of the programmers adding around 10 blank weapon classes (and ammo types for these).

#

Although even if it were, having an SDK would still be nice.
Adding new entities by editing existing is pain (especially if it's an NPC), and again, no opportunities or alternatives to edit client code (for weapon icons, ui, sound, prediction, etc).

I hope this is a detailed enough answer for both sides (СС and Cyber or other people who will make posts like this).

snow orbit
#

Real shame, but I do not loose hope. Maybe if they see this and enough people show support they'd at least consider alternatives. It would be such a shame to bury the potential of BMS just like so.
I was mainly upset VR never came into production as a lot of people are enthusiatic about it. While yes reverse engineer could be fruitful maybe someone is already working on it?

Could there be made some sort of community SDK. The legal work would be trouble for sure.