Skip to content
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.

Coverage or Distance for swithing threshold? #1

Open
takahirox opened this issue Nov 1, 2022 · 0 comments
Open

Coverage or Distance for swithing threshold? #1

takahirox opened this issue Nov 1, 2022 · 0 comments

Comments

@takahirox
Copy link
Owner

takahirox commented Nov 1, 2022

Currently the extension allows to define screen coverage to determine the LOD switching threashold. Another option may be distance from the camera.

The both have Pros and Cons. Which one should be used?

Screen coverage

  • Pros: Better quality. For example if an application scales up a distant model and the model will be more visible, higher LOD level will be selected.
  • Cons: Harder to compute. Because the computing needs some dependencies eg. camera info, world scale, geometry (bounding box) size. And screen coverage of a model needs to be dynamically re-computed if camera parameter or model's world matrix is updated.

Distance Pros and Cons

  • Pros: Easier to compute. No dependencies needed unlike screen coverage computing. And no dynamically recomputing is needed.
  • Cons: Worse quality. For example even if an application scales up a distant model and the model will be more visible, lower LOD level will still be selected. Then it will end up that the model will be noticable with low quality model.

I may prefer distance because of easiness? But not sure if all the major engines support distance based threashold. (I feel screen coverage based threashold is more standard now?)

@takahirox takahirox changed the title Coverage or Distance? Coverage or Distance for swithing threshold? Nov 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant