Introduction
Have you ever looked at Valve's map loading screens and can't figure out how they added those damn icons, backgrounds, and more? This article will provide some information about it.

A repository on Github that will allow you to better understand the location of the files.

Note: Text surrounded by arrows indicates what needs to be entered here. Arrows should not be written, it is only necessary for a more convenient understanding of important elements. For example, instead of <mapname>.png I will write de_dust2.png
Note: Spoiler blocks replaces code blocks

Background
The loading screen uses PNG images as background. You need to create two images, where the first image will be have resolution 640x360 and the second will be have 1920x1080. After creation, you need to put the images in these paths:

Radar
Loading screen uses default radar file. If you want to use some image instead of the radar that the player should not see on the map (for example, a screenshot of the map with heroes, as is done in some of Valve's cooperative maps), then you should use heights that will hide the unnecessary image somewhere in 32 thousand units from the zero point of the map.

In the already created TXT file of the radar, we prescribe this code that adjusts the high-altitude images:

The final version of the files needed for the radar:

The problem with vertical sections of the radar
If the sections contain the same values in AltitudeMax and AltitudeMin, then the game just crashes without any messages. The same values can only be in one of the parameters!

Problem code example:

Correct code example:

Title
I tried to find a file that regulates the names of official maps, but nothing came of it. For now, the name depends on the Steam Workshop and some sort of Valve magic file.

Map icon
The loading screen uses SVG for the map icon. Valve uses Adobe illustrator to create and export the svg.

Export your svg
You need to create a document with the resolution you want (Valve use 35x35 or 80x80), create your nice gamemode/map icon, and then save it (File > Save As) to this path:
"../Counter-Strike Global Offensive/csgo/materials/panorama/images/map_icons/map_icon_<mapname>.svg"

Settings for the Save As panel
SVG Profiles: SVG 1.1
Fonts:
• Type: SVG
• Subsetting: None (Use System Fonts)
Advanced Option:
• CSS Properties: SVG
• Decimal Places: 3
• Encoding: Unicode (UTF-8)
• Addaptive SVG / Responsive: Disabled

Description
Go to the map folder and create a blank TXT there and name it with the BSP name, for example: de_dust2.txt

Adding an official command with a list of authors
Open an TXT file and write code like this:

Using HTML syntax
You can use the html syntax without COMMUNITYMAPCREDITS, but I am giving an example with this command.

Open an TXT file and write code like this (Use HEX or RGB for colors):

Final result

Tags for search engines: Counter-Strike: Global Offensive, csgo, cs, mini-map.

Static Prop Combine in Counter-Strike: Global Offensive

A step by step guide
thanks to @untor

What is Static Prop Combine?

Static prop combine, or informally speaking "autocombine", is a new feature in CS:GO's VBSP.
It allows VBSP to merge together multiple static props into a single static prop, either automatically or with user-defined rules.

What is static prop combine good for?
Static prop combine is another feature to optimize your maps. Most people might think that "the less geometry rendered the better". So if you use small props, it's easier to hide what is not visible.
That's not wrong. But there is a problem:
In Source, there is one draw call per model per material. And these draw calls are very performance-hungry.
That's where static prop combine comes into play:
By combining models sharing the same materials, less draw calls are performed, which greatly helps optimization.
Valve has stated that Nuke runs 40% faster after they implemented static prop combine.

How do I use static prop combine?
The static prop combine feature was added in 2016 with the release of the reworked de_nuke. But since then it was not (?) used by community mappers, there are no (?) guides on the Internet except this documentation.
@untor helped me to make static prop combine feature do its job. So we decided that it's time to publish a step by step guide how to use static prop combine.

• We presuppose that you are already familiar with the creation of props

0. Backup your CS:GO folder (optional)
We do not take responsibility for any damage done to your files. So it's time to backup your game files now if you have not already. In general we recommend to duplicate your "Counter-Strike Global Offensive" folder, so you can use a separate installation of CS:GO for mapping while keeping the other one clean for playing.

1. Source files
You must have the source files of the models you want to be combined. Usually 3 files for each prop:

• *.qc
• reference mesh (supported formats are *.smd, *.dmx and *.fbx)
• physics mesh

So if you want to combine props made by you, you should already have these files.
If you want to combine props made by Valve, you will need to decompile them first. And then change the names - otherwise, the version of the prop that is packed in the VPK would overwrite your version.
    
In this guide we will use two different pipe props:

You can download the example files here (contains the *.qc and *.smd files) :

example.zip

Browse to "...\Steam\steamapps\common\content\csgo\"
Create a folder "models". In our example we have another subfolder "example". Save the model source files there:
 

These are our QCs:

pipe_straight.qc

Quote

$modelname         "props\example\pipe_straight.mdl"
$staticprop
$body "pipe_straight"    "pipe_straight_reference.smd"
$surfaceprop         "metal"
$cdmaterials         "models\props\de_nuke\hr_nuke\metal_pipe_001"
$collisionmodel     "pipe_straight_physics.smd" { $concave }
$sequence "idle"    "pipe_straight_reference.smd"

pipe_curved.qc

Quote

$modelname         "props\example\pipe_curved.mdl"
$staticprop
$body "pipe_curved"    "pipe_curved_reference.smd"
$surfaceprop         "metal"
$cdmaterials         "models\props\de_nuke\hr_nuke\metal_pipe_001"
$collisionmodel     "pipe_curved_physics.smd" { $concave }    
$sequence "idle"    "pipe_curved_reference.smd"

Notes:
Restrictions for the *.qc:

• Only the first $body is recognized.
• $model is not recognized.
• $appendsource and $addconvexsrc are not recognized.
• You can only use $upaxis Z or Y.

2. Compile your props
Your models have to be compiled from this directory now:
Open your model compile tool (I use Crowbar)
Then browse to "...\Steam\steamapps\common\content\csgo\models\example\" and compile the QCs.
The compiled model files should be in "...\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\models\props\example\" now.

3. spcombinerules.txt
Browse to "...\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\scripts\hammer\spcombinerules\"

There you will find "spcombinerules.txt". In this file the combine rules for Valves props are defined. It is a standard KeyValues-formatted text file. Each entry follows the format below.
Rename it to "spcombinerules_valve.txt" (or whatever you want) and create a new text file "spcombinerules.txt".

Then copy and paste the following into "spcombinerules.txt" and save it.

Quote

"combine rules"
{
    "pipe_combine"
    {
        // this is a stub qc that will be used to generate combined models
        "qc_template_path"    "scripts/hammer/spcombinerules/qc_templates/example/pipe_combine.qc"
        
        // max models per cluster using these peers
        "cluster_limit" 24
        
        // don't cluster models greater than this far apart
        "distance_limit" 500

        // these are models that can combine with each other
        "peers"
        {
            "models/props/example/pipe_straight.mdl" ""
            "models/props/example/pipe_curved.mdl" ""
        }
    }
}

4. Stub QCs
Stub QCs are QCs which contain a base template for the QCs which static prop combine generates. Generally, they should only include:

• $staticprop
• $surfaceprop
• $cdmaterials
• Any $texturegroups used by the models.

Browse to "...\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\scripts\hammer\spcombinerules\qc_templates\".
In our example we create a new subfolder "example", open it and then create a text file and rename it to "pipe_combine.qc":

Copy and paste the following into "pipe_combine.qc" and save it:

Quote

$staticprop
$surfaceprop     "metal"

$cdmaterials    "models\props\de_nuke\hr_nuke\metal_pipe_001\"
$texturegroup     metal_pipe
{
        { "metal_pipe_001" }
}

5. Compile your map
Add some of our example props to your map in Hammer and compile the map.
In our example we use the following compile parameters for VBSP

Quote

-staticpropcombine -staticpropcombine_mininstances 3 -keepsources -game $gamedir $path\$file

Compile parameters (full list here) :

-StaticPropCombine: Merges static props together according to the rules defined in scripts/hammer/spcombinerules/spcombinerules.txt. This lowers the number of draw calls, increasing performance. It can also be used to lower the number of static props present in a map.
-StaticPropCombine_AutoCombine: Automatically generate static prop combine rules for props that VBSP deems should be combined. Note: This does not write to spcombinerules.txt.
-StaticPropCombine_ConsiderVis: Instead of using the distance limit, combine all props in the group that share visclusters.
-StaticPropCombine_SuggestRules: Lists models sharing the same material that should be added to spcombinerules.txt.
-StaticPropCombine_MinInstances <int>: Set the minimum number of props in a combine group required to create a combined prop. Tip:Valve had this set to 3 for the new Dust 2.
-StaticPropCombine_PrintCombineRules: Confirm: Prints the combine rules?
-StaticPropCombine_ColorInstances: Instances of combined props get colored.
-KeepSources: Don't delete the autogenerated QCs and unpacked model files after finishing.
-CombineIgnore_FastReflection: Combine props, even if they have differing Render in Fast Reflections settings.
-CombineIgnore_Normals: Combine props, even if they have differing Ignore Normals settings.
-CombineIgnore_NoShadow: Combine props, even if they have differing Disable Shadows settings.
-CombineIgnore_NoVertexLighting: Combine props, even if they have differing Disable Vertex lighting settings.
-CombineIgnore_NoFlashlight: Combine props, even if they have differing Disable flashlight settings.
-CombineIgnore_NoSelfShadowing: Combine props, even if they have differing Disable Self-Shadowing settings.
-CombineIgnore_DisableShadowDepth: Combine props, even if they have differing Disable ShadowDepth settings.

6. Success?
The combined props look exactly like the single props. So how can you be sure that the static prop combine process was successful?
- Once the map is compiled, the combined props will be packed into your *.bsp automatically.
- If you add -keepsources to the compile parameters, you can also find the combined props in "...\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\models\props\autocombine\*name of your map*\"
and their QCs in "...\Steam\steamapps\common\content\csgo\models\props\autocombine\*name of your map*\".
- If you add -StaticPropCombine_ColorInstances to the compile parameters, instances of combined props are colored in CS:GO.

7. Additional notes

Hammer:

- You can manually disable static prop combine for individual props with the "Disable Prop Combine" keyvalue.
- Prop scaling (Uniform Scale Override) is not supported yet (?)
- If the original props don't have a collision model, you will have to set collisions to "Not Solid" in the properties. Otherwise the combined prop will be solid (automatically generated collision mesh; causes problems).
- If the props differ in specific keyvalues, in most cases the default (e.g. Alpha) or the higher value will be used (e.g. fade distances)
- Props that differ in the below keyvalues will NOT be combined, unless manually overridden with the appropriate VBSP option:

• Render in Fast Reflections (-combineignore_fastreflection)
• Ignore Normals (-combineignore_normals)
• Disable Shadows (-combineignore_noshadows)
• Disable Vertex lighting (-combineignore_novertexlighting)
• Disable Flashlight (-combineignore_noflashlight)
• Disable Self-Shadowing (-combineignore_noselfshadowing)
• Disable ShadowDepth (-combineignore_disableshadowdepth)

- Props that differ in the below keyvalues will NOT be combined:

• Skin
• Color
• Disable Flashlight

TO DO

• some fps tests with an actual map!
• which gives better results: " -StaticPropCombine_ConsiderVis" or prop combining based on distances?
• Is there a console command to display the number of performed draw calls/props?
• ...

______________________________________________________________________
Sources:
https://developer.valvesoftware.com/wiki/Static_Prop_Combine
https://developer.valvesoftware.com/wiki/QC
https://developer.valvesoftware.com/wiki/VBSP

Creating a custom grass variant for the Danger Zone

1. Open your GCFScape and after open pak01_dir.vpk in "Counter-Strike Global Offensive/csgo" go to "materials/hr_massive" and found there broken_road_1_4wayblend_1.vmt. Extract that file into your materials folder, for example: "../csgo/materials/my_project_folder", and rename it, example: my_custom_4wayblend_material.vmt.
    
2. Go back to pak01_dir.vpk and find the detailsprites_survival.vmt file in "materials/detail", then extract it to "../csgo/materials/detail"
   Note: Rename "detailsprites_survival.vmt", for example: "detailsprites_test.vmt".
    
3. Open the extracted file and delete the lines below to remove the texture that controls the density of the grass.

   Quote

   $worldspacetint "detail/test_massive9_grass_tint"
   $worldspacetype "detail/test_massive9_grass_type"

   
    
4. Go to "../Counter-Strike Global Offensive/csgo" and find there detail.vbsp. Open it (You can use Notepad++) and find there the cluster "survival_grass_2". Copy that and paste after that cluster, but with new name, for example: survival_grass_theowl.
   Find line (inside the cluster) "associated_material" "detail\detailsprites_survival" and replace "detail\detailsprites_survival" to your custom texture which you created recently. Example: "associated_material" "detail\detailsprites_mycustommap")
   
    
