-
Notifications
You must be signed in to change notification settings - Fork 3
Common Problems
"The engine drop-down is blank or missing entries! I can't find the game I want to run PackBsp for!"
Your Source SDK configuration may be corrupt or incomplete. This must be fixed before PackBSP (or most official SDK tools) can run.
- Try briefly starting up the game that is missing.
- Try using the
Refresh SDK Contentoption from the Source SDK launcher.
If you are able to start the Hammer editor for a game, but cannot do the same for PackBsp, please file a bug report.
“I try to pick the steam directory, and it says that clientregistry.blob is being used by another process!”
Steam is probably in the middle of reconfiguring itself somehow, such as with an update to the Steam platform or to a game.
- Please wait for the update to finish, and try again.
- If it still does not work, restart Steam.
If problems persist please file a bug report.
"PackBsp isn’t automatically finding a certain dependency in my map, I keep needing to add it manually."
Please file a bug report, explaining the dependency which is missing and what chain of relationships pulls it in. For example, you may have a prop_static in your map that has a custom model, that model may have a custom skin, and that skin-material may have a custom texture, but the texture isn't being seen.
PackBsp does not support dependencies which may be triggered by the I/O system in Hammer, since it is difficult to analyze and predict what it may do. The env_projectedtexture entity relies on the I/O system to set the texture that it must use. Please inspect your map logic to determine what file(s) are needed, and add them manually.
“I have some map logic which the model that a prop shows, but when I trigger it the new model is missing.”
PackBsp does not support dependencies which may be triggered by the I/O system in Hammer, since it is difficult to analyze and predict what it may do. Please inspect your map logic to determine what file(s) are needed, and add them manually.