Building with exclusive nativization fails

Development Platform & Builds Mobile
, , , , ,
1

I tried using exclusive nativization with FirstPersonCharacter BP being nativized and build failed, development and release (and release for distribution).

Here is the output: Google Drive: Sign-in

I was building for Android / Gear VR.

EDIT: Tried dev build with Inclusive nativization - same story. Here is the log:

Does it have anything to do with FMOD ?

2

Hello motorsep,

My first suggestion would be that it could be related to FMOD. I tried doing the same thing (packaging Gear VR for Development in the FirstPersonCharacterBP with Inclusive on) and didn’t get any errors or warnings. Could you attempt packaging without FMOD so that we could narrow it down if that is the cause?

3

I’ll try, but I’d probably have to dig into my project and remove all FMOD BP nodes (otherwise building with FMOD disabled will fail).

I suspect that building stock templates will always pass as templates have no interfaces and no dispatchers.

Nativization actually used to work for me in 4.14.x (inclusive)

4

Were you ever able to try removing FMOD to see if it was the problem?

5

Unfortunately I got entangled with release build for distribution bug and haven’t been able to completely get a rid of FMOD. I’ll probably have new report for you using 4.16 since that’s what’s going to be released soon anyway. I’ll change version to 4.16 once I have results.

6

Oculus confirmed the issue is with FMOD not “wanting” to be nativized. Is it something you guys can fix or have FMOD team fix it on their side? Maybe alternatively have an option to not nativize plugins ?

7

I can’t be sure without knowing the exact reasons for it, but I would assume that this would need to be fixed on FMOD’s side. As for an option to not nativize plugins, would you like to me to enter a feature request for that functionality?

8

Yes please, such functionality would be very welcomed!

9

I’ve placed a feature request in for the ability to decide if plugins should be nativized or not. It was entered under the number UE-45880. In the meantime, this seems like something that will need to be fixed with FMOD itself so that it can be nativized.