feat: vanilla ts example for wind prediction #35
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This branch is a simple example of how to do wind predictions from an embedded view. * get desired position using `Forma.designTool.getPoint()` * Generate height maps using raycasting in `generateHeightMaps` * Perform predition using `Forma.predictiveAnalysis.predictWind` * Draw results to scene using `Forma.terrain.groundTexture.add` I've done simple sanity check of comparing this approach with the one done by the built in feature, but make no promises that I've included the exact same geometry in the height map.
knut-sverdrup-adsk
approved these changes
Feb 27, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch is a simple example of how to do wind predictions from an embedded view.
Forma.designTool.getPoint()generateHeightMapsForma.predictiveAnalysis.predictWindForma.terrain.groundTexture.addI've done simple sanity check of comparing this approach with the one done by the built in feature, but make no promises that I've included the exact same geometry in the height map.
This codebase to the left. Native feature to right:
Note that there is expected to be slight differences as the height map generation technique is different, and the extension texture does not look as crisp.