5. Inside your custom vmt file ("my_custom_4wayblend_material.vmt") you should replace %detailtype survival_grass_2 to %detailtype <your name of cluster inside detail.vbsp>", for example: %detailtype survival_grass_theowl
   

Links
• GCFScape
• VMT Editor
• Notepad++

First connection with Mapcore
Hello! On Mapcore for the first time, so I don’t know if you write something like that here. In general, I recently encountered a problem I had been thinking about for a long time, and the solution was the simplest...

4wayblend textures stumped me and I didn't understand how to work with them. Since I could not find any articles about this issue, I decided to write about them.

Connecting and using grass sprites on your map
In order for 4wayblend textures to use grass, you must write the path to these details in the Map Properties (The path you must follow is shown below).

Find the Map menu on the top panel in Hammer World Editor > Further Map Properties > Property Name Detail material file > Set the value of Detail material file to detail/detailsprites_survival.

List of Danger Zone values for Detail material file:
• detail/detailsprites_survival [dz_blacksite]
• detail/dust_massive_detail_sprites [dz_sirocco]



To set the grass to the material, use "Paint Alpha" in the Displacement settings, but be aware that the official materials are governed by a mask that will not allow you to set the grass manually, more on that in another thread.
If you are using a mask and are experiencing performance troubles due to grass, click "Invert Alpha" to remove the already placed grass.

Let's start blending
Go to the settings "Displacement" and select there "Sculpt", then find the button "Blend" and there select the desired texture.

Blending control:
• [Left mouse button] – Apply selected texture.
• [Ctrl] + [Left mouse button] – Remove selected texture.
• [Right mouse button] + Mouse movement left or right – Resize blending area.

Bug: If the camera mode in 3D view is set to "3D Shaded Textured Polygons", then you will not see the drawn part of the texture. Camera mode should be set to "3D Textured" when drawing (fixed in Hammer++).

Creating your own 4wayblend material with Danger Zone style grass →