Source engine source code

03.09.202203.09.2022 admin 0 Comments

Source engine source code

ValveSoftware/source-sdk-2013

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README

About

The 2013 edition of the Source SDK

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 14

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Source Modding — Часть 1 — Основы основ

В мире существует множество игровых движков, но нет ни одного движка, похожего на Source своей историей и особенностями.

В этом (пилотном) уроке мы разберем простейшие действия с исходными кодами SDK, а также внесем наше первое изменение в код Half-Life 2.

Вступление

Немножко терминов

Сам по себе Source SDK — набор утилит и программ, помогающих в разработке собственных уровней и модификаций для игры, а также исходные коды Half-Life 2 и эпизодов.

Игра/Мод (Для сурса нет никакой разницы, игра это или мод :p) — скомпилированные исходные коды SDK.

Так почему же именно Source?!

Что нам необходимо?

Введение в сурс дела

Репозиторий

Исходный код SDK находится в репозитории на GitHub. Склонируйте его в любое удобное для вас место:

Выбор ветки

Если вы хотите написать свой первый мод для Half-Life 2/Episode 1/2, то используйте директорию sp/ и Source SDK Base 2013 Singleplayer.

Стиль кода

Поля класса именуются с префиксом m_, использование венгерской нотации рекомендуется (на то есть свои причины, которые здесь обсуждать нет смысла):

Структура кода

SDK, так же как и движок, разделён на несколько частей.

Вот пути до некоторых таких файлов:

ВАЖНО: При внесении ЛЮБЫХ изменений в VPC файл решение должно быть заново перегенерировано!

Генерация проектов

Исключение HL2

SDK имеет внутри себя также разделение на HL2 и Episodic. Использование второго позволит нам иметь некоторые фичи, например отдельную от стамины шкалу заряда фонарика.

И поэтому, чтобы не компилировать лишний код, мы можем просто исключить HL2 из скриптов:

Другие скрипты

Рядом с creategameprojects.bat также лежит его клон для bash а также два интересных файла — createallprojects.bat и его клон для bash.

Эти два скрипта заставляют VPC создавать проекты не только для чистых библиотек мода, но и для различных утилит, таких как vrad (Radiosity!) или height2normal.

Сейчас использовать я его вам настоятельно не рекомендую, так как свои собственные компиляторы карт нам пока не нужны.

Первичная сборка и запуск

Сборка

Чтобы удостовериться, что вы всё сделали правильно, необходимо собрать всё сгенерированное решение. Итак, собираем (вы же ведь открыли решение в IDE?):

После сборки в папке game/mod_hl2/bin/ или game/mod_episodic/bin/ должны появится наши клиентская и серверная библиотеки!

Запуск — Способ 1 — Steam

Запуск — Способ 2 — Visual Studio

Я рекомендую использовать именно этот способ — не копировать же бинарники мода каждый раз после сборки!

Если карта загрузилась и вы можете передвигаться и двигать камеру мышью — сборка успешна!

Первая модификация в коде

Функции семейства Msg()

Заключение

Чему мы научились?

[Я надеюсь, что] из данного урока мы выяснили:

Что дальше?

Во второй части мы разберем систему сущностей Source SDK.

SourceCE/Source-SP

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

This branch is 134 commits ahead of ValveSoftware:master.

Open a pull request to contribute your changes upstream.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Source SDK 2013 Community Edtion

This is a variation of Source 2013 with community changes to make the game look, run, and play more efficiently and add tools for developers. Some examples are implementing Physically Based Rendering, adding Biohazard’s ShaderEditor, implementing CSM, and more.

If you want to use this mod in your own creations, add attribution to your mod (say that you used this branch and give a link to it). We recommend you use the GitHub client when downloading this because we update frequently.

If you want to help contribute, message Wazanator on Steam or on Discord, or join our Discord server: https://discord.gg/GYza458

Alternatively, you can view proposed changes to be added via this link: https://docs.google.com/document/d/1yRjjMOtkjO590ApCdRn00wWshT9KKOYO0ESQIKBveOw/edit The latest suggestions and changes will always be found on Discord and GitHub

At this time only Singleplayer mods are being worked on, Multiplayer updates should be not-so far into the future.

SOURCE 1 SDK LICENSE

Source SDK Copyright(c) Valve Corp.

THIS DOCUMENT DESCRIBES A CONTRACT BETWEEN YOU AND VALVE CORPORATION («Valve»). PLEASE READ IT BEFORE DOWNLOADING OR USING THE SOURCE ENGINE SDK («SDK»). BY DOWNLOADING AND/OR USING THE SOURCE ENGINE SDK YOU ACCEPT THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE PLEASE DON’T DOWNLOAD OR USE THE SDK.

You may, free of charge, download and use the SDK to develop a modified Valve game running on the Source engine. You may distribute your modified Valve game in source and object code form, but only for free. Terms of use for Valve games are found in the Steam Subscriber Agreement located here: http://store.steampowered.com/subscriber_agreement/

You may copy, modify, and distribute the SDK and any modifications you make to the SDK in source and object code form, but only for free. Any distribution of this SDK must include this LICENSE file and thirdpartylegalnotices.txt.

Any distribution of the SDK or a substantial portion of the SDK must include the above copyright notice and the following:

tjhorner/node-source-engine

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

This branch is not ahead of the upstream ValveSoftware:master.

No new commits yet. Enjoy your day!

Latest commit

Git stats

Files

Failed to load latest commit information.

README

About

The 2013 edition of the Source SDK

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Source SDK 2013

This article or section needs to be cleaned up to conform to a higher standard of quality because:
OS X instructions are incomplete, the files cannot be possibly built due to the Windows dependencies, they need to be re-written from scratch. Shader build instructions are poorly written, not crossplatform friendly. Valve Project Creator instructions are incomplete.

For help, see the VDC Editing Help and Wikipedia cleanup process. Also, remember to check for any notes left by the tagger at this article’s talk page.

Setting Up (All Platforms)

Setting up the Source SDK Base

Install Source SDK Base 2013 (multiplayer or singleplayer depending on your mod) from Steam->Library->Tools or from the links below:

Getting the code

Method one: Using the GitHub Desktop client (Windows/OS X)

Method two: Using the command line (Windows/OS X/Linux)

Method three: Downloading the ZIP archive

Setting up (Platform Specific)

Source SDK 2013 on Windows

Step One: Installing Visual Studio

You can also compile without Visual Studio, or using a different version.

As of 2021, Microsoft has removed the packages needed for the web-based VS2013 installer to work. To install VS2013 using the ISO method, follow these steps.

If at any point you get stuck, you can watch this video.

Also download and install the Multibyte MFC Library.

Step Two: Installing the Microsoft Speech SDK

Step Three: Compiling the Source SDK and preparing project files

\mp\src\ and run createallprojects.bat and creategameprojects.bat

Step Four : Building the shaders

Source SDK 2013 on OS X

Step One : Requirements

Step Two : Generating the Xcode projects

Run the following scripts to generate project files.

games.xcodeproj and everything.xcodeproj will be generated in the src folder.

Step Three : Building

Step Four : Binaries

When successfully built, client.dylib and server.dylib will be created and ready to use with the desired Source SDK Base 2013 branch (singleplayer or multiplayer).

Source SDK 2013 on Linux

To do: Add instructions for building with the latest Steam Runtime.

Step One: Getting the basic C/C++ development tools

You should already have these, but to be sure, you can run the following command in a terminal:

AMD64 (64 bits) users will need to download and install additional packages to target the i386 (32 bits) architecture, this can be done with this command in a terminal:

Step Two: Preparing the Source SDK 2013

Assuming you have already cloned the Source SDK 2013 through Git (or downloaded the ZIP file), just run the following commands (by replacing [SDK_ROOT] by the location of the Source SDK 2013, [GAME] by «sp» or «mp» depending on your mod and [SCRIPT] by either «./createallprojects» or «./creategameprojects»), go into :

Depending on the script you ran, you will have a master Makefile called games.mak or everything.mak that will be generated in the src folder.

Step Three: Downloading, installing, setting up the Steam Client Runtime

The Steam Client Runtime will help you guarantee compatibility with most GNU/Linux distributions. It is recommended to install it in «/valve/steam-runtime», if you don’t like this and wish to install the Steam Client Runtime elsewhere: symbolic link is your friend. We are going to assume you want to do the first option. Run the following commands in a terminal, make sure to replace «[USER]» by your login and «[GROUP]» by your group name:

Run the «./setup.sh» script in the «steam-runtime» directory, select the «i386» architecture and one configuration of your choice, say «Yes» to everything related to updates.

Step Four: Time to compile

