I had this problem crop up in my WAR-Dune map also and could never, for the life of me, fix it.
In Dune it was more of a cosmetic issue, but in my new map, it's seriously effecting the gameplay.
I had perfect collision on one of my palm tree models, it was simple but it worked fine. I just had one issue where in the Generic Browser, it kept telling me that I had "25 COLLISION PRIMS!" and it was rather annoying to see... plus I wasn't sure if that would cause optimization issues later on. So, I created a simple box collision out of a builder brush, then saved the brush as collision.
Now, the engine recognizes that there IS collision on the meshes, but paths build right through the trees and you can walk/drive right through them.
If I hit the "C" key in the editor to view collision, no collision box comes up and I am very very confused. I tried deleting and re-importing the mesh and adding collision, but the editor just refuses to allow this one mesh to have collision of any sort, It does block weapons, but nothing else.
In Dune it was more of a cosmetic issue, but in my new map, it's seriously effecting the gameplay.
I had perfect collision on one of my palm tree models, it was simple but it worked fine. I just had one issue where in the Generic Browser, it kept telling me that I had "25 COLLISION PRIMS!" and it was rather annoying to see... plus I wasn't sure if that would cause optimization issues later on. So, I created a simple box collision out of a builder brush, then saved the brush as collision.
Now, the engine recognizes that there IS collision on the meshes, but paths build right through the trees and you can walk/drive right through them.
If I hit the "C" key in the editor to view collision, no collision box comes up and I am very very confused. I tried deleting and re-importing the mesh and adding collision, but the editor just refuses to allow this one mesh to have collision of any sort, It does block weapons, but nothing else.
Comment