Jump to content

[CS:GO] de_village (WIP)

Recommended Posts

Looks interesting! So make sure to have a good story for the map, like why and what is the terrorists blowing up. I see similar themed maps, but they're lacking exactly this

Share this post

Link to post
Share on other sites

Looks promising so far! But there are a couple of things you should change in my opinion:

- Gameplay looks really interesting. Some pretty cool angles, routes etc. But maybe it's too complex already. Don't add more routes. Try to simplify by removing what you don't need.

- Some very high shooting ranges (e.g. I1 to L15 on your overview)

- The ground has pretty much the same height level everywhere (except some ramps, bridges etc.). This makes the map look unrealistic. Add some slight height variation to make it look less flat. Preferably with displacements.

- There are many 90° angles (overview!). This looks too constructed imo and the player also has to check many corners. Try to add more diagonals. Catfood's de_ruby is a good example on how to do it right (https://steamcommunity.com/sharedfiles/filedetails/?id=1364646330&searchtext=ruby). But this requires some decent knowledge about the Source engine (func_instances, func_detail, VVIS, ...). Don't know how familiar you are with it already.

- Some areas/routes are too narrow in my opinion. For example where there are the log piles and pillars on screenshot 1

But all in all In like it. :)Keep it up!

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)