In a terminal (like always), «cd» into the «sp» (singleplayer) or «mp» (multiplayer) directory of the SDK and the «src» directory, just run the following command to compile (replace [MAKEFILE] by «games.mak» or «everything.mak» depending on the one available to you):

If everything went well, you should have the «client.so» and «server.so» files in the «game» directory to load with the appropriate Source SDK Base 2013. You can get more instructions on using the Steam Client Runtime by reading the «README.txt» file in the installed runtime directory.

Setting up on Steam

Other information

Adding new files with the Valve Project Creator

VPC generates project files for all of the platforms that the SDK supports, so if you want to add files to your project in a way that will allow you to easily build on other platforms, consider using VPC. For example, to add a file to a multiplayer game, you could add a line to src/game/client/client_hl2mp.vpc.

Directory structure

Troubleshooting

Or if you don’t feel like downgrading to VS2013 you can try this alternative solution and see if works for you.

Once You finish It should look like this:

MSB8008: Specified platform toolset (v120_xp) or (v120) is not installed or invalid (Windows)

(Project->Properties->Configuration Properties->General->Platform toolset = Visual Studio 2010(v100))

Issues with «min» or «max» from Steam Runtime when Compiling on Linux

If you get any issues mentioning «min» or «max» while compiling on Linux, it is because you are including something that references the STL, and Valve’s macros for min and max are conflicting with it.

Usually GCC is pretty good about telling you which files in particular are erroring.

Go to those files, and surround the erroneous includes with:

This should allow you to compile. Make sure to only wrap the includes that are using the STL, as other, game-related includes may require the Valve min/max macro defines!

evil-inject0r/Source-Engine-2019

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

This branch is 192 commits ahead of quiverteam:master.

Open a pull request to contribute your changes upstream.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Source Engine 2019

Custom Source Engine branch based on Source Engine 2007 currently available on Windows in x86. Forked from Quiver.

Install Visual Studio 2019 Community, Make sure to go to Individual components and install C++ MFC for v142 build tools (x86 and x64)

Run /src/createallprojects.bat and build the solution either as release or debug.

Run /src/materialsystem/stdshaders/buildallshaders.bat, then build stdshader projects.

64-bit support is being worked on. In the current state the entire codebase compiles as 64-bit but it cannot be started at this point. Feel free to contribute with a pull request.

Run createallprojects-x64.bat to create 64-bit projects. To build 64-bit projects you need to run build-solution-x64.bat through the Microsoft Developer Command Prompt for VS2019.

You can run the engine with run_mod_hl2.bat or run_hl2r.bat.

Linux support is currently being worked on in the posix-support branch. Feel free to contribute with pull-requests.

Feel free to contribute to the project with pull requests. They will be reviewed and merged as fast as possible.

Source SDK 2013

Для начала скачайте исходный код размещённый на GitHub Valve Software Source SDK repository. А теперь вперёд, к созданию великих и прекрасных модов!

Скачивание исходников с GitHub

Git репозиторий

Установка клиента для GitHub (Windows & Mac)

Если Вы хотите обновить код, вы можете сделать это, нажав «Sync» в самом клиенте или кнопку «Sync Branch» в самом репозитарии.

Git CLI (Для всех платформ)

Подробные инструкции о том, как работать с Git на любой платформе с использованием командной строки, включая обновление с репозитария, смотрите на GitHub.

Так, например, с помощью командной строки можно создать копию source sdk 2013 на Вашем компьютере (только с установленным CLI клиентом):

Скачивание

Можно просто скачать ZIP архив со всеми обновлениями, но соответственно загружать и обновлять код придется в ручную.

Особенности создания файлов проекта на различных ОС

Создание файлов проекта и make-файлов

SDK 2013 использует Valve Project Creator (VPC) для создания специальных файлов платформы и make-файлов проекта. Эти специальные файлы, необходимы для создания SDK. Если после выполнения этого шага, Вы обновили какие-либо файлы, то необходимо все действия выполнить повторно.

ОС Windows

В результате должны появиться файлы с расширением *.vcxproj (Visual Studio Project) и *. SLn(Solution) в директории SRC.

ОС Mac OS X & Linux

В результате в Mac OS X должны появиться файлы проекта `*.mak` и Xcode в директории SRC.

в ОС Linux, `.mak` файлы будут сгенерированы в SRC директории.

Информация о VPC

Для получения дополнительной информации о том, как можно использовать скрипты VPC перейдите на страницу, или выполните следующую команду под любой ОС:

Информация о Git репозиторий и игнорируемых файлах

Все сгенерированные файлы с помощью VPC перечислены в файле с расширением *.gitignore и игнорируются при обмене с Git репозиторием.

ОС Windows

Требования к компонентам системы

Чтобы создать Source SDK 2013 под ОС Windows вам нужно Microsoft Visual Studio 2010 с Service Pack 1. Также можно использовать Visual Studio 2012 но только при установленном Visual Studio 2010, при этом в настройках проекта не выбирать «updating», при новой компиляции (Дополнительно в комментариях на GitHub).

Если для создания вашего проекта нужен phonemeextractor, то вам необходимо скачать SAPI 5.1 от Microsoft. Мы не поставляем Speech SDK с Source SDK. Для установки просто поместите sapi51 в каталог src/utils/.

Создание

В результате у Вас должны появиться client.dll и server.dll, необходимые для загрузки Вашего мода под Source движком.

Создание шейдеров

Для добавления шейдеров в ваш мод вам необходимо создать специальные файлы. Для этого, откройте окно командной строки и введите:

Более подробную информацию об инструментах работы с шейдерами Вы можете найти в Source SDK здесь.

Mac OS X

Требования к компонентам системы

В Mac OS X, вам понадобится установленные Xcode 4.2 и «инструменты командной строки» («Command Line Tools»). Вы можете найти это в:

Создание

Запустите инструменты, введите следующую комманду в Terminal:

Когда успешно соберется, вы должны увидеть client.dylib и server.dylib файлы загруженными вместе с Source SDK Base 2013 на ваш выбор.

Linux

Время выполнения клиента Steam

Для построения Source SDK 2013 на Linux ОС, вы должны иметь Steam Client Runtime.

Замените на ту версию, которую только что распаковали.

Выберите вашу архитектуру и debug/release свойства. Затем ответьте Y ко всему остальному.

Постройка SDK

Выполните следующую команду:

В результате у Вас должны появиться client.so и server.so, необходимые для загрузки Вашего мода под Source движком.

Организация кода

Принятые обозначения в названиях файлов

Каждому каталогу требуется свой Source SDK 2013 Base AppID (Идентификатор приложения) для получения базовых файлов:

Эти два базовых приложения очень похожи, различаются в основном графиком обновления. Singleplayer база обновляется только при обновлении HL2 или Эпизодов, которые происходят не так часто. Multiplayer база обновляется несколько раз в год чтобы включить изменения в движке от TF2 и Counter-Strike: Source. Ни одно из этих обновлений не должно сломать совместимость модов.

Структура папок

У всех папок примерно одинаковая структура:

Мы рекомендуем вам следовать данного соглашения при создании собственного мода.

Общие ошибки

Здесь перечислены общие ошибки SDK 2013, имеющиеся на данный момент. Используйте Discussion перед написанием других решений.

«RegKey ошибки при генерации проектов»

Эта проблема обычна вызвана отстутствием ассоциаций с расширениями файлов в вашем реестре.

Visual Studio 2010

error MSB8008: Specified platform toolset (v120_xp) or (v120)

(Project->Properties->Configuration Properties->General->Platform toolset = Visual Studio 2010(v100))

Вы так же можете увидеть действия на скриншоте.

Это работает в Microsoft visual C++ 2010 SP1, как при «release» так и при «debug».

Visual Studio 2012

Утилита созданная участником сообщества для исправления такого типа ошибки в Visual Studio 2012. Используйте на свой риск. Скачать здесь: GitHub (Требуется AutoIt v3).

Не компилируется vgui_controls

Проблема решается приобретением свежей копии дистрибутива SDK. Если вы используете локальный GitHub репозиторий, синхонизируйте (pull) ваши репозитории. Иначе можете скачать ZIP-архив и обновить файлы вручную.

nillerusr/source-engine

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Welcome to source engine:)

About

Modified source engine (2017) developed by valve and leaked in 2020. Not for commercial purporses

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 11

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

SDK Installation

The Source SDK is freely available to all Steam users. It is used to develop mods and content for the Source 2006, Source 2007 and Source 2013 engine branches.

Valve games since 2008 onward started to have their own SDK or Authoring Tools, and are engine versions that have no source code available to the public (except Alien Swarm):

SteamPipe migration and abandonment of the Source SDK app

Previously these tools were distributed together under the «Source SDK» tool, which resided in a totally different folder from the games. Valve moved towards a model more similar to L4D and CS:GO. The SDK tools are currently shipped with the game by default. Note that the tools are only available for Windows.

