05-10-2020, 08:38 AM
(This post was last modified: 05-10-2020, 08:45 AM by josemendez.)
(05-10-2020, 08:20 AM)mr-matt Wrote: Issue resolve by adding OBI_ONI_SUPPORTED custom define to Super Unity Build. I think maybe it clears the defines set manually in the Unity settings?
OBI_ONI_SUPPORTED is automatically re-added to the defines list if not present every time the editor is started. So it really should be there.
Code:
foreach(var group in supportedBuildTargetGroups)
{
var defines = GetDefinesList(group);
if (!defines.Contains("OBI_ONI_SUPPORTED"))
{
defines.Add("OBI_ONI_SUPPORTED");
PlayerSettings.SetScriptingDefineSymbolsForGroup(group, string.Join(";", defines.ToArray()));
}
}
In case Super Unity Build clears all defines and replaces them with its own at build time, it could explain this problem. This is quite a risky operation though as it can inadvertently break a lot of stuff, IMHO the appropriate thing to do by a build system would be to append defines to existing ones at build time instead of replacing them, or at least let the user choose between append/replace. Glad you resolved it!