source1import
Import Source game content into Source 2 (by kristiker)
srctools
Modules for working with Valve's Source Engine file formats. (by TeamSpen210)
source1import | srctools | |
---|---|---|
1 | 1 | |
61 | 50 | |
- | - | |
5.8 | 9.3 | |
4 months ago | 6 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
source1import
Posts with mentions or reviews of source1import.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-03.
-
CS2 Hammer porting maps from CSGO to CS2. Only wait for official launch for all assets.
If your map contains custom models are not in the base game (this means you created, imported or downloaded from any else), you need sure to use source1import or recompile the model from scratch to new Source 2 models and textures with the new tools and add to custom addons folder.
srctools
Posts with mentions or reviews of srctools.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Need help understanding VMFs
The way it works is that the vertexes in the file may not necessarily be any vertexes on the brush themselves (though hammer does seem to have them match). As you kinda guessed, the three points define a plane for each face. Edges and vertexes are then produced by intersecting all the planes with each other - 3 would define a point. This is why you can't have concave brushes and why there's the vertex drifting when saving weird geo. It's quite awkward to obtain vertexes, but it does allow very easy collision checking - simply check if your point is behind all the planes, and if so it's inside the brush. There's some more documentation on the VDC. If it helps, I have some mostly functional Python code here decoding out the vertexes of a brush.
What are some alternatives?
When comparing source1import and srctools you can also consider the following projects:
CS-GO-Auto-Radar - Add your stuff to a visgroup named 'tar_layout', and Auto Radar will do the rest. [UnavailableForLegalReasons - Repository access blocked]
SFM-Asset-Browser - Issue tracker & source code for my SFM asset browser script
bsp_tool - Python library for analysing .bsp files