The tools are located in the respective bin folder for the game (e.g: [steam]/steamapps/common/Team Fortress 2/bin ) and are meant to be launched from the following batch files:

Installation of source code and launcher

The following instructions are appropriate if you need to download Source code. If you only need the authoring tools, they probably do not apply to you.

Source 2013

Legacy branches

Click here to install the Source SDK For future reference, or if that doesn’t work:

Running

Once Steam has finished downloading you can launch the SDK from the Tools tab. You can also create a desktop shortcut by right-clicking on the SDK in the Tools tab and clicking Create desktop shortcut from the context menu that appears.

When you first run the SDK it will spend a long time extracting its downloaded archive to loose files on your disk. This will not happen again until the SDK is next updated.

After that, you will be able to select a game and run any of the tools provided by the launcher. However, you will run into problems unless the game you want to work with is fully up to date. You can make sure it is by launching the game and quitting once you get to the main menu.

Where do I go from here?

If you want to learn about how to create content for the Source Engine in general, the main page of the Source SDK documentation is a good place to start.

VSES/SourceEngine2007

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

About

Topics

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

ar1a/Source-Engine-SDK

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Setup like this

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Is the source code of the Source Engine available?

Is the full C++ source code of the Source Engine available?

I know the SDK is available with the purchase of a Source-based game, but my goal is to find a open-sourced game engine that includes its full implementation details for learning purposes.

2 Answers 2

No, it is not. You may obtain a source license from Valve, but Source itself is not open-source.

Further, it is generally a very dangerous approach to use entire existing engines as learning material without guidance from somebody who was heavily involved in the development of that engine.

Source code alone only tells you the how of particular design decisions, not the why behind most of those decisions which is often extremely important given that so many choices in software engineering are from among generally equally-valid options. You need context to understand why a choice is good, and if you just look at the source of some engine and parrot their techniques and idioms, you are hardly learning anything useful.

Further, just because code shipped a game doesn’t make that code good (Source in particular is prone to lot of now very outmoded design decisions with respect to C++ and OO, for example). There are plenty of horror stories dwelling in the engine codebases of even the most successful AAA titles. And as an impressionable neophyte, how are you going to be able to tell the good code from the bad?

Be very careful using source code as a learning resource, and make sure to pair it with as much supplementary information as you can.

tl;dr: Learning how to make an engine is often as useful to game making as learning to build your own computer and operating system from scratch. If you not an expert in the field, you probably do not want to make an engine. Make a game instead, the engine part already exists. Later on if none of the engines you have access to meet the criteria for your game design, you could focus on building that specific aspect and hell it might be useful to others as well since you are creating something new and not rehashing a less robust version of something that people already invested thousands of hours in.

Long version: If you really want to learn how to write an engine, don’t look at an existing engine yet. Learn instead of the parts (algorithms) that make an engine, be it rendering, physics or path finding etc. Once you gain a deep understanding of a specific aspect, you may want to check out source.

You normally do not wish to learn directly from source unless there is no superior alternative. Even experienced programmers normally would not look at the source of an entire engine to learn from it (if they can help it), they would most likely inspect a specific part of it or tweak a certain part of it. Trying to look at the source for pure learning purpose would not expose the procedure and thought process behind the engine code; That would be like tearing a building apart ti pieces in an attempt to see its insides in order to learn how to build one. While I agree with Josh’s answer, I will take it another step further, you do not even learn the «How» in many senses (unless you are familiar with the field); for instance, what methodology was used by the programming team? What principles did they rely on to implement working code? What tools and techniques did they use for debugging? All these questions are sometimes more important than the code itself (for learning purposes).

If you do wish to learn from source, look for source that is well documented and has a strong community built around it. Reading (engine) code, even if you’ve written it yourself, is often confusing.

Source SDK. Вступление

Всем привет! Результаты голосования в моей предыдущей публикации показали, что среди вас есть люди интересующиеся данным направлением.

Итак, для того, что бы начать работать с Source SDK нам понадобится.

По пути (\Steam\steamapps\common\Source SDK Base 2013 Singleplayer\bin) hammer.exe

Открываем путь \Source SDK Base 2013 Singleplayer\ и создаем папку mymod и файл gameinfo в формате текста и следующим содержимым

Запускайте хаммер, все работает!

Не могу понять, какой смысл изучать Source в 2019 году? Только если ты прям мощный фанат какой-то из игр Valve.

Ну например, низкий порог вхождения, что бы освоить фундаментальные основы.

А чем тот же Unity или Godot не годны? На них хотя бы игру потом можно сделать. С таким уже успехом можно изучать редактор Starcraft 2 или Creation Kit.

Годны, любые, которым владеет умеющий человек годны еще как.

Не соглашусь, здесь инструментарий можно так же расширять.

А с помощью unreal engine нет?)

Настраивается в два клика. Простой уровень в три клика.

Никакого, как и в 2002-ом. Там все скрипты уже написаны, движок для ленивых миллионеров.

Ну если сравнивать блек месу с left alive, anthem или с тем же project borealis то можно понять какой движок более прогресивный и современный

Мне так не кажется, там весьма затратный по времени процесс, объединять с допустим маном по редактору я не хочу.

Эх, помню свои старые уровни на Source с 2010 года (когда только начал изучать) и по сей день, иногда возвращаюсь чтобы закончить свои уровни для проекта. Сам не понимаю почему Source SDK, ведь есть Юнити и анриал, просто есть какой-то шарм в движке. Если был бы Source 2 SDK перешёл бы на него, но, увы, он доступен только внутри компании.

Просто BSP архитектура)

BSP тоже есть в UE4, разве нет?

Вот тоже бесился с освещения, когда делал уровень для CS:GO.

CSGO? Там же норм свет, надо просто смотреть пресеты для скайбокса

Там вроде сломано освещение в реальном времени.

Тестовое задание или техническое?

Везде полезем, куда глаза глядят туда и полезем, попробуем что-нибудь необычное, полазим по форумам разным, побыдлокодим конечно же!

Я в процессе уже

Source Inside

Source Tools

Возможно вы новичок и не имеете представления что такое программирование на C++ и что стоит за этими всеми названиями: «компиляция», «класс», «интерфейс» и так далее, в таком случае, вы должны приобрести базовые навыки программирования на языке C++, после чего можно будет полноценно выполнять поставленные задачи перед программистом мода.
Source SDK предоставляет исходный код для модификации движка игры.
Это означает что вы обладая определенными знаниями и инструментами можете при наличии у вас этого исходного кода внести в него нужную вам функциональность.
Что такое движок?
Например есть некая игра которую вы запускаете на вашем компьютере.
Игра состоит из программного кода и файлов с данными.
Файлы с данными нетрудно понять что это — то из чего строится игровой мир, графика, модели карты,
А код — это то что выполняется процессором, грубо говоря, чтоб эти файлики могли отображаться на экране, двигаться и звучать.
Эту программную часть и называют «движок».
Движок состоит из нескольких систем, каждая отвечает за свою задачу (рендеринг графики, работа с файлами, обработка комманд, работа с сетью, организация игровой сцены, игровые объекты…)

2. Исходники из Source SDK. Скачать всегда можно при помощи Steam.

3. Microsoft Visual Studio 7.1. Работа над кодом производится в данной среде для работы с проектами Visual С++ 7.1 от фирмы Microsoft.
Возможно есть другие пути компиляции проектов Visual С++ но это отдельная тема.

4. Знание как устроен Source SDK.
Часто программисту нужно самому менять те данные которыми оперирует код и знать каким образом эти данные организуются.
Для этого необходимо:
— изучить документацию по Source SDK: http://www.valve-erc.com/srcsdk;
— знать какие есть команды и настройки консоли для разрабочиков модов;
— понимать как создаются карты (bsp);
— понимать как создаются материалы (vmt/vtx);
— понимать как создаются модели (mdl);
— понимать как создаются звуковые скрипты и ресурсные файлы.
Эти вопросы рассматриваются в других туториалах. 5. Игра Half-Life для запуска вашего собственного мода.

