Hammer Check For Problems Dialog: Difference between revisions
Jump to navigation
Jump to search
Erik Johnson (talk | contribs) No edit summary |
m (fixed titles, links) |
||
| Line 1: | Line 1: | ||
[[Category:Level Design]] | [[Category:Level Design]] | ||
=Check for problems | =Check for problems Shortcut: ALT+P= | ||
[[Image:hammer checkforproblemsdialog.jpg]] | [[Image:hammer checkforproblemsdialog.jpg]] | ||
| Line 8: | Line 8: | ||
When you select one of the errors, the entity/solid will be highlighted (if applicable) and three options become available to you. | When you select one of the errors, the entity/solid will be highlighted (if applicable) and three options become available to you. | ||
=Go to error= | ==Go to error== | ||
This button will center the 2D windows on the selected error object. | This button will center the 2D windows on the selected error object. | ||
=Fix= | ==Fix== | ||
This button will attempt to fix the currently selected error. | This button will attempt to fix the currently selected error. | ||
=Fix all (of type)= | ==Fix all (of type)== | ||
Selected this button will fix all errors of the selected type. | Selected this button will fix all errors of the selected type. | ||
| Line 22: | Line 22: | ||
'''Note:''' The '''Check for Problems''' command looks for errors in unmodified, supported game types (Half-Life 2 , Counter-Strike, etc). If you are creating maps for a proprietary game with your own game code and .FGD, some or all of the errors generated by this command may not be applicable. | '''Note:''' The '''Check for Problems''' command looks for errors in unmodified, supported game types (Half-Life 2 , Counter-Strike, etc). If you are creating maps for a proprietary game with your own game code and .FGD, some or all of the errors generated by this command may not be applicable. | ||
=Some common errors that may occur in your maps...= | ==Some common errors that may occur in your maps...== | ||
{| | {| | ||
| Line 31: | Line 31: | ||
| <code>Entity (entity_name) has unused keyvalues.</code> || The entity contains keyvalues (variables) that are not used in its class. You can fix this error with the Fix button. Note that this error will pop up if you are taking advantage of custom compile tools which add keyvalues to entities, but you are not using an FGD file that has these special keyvalues listed. | | <code>Entity (entity_name) has unused keyvalues.</code> || The entity contains keyvalues (variables) that are not used in its class. You can fix this error with the Fix button. Note that this error will pop up if you are taking advantage of custom compile tools which add keyvalues to entities, but you are not using an FGD file that has these special keyvalues listed. | ||
|- | |- | ||
| <code>There is no player start.</code> || There is no info_player_start entity in the map, or the start point was embedded in a solid object. This error could also occur if you are using the | | <code>There is no player start.</code> || There is no info_player_start entity in the map, or the start point was embedded in a solid object. This error could also occur if you are using the [[Hammer_Using_Cordon|Edit Cordon Bounds]] tool, and the player start entity was not inside the cordon area marked. If no player start point was created, use the [[Hammer Entity Tool|Entity Tool]] to create one. | ||
|} | |} | ||
==See Also== | |||
[[Optimizing and Checking Your Map]] | |||
[[Controlling Geometry Visibility and Compile Times]] | |||
[[Compile Errors]] | |||
[[Troubleshooting Level Design]] | |||
Revision as of 02:41, 9 August 2005
Check for problems Shortcut: ALT+P
Opening this dialog will cause Hammer to run through your map and notify you of any errors it finds.
When you select one of the errors, the entity/solid will be highlighted (if applicable) and three options become available to you.
Go to error
This button will center the 2D windows on the selected error object.
Fix
This button will attempt to fix the currently selected error.
Fix all (of type)
Selected this button will fix all errors of the selected type.
Note: The Check for Problems command looks for errors in unmodified, supported game types (Half-Life 2 , Counter-Strike, etc). If you are creating maps for a proprietary game with your own game code and .FGD, some or all of the errors generated by this command may not be applicable.
Some common errors that may occur in your maps...
Invalid solid structure |
The solid has invalid structure, probably as a result of vertex manipulation. What this means is that the solid is not convex in every plane. You will need to either fix it, or if this is not possible, rebuild it. |
Solid Entity (entity_name) is empty. |
This solid-entity contains no solids. Fixing the error deletes the entity. |
Entity (entity_name) has unused keyvalues. |
The entity contains keyvalues (variables) that are not used in its class. You can fix this error with the Fix button. Note that this error will pop up if you are taking advantage of custom compile tools which add keyvalues to entities, but you are not using an FGD file that has these special keyvalues listed. |
There is no player start. |
There is no info_player_start entity in the map, or the start point was embedded in a solid object. This error could also occur if you are using the Edit Cordon Bounds tool, and the player start entity was not inside the cordon area marked. If no player start point was created, use the Entity Tool to create one. |
See Also
Optimizing and Checking Your Map