Implements support for MotionBuilder 2023 #28
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
|
FYI, I wasn't able to compile a working plugin using a source build of UE 5.3.1 using your changes as-is. However, I was able to compile a build for MotionBuilder 2023 using a source build of UE 4.27, reverting back to the 2.5.0 release tag and simply cherry-picking this commit to add the build and target files. I used this youtube video as a reference for compiling UE 4.27 on Windows 11, as there were some issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello!
Those changes implement Build and Target for MotionBuilder 2023.
I've tested compiled binaries in MotionBuilder 2023 and with Unreal Engine 5