После того как вы создали новый мод (Play Games → Tools/Source SDK → Create a Mod → Modify Half-Life 2) открываем файл src/Game_sdk.sln
Файл sln — это Solution — решение, такой вот термин в Visual Studio. Почему не называют его проектом как в Visual Studio 6?
Решение (.sln) состоит из нескольких проектов (.vcproj), которые можно генерировать все сразу или по отдельности.
Данный файл решения состоит из двух проектов:
client — клиент
hl — сервер
Зачем их два, а если у нас например, не будет мультиплеера в игре?
В любом случае, будь то мультиплеер или синглплеер движок будет состоять из двух частей. Это обясняется тем что сам механизм имитации игрового мира разделен на две зависящие друг от друга стороны.
Что делает сервер, а что клиент, в чем их разница?
Сервер выполняет имитацию виртуальной реальности в реальном времени позволяя синхронизировать различные игровые объекты;
к серверу присоединяются клиенты которые тоже являются этими объектами, один или несколько, вообще в движке Source может быть до 255 клиентов.
В случае сетевой игры через интерент или локальную сеть, запускается общий сервер который синхронизирует всех клиентов, а в одиночной игре работают только свой локальный сервер и клиент.
За что отвечает клиент? Он выполняет ввод управления от игрока и вывод информации в том числе поступившей от сервера. Тоесть он реализует интерфейс с игроком.
Обычно все что невозможно (нет надобности) каким-либо образом выводить для игрока не выполняется на клиенте.
Вообщето клиент имитирует примерно то же что и сервер, но не может превышать больше полномочий чем сервер. Поэтому для сервера важно только то что клиент может передавать состояние игрока, и может вносить разные настройки сервера, предусмотренные разработчиками.

Вот мы и пришли к тому что в движке есть две разные стороны которые выполняются паралельно и зависят друг от друга.
Теперь как это выглядит в исходном коде.
Есть часть кода который отвечает за сторону клиента, есть часть кода сервера, и есть часть кода которая у них общаяя.

В результате компиляции этого кода получается два DLL модуля (клиент и сервер).

Серверный код находится в директории src/dlls.
В нем содержится иерархия серверных классов, в котором одни классы являются базовыми для порождаемых дочерних классов. При проектировании классов все общие свойства нескольких дочерних классов содержатся в родительском.
Серверные классы обычно имеют имена подобные CИмя (CBaseEntity, CBasePlayer).
Сервер отвечает за суть происходящего в игре, для него не важно как это нужно отображать на экране игрока, важна сама логика происходящего.
В результате сборки проекта src/dlls/hl_sdk.vcproj получается файл server.dll.

Код клиента находится в директории src/cl_dll.
Содержит иерархию клиентских классов. Классы клиента обычно имеют имена подобные C_Имя (C_BaseEntity, C_BasePlayer). Все классы игровых объектов которые участвуют в имитации мира имеют соответствующий класс на стороне сервера.
Здесь содержится код управлющий рендерингом моделей, озвучкой, обработка GUI-интерфейса, вывод текстовых сообщений, обработка ввода клавиатуры и мыши
В результате сборки проекта src/cl_dll/client_sdk.vcproj получается файл client.dll.
Если поместить DLL файлы клиента и сервера в директорию bin вашего мода, движок сможет их подключить при запуске.

Общий код лежит в директориях src/public и src/game_shared.

В директории linux_sdk содержатся файлы для создания специального для этой платформы файла компиляции — Makefile, если вы занкомы с Unix, то уже догадались что он нужен для компиляции порта сервера под Linux.

Кроме того в Source SDK есть разные вспомогательные исходники, которые непосредственно не относятся к движку игры, их можно найти в директории src/utils
Это различные утилиты, ну например вы решили сделать какойто свой редактор для файлов в форматах движка Source, вам могут потребоваться такие исходники.

Вникаем в подробности

Для начала сделаем первый шаг в программировании мода.
Открываем файл src/dlls/hl2_dll/hl2_player.cpp
Находим реализацию метода PlayerUse, который отвечает за нажатие на клавишу USE

CBaseEntity *pUseEntity = FindUseEntity ();

Сборка файлов выполняется коммандой Build → Build Solution.
В окне вывода (Output) мы можем видеть вывод процесса сборки:

Первая компиляция может занимать довольно много времени.
Если сборка произошла удачно, в самом конце вывода будет сообщено:

Build: 2 succeeded, 0 failed, 0 skipped

Сгенерированные в результате файлы автоматически копируются в директорию bin вашего мода (в соответствии установкам Custom Build Step).

Теперь если запустить игру с нашими изменениями при использовнии каких-либо предметов (поднимите какойто предмет клавишей USE) мы должны видеть сообщение «Hello MOD!».
Запускать мод можно с помощью файла run_mod.bat в директории вашего мода.

Рассмотрим подробнее параметры командной строки для запуски собственных модов.
Вот пример:

Запомните одну из очень ценных возможностей имеющуюся в Visual Studio — это поиск в файлах с кодом.
Find in Files — поиск в файлах или Ctrl+Shift+F с клавиатуры.
С помощью поиска вы можите исследовать исходный код, и находить самые важные для вас места для модификации.

Первым делом следует рассмотреть базовые вещи с которых нужно начинать знакомство с устройством движка.
Серверу и клиенту предоставляются различные программные интерфейсы которые предоставляют огромный список различных возможностей.
Например,
IPhysics — обработка физики;
IMaterial — огранизация системы материалов;
ICommandLine — работа с коммандами консоли;
IBaseFileSystem — запись/чтение файлов;
IEngineSound — вывод звука;
IInput — ввод клавиатуры или мышки;
и так далее…
Этот список довольно длинный, детальное рассмотрение требует большего объема чем данный туториал.

Чтобы в определенном месте кода сделать проверочный вывод информации на экран например чтобы проконтролировать как выполняется код — используйте вспомогательные функции:
UTIL_ClientPrintAll, ClientPrint или Msg

При дальнейшем изучении как устроен движок встретится много деталей которые важно будет понимать:
серверные и клиентские энтити и их система взаимодействия, таблицы строк, система сообщений, события, обработчики событий, система кэширования, и многое другое.
Все это рассмотрим в следующих туториалах.

AgentAgrimar/source-sdk-trilogy

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

A fully working Half-Life: Source, Half-Life 2 + Episodes, ready to be modified and compiled!

Source SDK Copyright(c) Valve Corp.

Any distribution of the SDK or a substantial portion of the SDK must include the above copyright notice and the following:

If you would like to use the SDK for a commercial purpose, please contact Valve at sourceengine@valvesoftware.com.

About

A fully working Half-Life: Source, Half-Life 2 + Episodes, ready to be modified and compiled!

lua9520/source-engine-2018-hl2_src

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

About

Leaked TF2 Source Engine source code from

2018. Thanks Tyler McVicker! (lib, tools/runtime excluded)

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

BlackRa1nFR/source-2003

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

About

Source Engine 2003 code leak

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

thexa4/source-pbr

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README

About

Source Engine Physically Based Rendering implementation

Topics

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 6

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Source engine source code

10,284	уникальных посетителей
519	добавили в избранное

You can find a more up to date version on my site now: https://www.wazanator.com/tutorials/sp2013setup/

I would also highly recommend checking out Mapbase! It has a lot of great additions to the Source SDK 2013 singleplayer base including Vscript support.
https://www.moddb.com/mods/mapbase

Don’t feel like reading or need a visual aid? Here’s a video

Check out my other guide if you are wanting to do multiplayer

EDIT: It would seem Steam does not like my links to Microsofts site for some reason. So if you see LINK REMOVED let me know in the comments. But all links should be in the description of the video

To start off you’re going to need to download a few things:

NOTE: Default notepad has some issues when looking at files like gameinfo.txt the formatting is kind of off. It’s still usable but I highly recommended notepad++ so you dont have to deal with it.

Once you have installed both Source SDK base 2013 singleplayer and visual studio 2013 run both to make sure they launch before continuing.

Choose a location you want for your mod source files to be. This will serve as the location that you will keep all your files both WIP and final. This includes but isn’t limited to maps, models, sounds, textures, scripts, code, etc.

Once you’ve picked out a spot create a new folder and name it your mods name.

Move the source-sdk-2013-master.zip into this folder, right click it and choose to extract it here.

Open up the Source-sdk-2013 folder and delete the MP branch since we do not need it.

NOTE: There can’t be any spaces at all in the file path, I suggest putting it at the top of one of your drives

Run the SpeechSDK51.exe file you downloaded. It should unzip contents to a selected folder. One of the contents it unzips is Microsoft SDK 5.1.msi. Running this with the default settings should create a directory in C:\Program Files (x86) called Microsoft Speech SDK 5.1. Copy the Microsoft Speech SDK 5.1 directory into the src/utils directory of your mod and rename it sapi51.

Navigate to sp\src\utils\sapi51\Include and open sphelper.h in visual studio.

The following are changes you need to make to the code (hint if your line numbers are off by default read this [msdn.microsoft.com] ):

Navigate to source-sdk-2013\sp\src

Run both createallprojects.bat and creategameprojects.bat

Open games.sln in visual studio 2013. It shouldn’t ask if you want to update files but if it does say yes. Right click on the games solution and go to properties.

Choose Configuration Properties then click Configuration Manager.

