Snarkpit Forum Index » Source engine editing » CS:S - bookcases missing vphysics models
CS:S - bookcases missing vphysics models
1
Post Reply
Quote
 Re: CS:S - bookcases missing vphysics models
Posted by RealEschaton on Wed Jan 12th at 10:33pm 2005

I'm working on a CS:S map based on a local library, so it's probably obvious that bookcases would be necessary. For some strange reason, both bookcase_large and bookcase_small are missing their vphysics models:

SOLID_VPHYSICS static prop with no vphysics model! (models/props/cs_havana/bookcase_small.mdl)
SOLID_VPHYSICS static prop with no vphysics model! (models/props/cs_havana/bookcase_large.mdl)

Those are the warnings reported when the level loads (though there are actually about a half dozen of each right now).

I have checked the official maps that came with CS:S, and the ones that have bookcases have them functioning perfectly. For example, the bookcases in de_chateau seem to have their vphysics intact. When I shoot them, the bullets hit in the correct spot and the bullet hole is the correct material, indicating that they didn't simply use a prop_dynamic_ornamental and place a clip brush around it.

Anyone else have this problem? Any solution to it?





Quote
 Re: CS:S - bookcases missing vphysics models
Posted by Grash on Wed Jan 12th at 10:44pm 2005

if you can find the collision models for the models, your best bet is to create an invisble phy boxs for each item. Give each phys box will need a name so you can then parent them to the prop you are using.

Not the best Solution, but it should work.
(If it doesn't someone please tell me)





Quote
 Re: CS:S - bookcases missing vphysics models
Posted by Leperous on Wed Jan 12th at 10:56pm 2005

If you want to find out what prop_ they used, type impulse 106 into the console when looking at it (with cheats enabled), or if that fails try surfaceprop.



Quote
 Re: CS:S - bookcases missing vphysics models
Posted by RealEschaton on Wed Jan 12th at 11:16pm 2005

Well, I don't really know how to find their collision models, and it seems like an awfully large amount of work to individually name and tie together all the bookcases in a library.

Except for impulse 101, I've never gotten any of the impulse commands to work for me (yes, I did enable sv_cheats). I used Lep's suggestion of the surfaceprop command, and it looks like the models in de_chateau are the same ones I'm using in my map. Since the models are not stored in the map, it really boggles my mind that the engine would be able to find them for one map and unable to find them for another.





Quote
 Re: CS:S - bookcases missing vphysics models
Posted by DjBourgeoisie on Wed Jan 12th at 11:24pm 2005

just go to its props and select not solid for vphysics. Then all you have to do is put a clip brush over the model.



Quote
 Re: CS:S - bookcases missing vphysics models
Posted by RealEschaton on Thu Jan 13th at 12:08am 2005

? quoting DjBourgeoisie
just go to its props and select not solid for vphysics. Then all you have to do is put a clip brush over the model.

If I did this, players would be able to shoot through it. In addition to stopping bullets though, I would like the bookcases to get punctured in the right places when shot, and consist of the right materials for when players shoot them or walk on top of them. These properties are displayed by the bookcases in the official maps.





Quote
 Re: CS:S - bookcases missing vphysics models
Posted by Leperous on Thu Jan 13th at 10:17am 2005

There's nothing you can do about it except placing some invisible wood brushes in the same place as the prop (using render modes etc. a la HL1)



Quote
 Re: CS:S - bookcases missing vphysics models
Posted by RealEschaton on Thu Jan 13th at 10:19pm 2005

I'm hoping this is an issue that will be dealt with by Valve at some point. For now, I'm just going to abandon this map until a quick solution surfaces. It would be very annoying to spend a ton of time fine-tuning an invisible brush system or tying invisible physboxes to everything, only to have an update fix the whole problem. It really seems like this is something that should not be broken and while I appreciate your suggestions I'm not interested in using a sub-optimal solution.




1
Post Reply