Sledge: Difference between revisions
(badly moved multipage rest of page history at Archived Page History/Sledge/en) |
mNo edit summary |
||
Line 35: | Line 35: | ||
*It was built using modern frameworks and libraries and is tested on modern operating systems. | *It was built using modern frameworks and libraries and is tested on modern operating systems. | ||
*It was constantly being enhanced and new features are always being added. | *It was constantly being enhanced and new features are always being added. | ||
*It is open source, | *It is open source, meaning the source code is available to everybody to modify or improve. | ||
**Even though it is no longer being actively developed, its source code is available | |||
== Features == | == Features == | ||
Line 49: | Line 50: | ||
* Displays models from unextracted PAK files | * Displays models from unextracted PAK files | ||
* Improved texture browser filtering and display options during its lifetime | * Improved texture browser filtering and display options during its lifetime | ||
=== Possibilities suggested during lifetime === | === Possibilities suggested during lifetime === | ||
{{Note|Sledge is no longer being actively developed, however, some features were planned before shutting down}} | {{Note|Sledge is no longer being actively developed, however, some features were planned before shutting down}} | ||
When a map is compiled, | When a map is compiled, certain features would be converted to {{goldsrc|3.1}} compatible brushwork. | ||
Some popular ideas included the following: | Some popular ideas included the following: | ||
*Collaborative editing and multi-user support | *Collaborative editing and multi-user support | ||
*A plugin system | *A plugin system with support for scripting | ||
*Built-in support for version control systems like SVN | *Built-in support for version control systems like SVN or Git | ||
* | *Displacement editing tools | ||
*A complete 'Sledge SDK' containing other editing and creation tools based on the Sledge code base...and anything else you can think of! | *A complete 'Sledge SDK' containing other editing and creation tools based on the Sledge code base...and anything else you can think of! | ||
* Model loading | |||
* Cordon clipping during compile | |||
* Support for prefabs/instances | |||
* Automatic detection of game configurations | |||
== Source Support == | == Source Support == | ||
Line 75: | Line 71: | ||
{{Note|Sledge is no longer being actively developed, however, its 2.0 version was planned to have Source compatibility}} | {{Note|Sledge is no longer being actively developed, however, its 2.0 version was planned to have Source compatibility}} | ||
The current milestone | The current milestone was to fully support {{goldsrc|3.1}} editing. Once the alpha test is complete, work to add support for Source would have likely begun. Full Source support was expected to be released in version 2, but official development was discontinued. So it's unlikely that it would be added in the future. | ||
Many Source editing features will be available in Goldsource as well, such as displacements and instances. | Many Source editing features will be available in Goldsource as well, such as displacements and instances. | ||
Revision as of 14:05, 13 August 2024


![]() | |
---|---|
![]() | |
Type | Open source Third Party Tool |
Engine | ![]() |

Sledge may still be occasionally useful for generating certain geometry with its advanced primitives, but should not be used as one's primary map editor.
Sledge was a free and open source level editor that supports the
GoldSrc engine.
The original scope of Sledge was to offer advanced editing features from later versions of Hammer and other editors and make them available to all users, regardless of which engine they choose to use.
Sledge uses the same file formats as Hammer does (RMF, MAP, VMF) and maps are compatible between both programs. The editing process is almost identical to Hammer, the hotkeys are the same, as well as many of the screen elements and dialogs. Switching to Sledge will not be difficult for users who are familiar with Hammer.
Requirements

Minimum | Recommended | |
---|---|---|
Operating system (OS) | ![]() |
![]() |
Processor (CPU) | 2.0 GHz dual-core processor | N/A |
System memory (RAM) | 2048MB | 4906MB |
Hard disk drive (HDD/SSD) | 5GB* | 10GB* |
Video card (GPU) | OpenGL-compatible graphics card | OpenGL-compatible graphics card |
Other | .NET Framework 4.0 |
Advantages
- Sledge included many editing features available in
Hammer 4.x in the GoldSrc editing environment.
- It was built using modern frameworks and libraries and is tested on modern operating systems.
- It was constantly being enhanced and new features are always being added.
- It is open source, meaning the source code is available to everybody to modify or improve.
- Even though it is no longer being actively developed, its source code is available
Features
- Runs on modern operating systems and graphics cards
- Full support for GoldSrc editing
- Capable of Reading and writing RMF, MAP, VMF files, as well as its own SMF format.

- Complete compatibility with Hammer maps
- Proper decimal precision for sub-grid geometry
- Support for larger maps
- Support for multiple visgroups per object
- Automatic visgrouping
- Displays models from unextracted PAK files
- Improved texture browser filtering and display options during its lifetime
Possibilities suggested during lifetime

When a map is compiled, certain features would be converted to GoldSrc compatible brushwork. Some popular ideas included the following:
- Collaborative editing and multi-user support
- A plugin system with support for scripting
- Built-in support for version control systems like SVN or Git
- Displacement editing tools
- A complete 'Sledge SDK' containing other editing and creation tools based on the Sledge code base...and anything else you can think of!
- Model loading
- Cordon clipping during compile
- Support for prefabs/instances
- Automatic detection of game configurations
Source Support

The current milestone was to fully support GoldSrc editing. Once the alpha test is complete, work to add support for Source would have likely begun. Full Source support was expected to be released in version 2, but official development was discontinued. So it's unlikely that it would be added in the future. Many Source editing features will be available in Goldsource as well, such as displacements and instances.
Media
External links
- Website at GitHub
- GitHub Repository
- HammerTime (active development fork) at GitHub
|
|