For the Active Solution configuration choose Release

Click Close, then OK.

Right click on the games solution again but this time choose «Rebuild Solution». Wait for it to compile. If you did everything correctly you should get no errors. If you get an error debug it like you normally would, if you have never really coded before this means google the error and try and figure out why it broke on your own. Yes this might mean spending thirty minutes to an hour to figure out what broke. If you can’t figure it out and you have put a good amount of time into trying to do it on your own post on the forums as well as other places like stack overflow.

Do the same thing as above.

NOTE: If you do not plan on modifying things like vbsp, vrad, vvis, shaders and the like you do not need to bother with everything.sln

Go to Steam\steamapps\common\Source SDK Base 2013 Singleplayer

Copy the hl2 folder.

Paste it into Steam\steamapps\sourcemods (should be about 2.6 GB)

Rename it to your mods name (if your mods name contains spaces use underscores instead and use no capitals or special characters).

Source engine source code

1,550	уникальных посетителей
30	добавили в избранное

This guide will walk you through the steps of making your very own functional mod with help of the Source SDK 2013.

In this guide we will set up Visual Studio 2013 along with the important Source SDK 2013.
You will have to download a lot so if you are not patient you should download the neccessary files over night so you do not have to wait.

Side note: Visual Studio 2015 will NOT work with Source SDK 2013!! I tried it myself and I could not get it to work any way possible not even when using the settings from VS 2013! You need Visual Studio 2013 for this guide! I am sorry if you have any other version of Visual Studio installed, but you will have to use Visual Studio 2013 here!

This part is actually pretty simple! (for once at last)

Just press ‘Run’ and ‘Install’ if you are asked to.

and press ‘Open in Desktop’ After that just wait for GitHub Desktop to open and then you are asked to select where to save the files. Just select some directory where you wanna store all your development files. Hit ‘Ok’ and let GitHub do its thing.

After having downloaded the installer for Visual Studio 2013 from the link provided in the ‘Requirements’ section,

you just have to open the downloaded installer. Simple.

Just choose where to install Visual Studio 2013 (Side note: VS2013 will require a lot of space on your hard drive so be careful where you install it!), tick ‘I agree to the Terms of Service’ and you do not have to tick the second box, but you can (I usually leave it unticked). Then you press ‘Continue’ or ‘Install’ depending on your language you use. Then you will see a screen similar to the one on the right of this text. ONLY tick ‘Microsoft Fundation Classes for C++’, because you will not need anything else that is provided here. IF you want to install any of the packages later on just re-download the installer, open it, and press the ‘Modify’ button.

The next step is to press ‘Install’ on the bottom of the screen and grab about 8 and a half mugs of coffee (Well I drank that many I do not know if coffee is your thing so if you do not like coffee then, first of all wtf, but second of all just grab a tea or hot chocolate if that is more your thing)

## 1 1/2 hours later ##
(Thats how long it took for me, but it is hard to compare since I have a download speed of 7.5 Megabyte per second)

After the waiting game is over you should be greeted with a screen where you can log into a Microsoft account. You do not have to, but it will syncronize your settings over every computer aka. instance of VS2013 you log into. If you do not want to or you do not have a Microsoft account then just press the ‘Not now. Maybe later.’ link under the Login button.

NOW VISUAL STUDIO IS READY! good work.

It is pretty simple just run the installer for the VC Redistributable FIRST!! This is very important that you do it in the right order!

Then after installing the VC Redistributable you just install the Link Shell Extension. I advise you to install it on your C:\ drive, because I had some issues with Windows not finding the program sometimes for some random reason when I installed it on a seperate hard drive than the C:\ drive.

Just press: ‘Next’, ‘Next’, ‘Install’ and then you will be asked to restart Explorer. Press ‘Yes’ or restart your computer, but just restarting Explorer is way faster in some cases.

Your complete utils directory should look something like this.

Foot note: Since you copied it to the source-sdk-2013 directory you only need to do this once for both branches (sp and mp) and then the next time you make a game just copy the appropriate folder and rename it to your games name or do it like I do and decide the name later and just name everything ‘project01’, ‘project02’, etc.

For this step you need to be in your source-sdk-2013 directory. just saying.

So if you want to make a multiplayer game; copy the «mp» folder to your desired work location. And if you want to make a singleplayer game do the same for the «sp» folder

After having copied either the ‘sp‘ or the ‘mp‘ folder and renaming it to something useful, you go into the copied directory and open the «src» folder.

For a game that doesn’t need custom shader stuff and doesn’t need to modify the engine itself you just need to run the ‘creategameprojects.bat‘ and wait for it to finish. Then refresh the file browser by hitting the ‘F5’ key.

You should see a new file called ‘games.sln‘. Open it and wait for Visual Studio 2013 to update, parse and scan all files (As shown below).

Then go click the arrow left of ‘Configuration Properties’ and select ‘Debugging’. After that go to the field ‘Command’, click the arrow in the right field, select ‘Browse. ‘ and then open either.

For singleplayer mods:

and for multiplayer mods:

In the next field below (‘Command Arguments’) you will can just copy the following code:

This will start the game in windowed mode so you can see any errors showing up.

The next step is to copy do the same for the Release configuration. You can switch to the Release configuration in the top left of the properties window. Just click the drop-down menu that says ‘Debug’ or ‘Active(Debug)’ and change it to release. Now do the same as before. The exact same. After that change the configuration back to ‘Active(Debug)’.

After that just press ‘Apply’ and close the window or just press ‘Ok’, but do not forget to save the changes.

You probably don’t want to copy the compiled files everytime you change something. That’s why you need the Link Shell Extension. It allows you to trick Windows to think that a symbolic link is a real folder.

This is pretty easy to do. Just select both projects again, right-click and then hit ‘Build Selection’. After that Visual Studio will compile the game for the first time. It will take some time tho.

This is a good point to restart Steam so the game shows up in your library.
If you restart Steam you should see a new game called ‘My First Episodic Mod’ or something in that general direction. Congratulations this is your game / mod.

Source engine source code

1,390	уникальных посетителей
45	добавили в избранное

The Source Engine is a game engine created by Valve Software. The engine was first used in a commercial game in 2004 for the game Counter-Strike: Source. Later that year, Half-Life 2 and Half-Life 2: Deathmatch were both released on the Source Engine as well. Since then, the Source Engine has been used in all of Valve’s commercial games, as well as several third party games and a huge number of mods. And now I’m going to teach you how to make your own Source Mod.

When modding on the Source Engine, there are several different engine versions to choose from. This list will give you a basic idea of which engine type you’ll want to use to create your mod.

Source Engine 2006
This is the oldest version of the Source Engine. This version is used by Half-Life: Source, Half-Life: Deathmatch and various mods built on the old Source 2006 code.

NOTE: Anyone can play mods on this engine version, as long as they have the Source SDK Base 2006.

Source Engine 2007
This is the engine version that most Source Mods use. Various Source Mods have used this engine version such as Black Mesa, Dear Esther (mod), Minerva and The Stanley Parable (mod).

NOTE: Anyone can play mods on this engine version, as long as they have the Source SDK Base 2007.

Source Engine 2009
This is the engine version that is currently used by Half-Life 2, Half-Life 2: Episode 1, Half-Life 2: Episode 2 and Portal. This engine version doesn’t currently have a source code available.

NOTE: You can still mod this engine version, read Creating a mod manually.

Source Engine MP
This is the engine version that is currently used by multiplayer Source games. This version is used by Team Fortress 2, Half-Life 2: Deathmatch, Counter-Strike: Source, Day of Defeat: Source and Garry’s Mod. This engine version doesn’t currently have a source code available.

Other things you should know
Games such as Left 4 Dead, Left 4 Dead 2, Portal 2, Counter-Strike: Global Offensive and DotA 2 all run on different engine branches or have their own engine branches.

Half-Life 2 Single Player
Projects for Source Engine 2006 and Source Engine 2007.

Half-Life 2 Multiplayer
Projects for Half-Life 2: Deathmatch. This option is only available if you own Half-Life 2: Deathmatch; otherwise it will be greyed out.

Multiplayer mod from template
A specially-created SDK project that allows you to configure settings such as if your mod is team based, or if you have abilities such as sprinting and prone. This option does not require Half-Life 2: Deathmatch.

Source code only
Dumps the code without creating an actual mod. This handy if you are only creating a server plugin.

Whichever option you choose, you get the same actual source code files (even if you didn’t own one or another game). You also get an «everything» solution which includes a collection of development tools.

Most of the information from this section is from here.

NOTE: Some information has been edited to make it more accurate.

