Propper is an edited version of vbsp that outputs a model instead of a bsp.
Many mappers need to make props for their maps, but don't want to learn a separate modeling program. This tool allows them to make models in Hammer in a one-step process. It's also useful to modelers who work with mappers. No other method of .vmf export keeps texture mapping intact, or auto-generates a physics mesh.
- Can create static props or physics props
- Generates a .qc file and automatically compiles the prop for use in your game.
- Generates a working physics mesh.
- Automatic material conversion--Turns map textures into valid model textures.
- Distinguishes between real textures and "tool" textures.
- Respects Hammer smoothing groups or autosmooth.
- Configure your prop from within Hammer.
- Displacement support--outputs any displacement surface you can make (not solid).
- skins support--use multiple textures on the same prop.
Future planned features
- Output multiple models out of one map
- Automatic culling of invisible faces
- Breakable models with custom gib creation.
- LOD support.
A public beta release is now available! http://crazycarl.hl2sm.com/files/propper_0.22.zip
There are two versions of propper included. One is for the Episode 1 SDK, and the other is for the Orange Box SDK. A .fgd (Forge Game Data) file is included for both, to help you configure your props.
The folders in this ZIP file mirror the folders in the SDK. For best results, unzip the file to your steamapps\<username> folder, and let your zip utility keep directories intact.
After installing, you should change your game configuration a bit. Open Hammer under the game with which you will use Propper, and click Tools:Options.
Find the section for "Game Data Files", and click the "Add" button. Open propper.fgd when prompted (It will be right there if you installed correctly). Then Click OK or Apply to save the settings. Finally, restart Hammer so the settings take effect.
IMPORTANT: propper.fgd should be below your game's fgd in the list. If Hammer tries to load propper.fgd first, it will give you error messages.
Making a prop
To use Propper, copy some geometry from your map and paste it into a new Hammer file. There are three included entities. The first, info_prop_options, is required for your prop to compile correctly.
Place one in the map and look at its properties:
|Name||The name that other entities refer to this entity by. (not used by propper)|
|Origin (X Y Z)||The position of this entity's center in the world. Rotating entities typically rotate around their origin.|
|Model Name||The directory and name of the finished model. Relative to <yourmod>/models|
|Material path||Where the model's textures will be. Relative to <yourmod>/materials. Make sure this folder exists before running!|
|Scale||Scale the model up or down by this factor.|
|Surface property||The physical properties of the model--affects impact sounds and weight for physics props.|
|Concave collisions||Used to make a concave collision model. If you choose no, the model will be 'shrink-wrapped'.|
|Produce collisions?||Picking Yes allows the prop to be solid.|
|Smoothing mode||Determines how vertex normals are computed for lighting.|
|Source folder||Where you want to keep your .qc and .smd files. The final directory will be <sourcefolder>/<modelname>. Make sure this folder exists before running!|
|Smoothing threshold||If auto-smooth is enabled, Edges flatter than this angle will appear smooth. Pick from 0 to 180.|
|Snap to Hammer||Causes every vertex to be snapped to the nearest grid point.|
|Welding threshold||Vertices will be snapped together if within this tolerance. A value of 0 is not recommended because there may be visible gaps in the mesh. Larger numbers will merge vertices together, and may be useful for optimizing your model.|
|Model Origin||The model's origin point defines how it is lit and is how the prop is positioned in a map. Auto-center puts the model's origin at the center of its bounding box and is recommended for physics props. For static props, put the origin somewhere that lets you align the prop easily.|
|Automatically compile||By default, propper will run studiomdl to compile the prop. You can disable this.|
|Fix up materials||By default, propper will make a copy of any material used in the prop and make it valid for use on a model. You can disable this.|
|Don't warp displacement textures||In Hammer, when you move a displacement point, the texture moves with it. If you pick yes, the texture stay in place.|
You run Propper just like vbsp. Pass it the current game directory and your vmf file.
propper.exe -game D:\Steam\SteamApps\SourceMods\FortressForever C:\Users\Carl\Desktop\testmap.vmf
Propper will compile the model automatically unless you disable that function.
You can run Propper from within Hammer. Just create a new Run configuration and run propper instead of vbsp.
You should now have a new prop available to you! If you are replacing an existing model, you may have to restart Hammer to see the changes.
There's also the info_prop_physics entity. If you place this entity in your map, Propper will produce a physics prop. See Prop data for documentation on the following.
|Name||The name that other entities refer to this entity by. (not used by propper)|
|Origin (X Y Z)||The position of this entity's center in the world. Rotating entities typically rotate around their origin. (not used by propper)|
|Health preset||Dictates how strong the prop is vs. different weapons.|
|Health||Overrides the prop's health. Setting this to 0 will make the prop unbreakable. -1 will use the default value from "Health preset"(recommended).|
|Mass||Weight of the prop in kg. Enter zero or lower to automatically calculate mass.|
|Flammable||Will it burn? Picking this enables the 'ignite' options.|
|Ignite at half-health||Just like those barrels in HL2.|
|Ignite from explosions||Won't break right away if something explodes near it, but will ignite.|
|Explode damage||Damage to do when breaking|
|Explode radius||Radius of explosion|
|Gibs||Generic shards to spawn when the prop breaks|
|Gib count||How many gibs?|
|Gib skin||Which skin to use on the gib models, if applicable.|
New in version 0.22 is propper_skins. Propper can create alternate skins by replacing a texture that is on your prop. If you have multiple textures on your model that you want to change, you can use this entity more than once.
|Name||The name that other entities refer to this entity by. This is not used, but will be in the future.|
|Material||Pick a texture that's present in the original model. This will be skin 0.|
|Skin(1-14)||This texture will replace the original when you pick skin #.|
- I can't find these prefabs I've heard about. Where are they?
Propper no longer includes any prefabs for the config entities. You should use the entity tool and find info_prop_options in the list of entities.
- I can't find the new entities/the fgd won't work
propper.fgd needs to go after your game's fgd in the list of "Game Data Files". Some users have gotten success by editing propper.fgd: add this line at the beginning of the file:
- My prop's collisions are wrong. It's solid where it shouldn't be.
The source engine likes collsion models to be very simple. Once you go above 40 or so brushes, it starts to merge brushes together. Make your prop's collision mesh as simple as you can. It may be best to make your visible model a func_detail, and then make a simple collision model on top of that, out of nodraw brushes.
- I made a large building into a model and the lighting is not as good as a brush model. What gives?
Models in Source use rather simple vertex lighting, whereas brushes get radiosity lightmaps. What that means in simple terms is your map gets nice soft shadows and bounced light, but props don't. Buildings just look better when they're made from brushes.
- Propper quits with an error saying it can't open such-and-such file.
Usually this is a result of the EP1 version of Propper trying to write to a folder that doesn't exist. The OB version has no problem creating these folders. So browse to the folder mentioned in the error message and make sure it's there.
It might also be that the file exists, but is write-protected. Make sure it's not open in another program, and it's not set to read-only.
- Why would I want to make a prop anyway?
It's also not uncommon for mappers to run into the brush/face/plane limits for a very large or detailed map. Props let you add detail to your map without pushing this limit. If a feature is used several times in a map, making it a prop will reduce the size of the .bsp and the system memory needed to run the map.
Models can be smaller and more precise than the stuff you make in Hammer. Plus there is the fun stuff Propper lets you do with physics models.
- Hammer's a mapping tool! People who want to make models should learn a real modeling program like Blender or XSI.
I agree, but maybe they don't want to...
- The EP1 version of the tool won't create the folders it needs, and will quit if you don't make them beforehand. So make them beforehand.
- If you run the tool on a map with no brushes (displacements don't count), Propper will crash. This is an obscure bug from vbsp and I haven't managed to track it down yet. If you encounter this bug, just stick a nodraw, func_detailed brush in the map.
- If you include propper_skins and don't use all 14 available slots, Propper will create a model with 14 skins anyway; the extras will be Source's default pink checkerboard texture.
- You can use visgroups to hide brushes; They will be ignored by Propper.
- If you make any brushes func_detail, they will be non-solid in the finished prop. Using any other entity seems to cause problems, however.
- If you use certain invisible textures (eg. clip, nodraw, sky), on a face, that face will be solid, but invisible. This is useful when creating a physics mesh.
- When creating the collision mesh for a model, you are limited to about fourty brushes. After that you will begin to see errors. For very complex models, it's best to make a very simple version of your prop to act as the physical model.
- As always, it's better to use as few brushes as possible, and use nodraw wherever you can.
- Hammer limits you to its one-unit grid while you work. However, you can make your model at a larger scale--say, 16:1--and then tell Propper to scale it down to the correct size. That would allow you to model objects as small as 1/16 inch. (You can also resize brushes within Hammer itself, as always.)
- Don't set "materialpath" to the same folder as any of your map textures. The model materials may overwrite your map materials! It's best to follow the convention of putting model textures under "models\"
- Propper will over-write files without asking, so make sure there are no files in your selected folders that you don't want to lose.
Left 4 Dead
Propper doesn't currently support Left 4 Dead. If you are mapping for L4D, you can try the following:
- Extract the materials (vmt and vtf files) you want to use from L4D using Gibbeds_VPK_Extractor and mirror them in an Orange Box game that you own (such as Episode 2).
- Run Propper from the Source SDK as normal.
- Take the files created by Propper and copy them into your L4D folder.
Source Code Patches
The source code for Propper is available as a patch to Valve's SDK code. (Since Propper is a hacked version of vbsp.exe, I don't want to release the entire code--most of it belongs to Valve).
First create a new mod through the Source SDK (either OrangeBox or Ep1). Find the project for vbsp. Visual C++ Express 2008 can compile this project with no problems. If you select the "Release" version, you will create a new vbsp.exe.
Then download one of my patch files:
http://crazycarl.hl2sm.com/files/vbsptopropper_b22_OB.patch for Orange box, or
http://crazycarl.hl2sm.com/files/vbsptopropper_b22_EP1.patch for EP1.
Follow these instructions for Setting up Tortoise SVN to apply a Patch, substituting the vbsp folder for the game code. Your vbsp source code is now the source code for Propper. Edit and compile it as you wish.
This program has been used with some success by community mappers. It's based on vbsp, which we all know and trust not to destroy our PCs. That said, use at your own risk. I claim no responsibility for damage to your computer of games that may occur while using Propper.
Some tutorials have been made to help with using Propper.