Jump to content
Dr.ParadoX

ERROR Model attempted to load one or more VMT's it can't find.

Recommended Posts

My guess is you have flipped normals. In Blender go into edit mode, select all faces and press Ctrl+N. This will automatically orientate the selected faces and should fix the problem.

The reason why you can't go into your pipe is the collision model. As you can see in your compile logs on the first page, the model compiler just creates one convex part. Holes are a bit tricky because they usually get covered and you have to make it clear for the compiler not to do that. Maybe I know a solution, but I have to do some testing first.

Share this post


Link to post
Share on other sites
On 11/4/2018 at 8:32 PM, Dr.ParadoX said:

Right now I would like to make it possible to go in the pipe. I loaded the pipe into HLMV and it showed that the physics mesh ''closed'' up the holes. Why? How do I fix this?

for the collision mesh to work properly you have to make each piece of the collision into a separate convex piece, and ideally with smooth shading as well, but I'm not 100% sure about that.

convexhull.jpg.236a114fd052de86b170d87af29d7b15.jpg

make sure you don't merge the verts since all the pieces need to be separate.

and you should probably simplify it as well and use less pieces if possible, collisions can easily get complex.

Edited by tomm

Share this post


Link to post
Share on other sites
8 hours ago, tomm said:

ideally with smooth shading as well, but I'm not 100% sure about that.

I can confirm.

Share this post


Link to post
Share on other sites

Yeah, you have to smooth shade them individually before grouping them together. Otherwise it'll again end up as a convex collision after exporting/compiling.

Share this post


Link to post
Share on other sites

I managed to fix the pipe so that it is no longer hallow (thanks for that). But the physics mesh still closes up both ends of the pipe!

Screenshot (65).png

Screenshot (64).png

How do I tell the compiler to recognize holes? 

Share this post


Link to post
Share on other sites
4 hours ago, Dr.ParadoX said:

How do I tell the compiler to recognize holes?

You shouldn't have to. Can you post a screenshot of your physics model in blender?

Share this post


Link to post
Share on other sites
3 hours ago, esspho said:

It looks like you didn't smoothshade the individual parts before joining them together.

They should look like thissmooth.PNG.54bd64921926ea044f977f4b002ef2b0.PNG

On the original I did smoothshade them. Just I didnt save the original... 

Share this post


Link to post
Share on other sites

I would like to thank all the participants for assisting me in this matter. Your help has been ivaluable. I now have a working pipe. Thank you all for your cooperation. I will not forget this... 

Turns out the last bit didnt work because I messed up. But I managed to fix it. And now my pipe works just fine! Thanks everyone! 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • MapCore on Discord

  • Our picks

    • Post in [decompiled] dz_blacksite
      Alright, I did some testing with the new detail sprites and found out how more specifically how they work. @Mamorex was on the right track but there's a few key things you left out. 

      Removing $alphatest from the material or adding $translucent

      First, the detail sprites material - it's 2 detail sprite sheets side by side, so version A and version B. The different versions have to have same sprite positions and sizes. You only specify version A coordinates in the .vbsp.


      Next up, the detail sprites masks. Red and blue are for wind offset -- so you can have different parts of the sprites sway in the wind differently, you can see Valve isolated some blades of grass for this effect. The green channel is a tint mask and controls how much the sprites are affected by the $worldspacetint. 

      That brings us to the world space textures. They seem to automatically get resized to fit the whole map area, so it you resize the map you'd have to resize the textures too.

      The world space tint texture is pretty self explanatory, controls what color to tint the grass, 127 grey means no tint. 

      The world space masks texture uses the red channel to select which version of the sprites to use -- 0 is version A and anything more is version B. 

      The green channel of the texture controls the sprite size -- 127 is default, with darker making the sprites smaller and brighter making the sprites larger. The vmt command $minimumspritesize controls the cutoff point for the sprites, so the sprites smaller than the specified value don't get rendered which can act as a placement mask. 

      I don't know what the blue channel of this texture does, changing it had no effect on the sprites for me. 

       

      All this means sprites still get placed by vbsp on map compile, so they still use displacement alpha for the placement, but the new masks can manipulate sprites size and color after map compile.


       

       
  • Articles (view all)

×