Step 1: Create a folder under steamapps\SourceMods\ (A mod can actually reside anywhere, but placing it here allows Steam to detect and launch it.)
Step 2: Create a gameinfo.txt in the folder. You now have a mod!
Step 3: Open the SDK launcher and switch to the relevant engine branch.
Step 4: Choose «Edit Game Configurations» and click «Add». Enter your mod’s name and folder.

To get the source code (or indeed any other files of Valve’s that you want to modify) you will need to use GCFScape and access sourcesdk.gcf/src_mod/. Remember to change the custom build steps to point to your mod’s folder.

All information from this section is from here.

Source Engine Features

Rendering System

Source features fast, reliable and flexible technology to render computationally intensive game environments. The highest-performing shader-based rendering available to game developers helps you quickly produce even the most complex scenes quickly and efficiently. Source’s renderer utilizes advanced processor technologies such as multi-core and SIMD, as well as the latest GPU features via DirectX, to bring your vision to life in vibrant detail.

Advanced Shader Technology

Dynamic Lighting and Shadows

Effects

Materials

Modeling and Animation

Compatibility with popular graphics and 3D modeling software lets you model realistic or highly-stylized characters, weapons, vehicles, and props within the Source environment. A robust set of tools help you efficiently rig, animate, and define physics interactions for a wide range of characters and objects.

Advanced Character Meshes

Create believable characters with accurate human characteristics:

Advanced Animation Tools

Environments

Valve Hammer Editor, the Source map creation tool, is an intuitive design environment for constructing level architecture (geometry, texturing, lighting); placing and scripting models, entities, and NPCs; and compiling and running game levels. Included is the VMPI tool, which greatly reduces map build time by distributing compilation across multiple PCs.

Physics

Source’s highly scalable, network-enabled physics system is both processor and bandwidth efficient. Construct responsive, transformable worlds where AI characters interact with physically simulated objects, and sound and graphics follow from physics. Source’s physics features can be controlled by level design.

Game Mechanics

Innovative and seamless interaction between player and non-player characters is a hallmark of Source-powered games. A sophisticated AI system allows NPCs to follow players, join in the fight, or engage the player in epic non-scripted battles. AI characters can run, fly, jump, crouch, climb stairs, and burrow underground.

Programming

Authored entirely in C++, the Source engine is architected with extensibility, flexibility, and performance in mind. Licensees of Source technology have access to all of the source code that Valve uses to build the Source engine as well as our award-winning games. This allows your development staff to spend its time realizing your game design rather than starting from the scratch.

Audio

Source includes a powerful suite of digital audio technologies to create vibrant, dynamic soundscapes within the game world. Seamlessly blend sound effects, dialogue, and music with visual elements for an intensely immersive and realistic playing experience.

Networking

Source’s multiplayer network code is time and gamer tested by millions of players around the world, with an average of more than 9 billion multiplayer minutes played per month.

Console Support

Source offers an ideal development environment for next-gen console platforms, including the Xbox 360™.

Source SDK

As a team largely comprised of former mod developers, Valve is dedicated to providing the best tools and resources for the modding community. The Source engine and SDK give you all the tools you need to produce brilliant game creations—in fact, more Source-powered mods have been successfully distributed as full-fledged commercial products than with any other engine.

The Source SDK is available free of charge via Steam with purchase of a Source-based game, such as Half-Life 2 or Team Fortress 2. Learn more about building Source-powered mods here.

wobbier/source3-engine

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

About

A simple C++ game engine that utilizes OpenGL and Havok Physics

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

ValveSoftware/halflife

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Half Life 1 SDK LICENSE

THIS DOCUMENT DESCRIBES A CONTRACT BETWEEN YOU AND VALVE CORPORATION (“Valve”). PLEASE READ IT BEFORE DOWNLOADING OR USING THE HALF LIFE 1 SDK (“SDK”). BY DOWNLOADING AND/OR USING THE SOURCE ENGINE SDK YOU ACCEPT THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE PLEASE DON’T DOWNLOAD OR USE THE SDK.

You may, free of charge, download and use the SDK to develop a modified Valve game running on the Half-Life engine. You may distribute your modified Valve game in source and object code form, but only for free. Terms of use for Valve games are found in the Steam Subscriber Agreement located here: http://store.steampowered.com/subscriber_agreement/

Any distribution of the SDK or a substantial portion of the SDK must include the above copyright notice and the following:

DISCLAIMER OF WARRANTIES. THE SOURCE SDK AND ANY OTHER MATERIAL DOWNLOADED BY LICENSEE IS PROVIDED “AS IS”. VALVE AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES WITH RESPECT TO THE SDK, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, TITLE AND FITNESS FOR A PARTICULAR PURPOSE.

LIMITATION OF LIABILITY. IN NO EVENT SHALL VALVE OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE ENGINE AND/OR THE SDK, EVEN IF VALVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

If you would like to use the SDK for a commercial purpose, please contact Valve at sourceengine@valvesoftware.com.

This is the README for the Half-Life 1 engine and its associated games.

Please use this repository to report bugs and feature requests for Half-Life 1 related products.

If you encounter an issue while using Half-Life 1 games, first search the issue list to see if it has already been reported. Include closed issues in your search.

If it has not been reported, create a new issue with at least the following information:

Please place logs either in a code block (press M in your browser for a GFM cheat sheet) or a gist.

There are basic rules of conduct that should be followed at all times by everyone participating in the discussions. While this is generally a relaxed environment, please remember the following:

Remember: Just because the issue you reported was reported here does not mean that it is an issue with Half-Life. As well, should your issue not be resolved immediately, it does not mean that a resolution is not being researched or tested. Patience is always appreciated.

tmp64/hl1_source_sdk

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Source SDK for Half-Life 1

This repository contains parts of Source SDK 2013 ported to be used with Half-Life 1 (GoldSource) engine. Specifically:

You can find engine interfaces in tier2/tier2.h:

Documentation can be found on Valve Developer Community:

Exploiting the Source Engine (Part 1)

Introduction

It’s been a long time coming, but here’s my first post on a series about finding and exploiting bugs in Valve Software’s Source Engine. I was first introduced to it through the sandbox game Garry’s Mod in 2010, which introduced me to the field of reverse engineering and paved the way for my favorite hobby, my education, and my eventual employment.

I took a long hiatus from working with the Source Engine when I went to college and got involved obsessed with playing CTF competitions, a type of competition where participants solve challenges that mimic real-world reverse engineering and exploitation tasks. One day, I saw a post made about a TF2 RCE proof-of-concept released against the engine. To be honest, the bug and the exploit was very simple, and nothing more difficult than some of the intermediate challenges one would find in a good CTF. With that knowledge under my belt, I decided to prove myself and come back to the Source Engine with the goal of finding a true Remote Code Execution (RCE).

NOTE: As of writing, the vulnerability has not been publicly disclosed. I will be doing a writeup of the bug and exploit chain if/when it goes public.


Source games Dota 2, CS:GO, and TF2 continue to hold top active player counts on Steam.

The Source Engine

The Source Engine is a third generation derivative of the famous Quake Engine from 1999 and the Valve’s own GoldSrc engine (the HL1 engine). The engine itself has been used to create some of the most famous FPS game series’ in history, including Half-Life, Team Fortress, Portal, and Counter Strike.

Timeline:

The Code:

The first thing that I didn’t truly appreciate about this engine (and other engines in general) is how large it is. The engine is gigantic, featuring millions of lines of C++ code to develop, render, and run games of all types (but mostly first-person games).

The code itself is old and unmaintained. Most of the code was very obviously rushed out to meet deadlines, and honestly it is a huge surprise that the engine even functions at all. This is not unique to Valve, and is very typical in the game development world.

A lot of the C++ classes included in the engine are straight up dead code. Big features were designed and developed, yet only used for very small parts of the engine. The 2013 SDK tools themselves still have difficulty building valid files for their current engine versions of the engine. Classes derive from anywhere from one to nine or more different base classes, and tend to feature a never-ending maze of abstractions on abstractions. Navigating this codebase is time consuming and generally unpleasant for beginners. All in all, the engine is due for a legacy code rewrite that will likely never happen.

Intro to Source Games:

Source Engine games consists of two separate parts, the engine and the game.

Lastly, a big feature of all Source games that was taken and evolved from the Quake engine is the ConVar system. This system defines a series of variables and commands that are executed on an internal command line, very similar to a cmd.exe or /bin/sh shell. The difference is that, instead of executing new processes, these commands will run functions on either the client or server depending on where its run. The engine defines some low-level ConVars found on both the server and client, while the game dlls add more on top of that depending on the game dll that’s running.

This is just an intro, more on all of this to follow in future posts.

The Bugs:

