Turn off vertical exaggeration for some Models in the Scene

[jjhembd]

Feature

As reported by @Jean-Dum in #11936: Scene.verticalExaggeration exaggerates every Model on the screen:

Some users may want to show exaggerated terrain, but leave some models unscaled. This was the behavior of the old Globe.terrainExaggeration which has been removed since v1.116.

@Jean-Dum can you add some context about your use case for exaggerating only part of the scene? This will help us prioritize the issue.

[Jean-Dum]

Thank you for openning this issue @jjhembd
I don't really know which solution would be the best to let the user choose on which object to apply verticalExaggeration, but it could be one of those options:

• Split behaviours between two different values (for example terrainExaggeration and modelsExaggeration)
• Allow the user to deactivate verticalExagerration for a given datasource (add an option disableVerticalExaggeration to CustomDataSource)
• Allow the user to deactivate verticalExaggeration for a given model (add an option disableVerticalExaggeration to ModelGraphics)

Maybe there is another solution which could be better for everyone!

[syzdev]

Hi @jjhembd , setting exaggerated parameters for different models is an important feature. Is there a plan for the next step in addressing this issue?

[ggetz]

Hi @syzdev, we don't have a planned date for this yet

If you'd like to add more information about your use case, that may help us prioritize. If you are interesting in contributing, please let us know and we'd be happy to discuss implementation or review a PR. Thanks!

[syzdev]

@ggetz I strongly agree with the several optimization solutions listed by @Jean-Dum . Overall, there are not many use cases for this feature. In limited use cases, most users should hope that the behavior of the model and terrain should be separated. However, further, users hope to independently control the exaggeration of each model. For example, in geological analysis use cases, users want to only exaggerate the geological model while keeping other building models above the geological model unchanged.

Of course, these suggestions will cause significant changes to the feature itself, and I am also very curious about what other users use cases are. I believe that more users need to participate in the discussion regarding this issue.