Jump to content

Search the Community

Showing results for tags 'autolod improvement'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Skype


Location


Interests

Found 1 result

  1. Hi. Would it be possible to add a special case for AutoLOD method when quality will be set to zero? As addLODLevel is not working properly for imported meshes (complex meshes extracted from GLTF files) and instances. For this reason, I am thinking to return to autoLOD method. This was working properly. In fact my goal is by now just hide very small meshes the problem is that if you specify zero quality in autoLOD method the decimation process takes a lot. Maybe would be a good idea for this case return a null mesh, this would be immediate. COuld anyone explain me how to modify the code to add this special case? Maybe the async decimation process should have an extra distance to be specified to return null mesh. This would be very useful to hide small meshes or very far away. Of course the first priority should be to return add this LOD null mesh and after the others. In fact in addLODLevel method you have this option, but when I try to use it it doesn't work properly. Does it make sense for you? Best regards
×
×
  • Create New...