Use final value instead of value to reflect automation in get_parameters - #442
Open
Claers wants to merge 1 commit into
Open
Use final value instead of value to reflect automation in get_parameters#442Claers wants to merge 1 commit into
Claers wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When updating a parameter in FMOD (for example to have a timing for the engine to prepare an event) the actual code is using
valuebut in FMOD Engine value is the value that is set by the user and does not reflect actual value changes made by FMOD itself.This pull request change this by using final_value instead of value. This should not break things bc it's a voluntary action to change a value into FMOD and want to gather it into the engine.