Legal & C++ Question: Including FbxImporter in a packaged game for Static Meshes Only
Dear Friends at Epic,
I am making a Make-Your-Own-Game sort of game, and I am not in any way attempting to duplicate UE4 Editor features.
I've written my entire own In-game editor.
I will not be duplicating or enabling creation of skeletal mesh assets of any kind
I would just like to be able to enable users to import static mesh geometry in FBX format for my in-game editor.
To do this, I believe I need FbxImporter.h and associated cpp files which are in the private directory of UnrealEd
What are the legal issues involved with this?
Here's the entirety of the functionality I would like to include, which I cannot do because FbxImporter.h cannot be included in my packaged game, (and does not compile in my unpackaged game)
( I am already including UnrealEd private dependency)
Would any of the below code, the UnrealEd.h and Factories.h, come along with a packaged game, or would this not work in a packaged game context?
Sorry for the delay in answer. Couple of points in response:
answered Apr 08 '14 at 02:24 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here