All of this old code and custom formats is fantastic for a bug hunter. In 2018, all that’s truly necessary to perform a full chain RCE is a good memory corruption bug to take control and an information leak to bypass ASLR. Typically, the former is the most difficult part of bug hunting in modern software, but later you will see that, for the SE, it is actually the latter.

Here is an overview of the Windows binaries:

If you’re an exploit developer, you would probably find the lack of stack cookies in a game engine with millions of players to be a very shocking discovery. This is a vital shortcoming of the already aging engine, and is essentially unheard of in modern Windows binaries. Valve is well aware of this protection’s existence, and has chosen time and time again not to enable it. I have some speculation as to why this is not enabled (most likely performance or build breaking issues), but regardless, there is a huge point to make: Any controllable stack overflow can overwrite the instruction pointer and divert code execution.

Hunting:

When hunting for these bugs, I chose to take a slightly more difficult path of only performing manual code auditing on the publicly available engine code. What this allows me to do is both search for potentially useful bugs and also learn the engine’s internals along the way. While it might be enticing for me to just fuzz a file format and get lots of crashes, fuzzing tends to find surface level bugs that everyone’s finding, and never those really deep, interesting bugs that no one is finding.

As I said previously, the codebase for this engine is gigantic. You should take advantage of all of the tools available to you when searching. My preferred toolset is this:

With these tools, my general “process” for bug hunting is this:

Find some section of the client code I feel is exploitable and want to look into more closely

Start reading code. I’ll read for hours until I come across what I think is a possible exploitable bug.

From there, I will open up IDA Pro and locate the function I think is exploitable, then compare its current code with the old, public code I have available.

If it still appears to be exploitable, I will try to find some method to trigger the exploitable function from in-game. This turns out to be one of the hardest parts of the process, because finding a triggerable path to that function is a very difficult task given the size of the engine. Sometimes, the server just can’t trigger the bug remotely. Some familiarity with the engine goes a long way here.

Lastly, I will write Sourcemod plugins that will help me trigger it from a game server to the client, hoping to finally prove the existence of the bug and the exploitability in a proof-of-concept.

Next Time

Next post, I will go more in-depth into the codebase of the Engine and explain the entity and networking system that the Engine utilizes to run the game itself. Also, I will begin introducing some of the techniques I used to write the exploits, including the ASLR and NX bypass. There’s a whole lot more to talk about, and this post barely scratches the service. At the moment, I’m in the process of working on a new undisclosed bug in the engine. Hoping to turn this one into another big payout. Wish me luck!

Установка Source SDK

Source SDK доступен бесплатно всем пользователям Steam Он используется для разработки модов и контента для Source 2006, Source 2007 и Source 2009.

Более поздние игры от Valve используют свой собственный набор инструментов SDK или Authoring Tools:

Authoring Tools в настоящее время поставляется в виде бета-версии соответствующих игр

Мы переводим на Authoring Tools следующие дистрибутивы игр:

Ранее эти средства распространялись отдельно от игры объединенные в один пакет (приложение «Source SDK» ). Сейчас же мы делаем схожую с L4D и CS:GO модель инструментов. Согласно той модели SDK Tools по умолчанию является частью игры, поэтому все, что вам нужно сделать, чтобы запустить утилиты SDK Tools, это запустить игру и обновить её до последней существующей версии. Пожалуйста, обратите внимание, что эти инструменты будут доступны только под ОС Windows.

Теперь обратите внимание на папку BIN. (Например: [steam]/steamapps/common/Team Fortress 2/bin ). Там Вы уведите несколько новых *.bat файлов, который можно использовать для настройки среды разработки и запуска соответствующих инструментов:

Если у Вас есть проблема с запуском, убедитесь что не где в путях не прописана переменная среды VPROJECT. Если Вы все же используете VPROJECT, то проверьте значение этой переменной среды в системе Windows, командой set в командной строке и установите правильное значение.

Установка и запуск

Следующие инструкции подходят только для установки Source SDK. Если Вам нужно установить Authoring Tools к какой либо игре, то смотрите разделы соответствующих игр..

Для установки новой версии Source SDK 2013 смотри: Source SDK 2013

Инструкция для установки старой версии Source SDK:

После того, как загрузка была завершена, Вы можете запустить SDK из вкладки Tools. Вы также можете создать ярлык на рабочем столе, совершив клик правой кнопкой мыши по SDK и нажав на Create desktop shortcut из появившегося контекстного меню.

Запуск

Как только Steam закончит загрузку, Вы сможете запустить SDK из вкладки Tools (Инструменты). Вы так же можете создать иконку на рабочем столе, нажав правой кнопкой мыши по SDK во вкладке Tools (Инструменты) и нажав на Create desktop shortcut (Создать ярлык на рабочем столе) в появившемся контекстном меню.

При первом запуске SDK, он будет в течении длительного времени извлекаться на жесткий диск. Этого не случится снова, пока SDK не обновится.

Что дальше?

Shader authoring/Quick Start

High Level Concepts

The two major pieces of code that have to be written to create a new shader are the HLSL code and the C++ code:

Every shader has one C++ class and one or more HLSL files that it uses to render.

The Source SDK ships with some of our production shaders that can be copied or modified to use in your own mod. To compile them and use them in a game read the following instructions:

2. Install a copy of the source code by running the Create a Mod from the SDK launcher. If the latest version of the source code is already installed, this step can be skipped.

