In addition to that article making me realize what Tirex feels like when he tries to read my posts, I think the process would be far too CPU intensive. It's pointless for models, as any such movement has to be worked into the model. It'd be more useful for map objects, maybe add some sort of func_fabric map entity, but doing movement relative calculations for so many vertexes in real time would seriously swamp the client or server. It'd be quite a stunt to make sure it, at least, only did the calculations when the client was in sight (as mappers know, func_water, which is the closest thing to it, doesn't work well in that regard either, and its movement is considerably simpler). The article is a nice theory, but I doubt he ever tried it in practice.
I've the Spirit of Half-life source, been trying to figure which entities would be best to attempt to add first.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.