Jump to content

Search the Community

Showing results for tags 'vsm'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Web Gaming Standards
    • Coding and Game Design
    • Paid Promotion (Buy Banner)
  • Frameworks
    • Pixi.js
    • Phaser 3
    • Phaser 2
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
    • GameMonetize
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered
    • Marketplace (Sell Apps, Websites, Games)

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 1 result

  1. When looking up all the great things that Varaince Shadow Maps can achive I was wondering which downsides are comming with VSM. And well... it seems to have some light bleeding, other than that I wasnt able to find anything in my research. So I was wondering. Does the depth percission decreese with VSM? Because we are storing depth and depth squared but have the same amout of bits as oposed to only store the depth, which means we store our values with less precision, correct? I know that when checking for shadows in VSM its not just comparing two depth values (I am honest and tell you, I couldnt fully understand the whole math going on with vsm ) but it still seems to me, that the more bits available to store the values, the better?! Would be cool if someone could enlighten me here ; )
  • Create New...