3. Open a Windows command prompt (enter cmd in the start menu ‘run’ dialogue, change to the C:\MyMod\src\materialsystem\stdshaders directory with the cd command. Then type:

This will compile the DirectX 8 and 9 sample HLSL code and copy the resulting files into a directory called shaders in the specified mod game directory.

4. If you wish to build a DirectX 8 shader DLL open stdshader_dx8-2003.vcproj in Visual Studio 2003 or stdshader_dx8-2005.vcproj in Visual Studio 2005 and build it. This will build the C++ part of each shader into a DLL and it will automatically copy the DLL into the game’s bin directory (where the client.dll and server.dll are stored).

Build the solution and verify that game_shader_dx8.dll is now in your game’s bin directory.

5. If you wish to build a DirectX 9 shader DLL open stdshader_dx9-2003.vcproj in Visual Studio 2003 or stdshader_dx9-2005.vcproj in Visual Studio 2005 and build it. This will build the C++ part of each shader into a DLL and it will automatically copy the DLL into the game’s bin directory (where the client.dll and server.dll are stored).

Build the solution and verify that game_shader_dx9.dll is now in your game’s bin directory.

6. Now modify a material (.VMT) file to use the new shaders at the top. Something like the following:

7. The SDK includes some example files that can be copied into a mod to see how to refer to the sample shaders that were just compiled. The relevant sample files are listed below:

Filename	Use
[steam]\half-life 2\hl2\maps\sdk_shader_samples.bsp	Small map that refers to the shaders
[steam]\sourcesdk_content\hl2\mapsrc\sdk_shader_samples.vmf	Map source
[steam]\half-life 2\hl2\materials\sdk\sdk_lightmap.vmt	Material sample 1
[steam]\half-life 2\hl2\materials\sdk\sdk_particle.vmt	Material sample 2

Downloading Unreal Engine Source Code

Steps for connecting to the source code repository and downloading the latest build of Unreal Engine.

In order to understand and use the content on this page, make sure you are familiar with the following topics:

This page provides detailed instructions for subscribers to download the source code for Unreal Engine 4 (UE4) from the Unreal Engine GitHub repository, and toВ get started working with the code.

be an Unreal Engine subscriber.

haveВ a GitHub account.

have associated your GitHub account with your Unreal Engine account as described onВ the UE4 on GitHub page.

You’ll getВ access to all the latest features and bug fixes that Epic engineers make every day, practically up to the minute.

If youВ find a bug that we haven’t fixed yet, but that is crucial to your project, you can unblock your project by making the fix in your own version of the source codeВ and rebuilding your ownВ binaries.

You can improve the engine and help the whole Unreal community byВ submittingВ yourВ fixes and features back to Epic.

If you are an Unreal Engine licensee, you can access the source code through our Perforce server instead of the public GitHub repository.

Source Code Branches

You’ll notice that we’ve published UE4’s source code in three rolling branches.

Release Branch

The release branch is extensively tested by our QA team and makes a great starting point for learning UE4 or making Unreal games. We work hard to stabilize this branch with the goal of releasing new builds every one to two months.

Promoted Branch

The promoted branch is updated with builds for use by our designers and artists. We try to update this branch daily so that our subscribers have access to UE4’s latest stable features. This branch is a great place to learn how feature development works in UE4.

Master Branch

Because the master branch contains cutting-edge technology, UE4 isn’t guaranteed to compile from source.

The master branch tracks live changes being made by our engine team. Our experienced subscribers typically work from this branch when they want to work in tandem with UE4’s developers.

Other branches may appear from time-to-time as we work to stabilize new releases or hotfixes.

Downloading the Source Code

Please follow these instructions to download the Unreal Engine source code.

Please make sure you are running Visual Studio 2015 or higher for Windows Desktop installed before proceeding.

To use Git from the command line, see the Setting up Git and Fork a Repo articles.

If you’d prefer not to use Git, you can get the source with the ‘Download ZIP’ button on the right. The built-in Windows zip utility will mark the contents of zip files downloaded from the Internet as unsafe to execute, so right-click the zip file and select ‘Properties. ‘ and ‘Unblock’ before decompressing it. Third-party zip utilities don’t normally do this.

Install Visual Studio 2017.

Open your source folder in Explorer and run Setup.bat.

This will download binary content for the engine, as well as installing prerequisites and setting up Unreal file associations. On Windows 8, a warning from SmartScreen may appear. Click «More info», then «Run anyway» to continue.

A clean download of the engine binaries is currently 3-4gb, which may take some time to complete. Subsequent checkouts only require incremental downloads and will be much quicker.

Run GenerateProjectFiles.bat to create project files for the engine. It should take less than a minute to complete.

Load the project into Visual Studio by double-clicking on the UE4.sln file. Set your solution configuration to Development Editor and your solution platform to Win64, then right click on the UE4 target and select Build. It may take anywhere between 10 and 40 minutes to finish compiling, depending on your system specs.

After compiling finishes, you can load the editor from Visual Studio by setting your startup project to UE4 and pressing F5 to debug.

To use Git from the Terminal, see the Setting up Git and Fork a Repo articles. If you’d rather not use Git, use the ‘Download ZIP’ button on the right to get the source directly.

Open your source folder in Finder and double-click on Setup.command to download binary content for the engine. You can close the Terminal window afterwards.

In the same folder, double-click GenerateProjectFiles.command. It should take less than a minute to complete.

Load the project into Xcode by double-clicking on the UE4.xcworkspace file. Select the ShaderCompileWorker for My Mac target in the title bar, then select the ‘Product > Build’ menu item. When Xcode finishes building, do the same for the UE4 for My Mac target. Compiling may take anywhere between 15 and 40 minutes, depending on your system specs.

After compiling finishes, select the ‘Product > Run’ menu item to load the editor.

Our developers and support teams currently use the latest version of Ubuntu; as a result, we may not be able to provide support for other Linux distributions (including other versions of Ubuntu).

Open your source folder and run Setup.sh to download binary content for the engine.

Both cross-compiling and native builds are supported.

Cross-compiling is handy when you are a Windows (Mac support planned too) developer who wants to package your game for Linux with minimal hassle, and it requires a cross-compiler toolchain to be installed (see the Linux cross-compiling page on the wiki ).

Licensing and Contribution

Next Steps

Footnotes

The first time you start the editor from a fresh source build, you may experience long load times. The engine is optimizing content for your platform to the derived data cache, and it should only happen once.

Your private forks of the Unreal Engine code are associated with your GitHub account permissions. If you unsubscribe or switch GitHub user names, you’ll need to re-fork and upload your changes from a local copy.

Croteam-official/Serious-Engine

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

This is the source code for Serious Engine v.1.10, including the following projects:

These have been modified to run correctly under the recent version of Windows. (Tested: Win7 x64, Win8 x64, Win8.1 x64)

To build Serious Engine 1, you’ll need Visual Studio 2013 or 2015, Professional or Community edition ( https://www.visualstudio.com/post-download-vs?sku=community ).

Do not use spaces in the path to the solution.

MP3 playback is disabled by default. If you need this feature, you will have to copy amp11lib.dll to the ‘\Bin’ directory (and ‘\Bin\Debug’ for MP3 support in debug mode). The amp11lib.dll is distributed with older versions of Serious Sam: The First Encounter.

3D Exploration support is disabled in the open source version of Serious Engine 1 due to copyright issues. In case if you need to create new models you will have to either use editing tools from any of the original games, or write your own code for 3D object import/export.

IFeel support is disabled in the open source version of Serious Engine 1 due to copyright issues. In case if you need IFeel support you will have to copy IFC22.dll and ImmWrapper.dll from the original game into the \Bin\ folder.

This version of the engine comes with a set of resources ( \SE1_10.GRO ) that allow you to freely use the engine without any additional resources required. However if you want to open or modify levels from Serious Sam Classic: The First Encounter or The Second Encounter (including most user-made levels), you will have to copy the game’s resources (.GRO files) into the engine folder. You can buy the original games on Steam, as a part of a bundle with Serious Sam Revolution ( http://store.steampowered.com/app/227780 )

When running a selected project, make sure its project settings on Debugging is set to the right command:

Before starting the build process, make sure you have a «Temp» folder in your development directory. If it doesn’t exist, create it. SeriousSkaStudio has some issues with MFC windows that can prevent the main window from being displayed properly.

Serious Engine is licensed under the GNU GPL v2 (see LICENSE file).

Some of the code included with the engine sources is not licensed under the GNU GPL v2:

About

An open source version of a game engine developed by Croteam for the classic Serious Sam games.

Enhanced-Source-Project/Enhanced-Source

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README

About

This is an unofficial updated branch of the Alien Swarm branch of the Source Engine. The project focuses on improving functionalities of the engine while keeping it developer friendly.

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 8

Languages

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Особенности Source Engine

Система Рендеринга

Особенностью Source является быстрая, надежная и гибкая технология рендеринга игрового мира. Высокопроизводительный, основаный на шейдерах, рендеринг доступный игровым разработчикам, помогает быстро создавать даже самые комплексные сцены быстро, и эффективно. Технология рендеринга использует продвинутые процессорные технологии, такие как многоядерный рендеринг, технологию параллельного вычисления (SIMD), также как последние графические процессоры интегрированы с DirectX, чтобы передать вам мир в ярких деталях.

Динамическое освещение и тени

Эффекты

Материалы

Моделирование и анимация

Продвинутые сетки персонажей

Создавайте правдоподобных персонажей с точными человеческими характеристиками:

Продвинутые инструменты анимации

Environments

Physics

Game Mechanics

Programming

Audio

Networking

Source’s multiplayer network code is time and gamer tested by millions of players around the world, with an average of more than 9 billion multiplayer minutes played per month.

Console Support

Source offers an ideal development environment for next-gen console platforms, including the Xbox 360™.

Source SDK

Source SDK доступен бесплатно через Steam при покупке игры на базе Source, такой как Half-Life 2 или Team Fortress 2. Узнать больше о создании модов на основе Source можно здесь.

BlackPhrase/OGS

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Gold Source is a version of Quake and Quake is open source so maybe that is an option for you.

GoldSource Engine Clone Prototype

Clean open source reimplementation of the GoldSource game engine
Based on original Quake (Id Tech 2) engine sources

For more information about the project you can visit its official Wiki

Q: What’s this?
A: This is a GoldSource game engine reimplementation using only original id Tech 2 engine (NetQuake/QuakeWorld/Quake 2) sources (and its forks) and no reverse-engineered code (like from ReHLDS or Xash3D)

Q: What’s the purpose?
A: If you can’t see the purpose then you simply don’t need it and you’re just wasting your time here

Q: So no usage of reverse-engineered code at all?
A: Nope, only backtrace logs and a lot of researching of original GS engine history

Q: How much the GoldSource engine is different from the original Quake engine?
A: Let’s say it’s pretty much a «dieselpunk» version of the Quake engine

Q: What are the «backtrace logs»?
A: Call stack of the latest called program functions/class methods before crash of the program. This information allows you to see which function caused the crash and its location in source code. (Backtrace logs don’t show you the actual source code)

Q: Will the engine be able to run my precious (%MODNAME%)?
A: Technically, it’s possible to interconnect the reimplemented engine with original mods written using HLSDK, its license doesn’t explicitly forbids to do that, but that’s at your own risk. And only for non-commercial use. The game dlls compiled from the HLSDK code will still be licensed under terms of Half-Life SDK License, I can only permit to link the GPL3 OGS code with them as a special exception

Q: Can I use the HLSDK to create a mod for this engine?
A: Nope, HLSDK EULA expects that any modification created using it will be used only by the original GoldSrc engine. You need to reimplement the game code yourself or use the reimplemented OGS SDK template game code based on Quake’s QC progs code (if it’s present at the time you reading this, I’m not planning to reimplement the game code for this engine for now, can’t say for sure, but I doubt that anyone else decides to rewrite the game code for this engine, so it probably end up being used as a tech demo of the GoldSrc showcasing its features using some recreated HL Alpha maps)

Downloading Unreal Engine Source Code

Steps for connecting to the source code repository and downloading the latest build of Unreal Engine.

Choose your operating system: