Hi, is compatibility with upcoming 2019.3 alpha being addressed as GUIText and GUITexture are being completely removed from Unity? 

If I remove the actions that cause errors in unity and comment out the offending lines in ComponentAction.CS I still get these errors when building in Xcode:

// UnityEngine.GUITexture PlayMakerFSM::get_GuiTexture()
IL2CPP_EXTERN_C IL2CPP_METHOD_ATTR GUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51 * PlayMakerFSM_get_GuiTexture_mF9CCD9D13099FA16165DADB957F89C7CD79BC62C (PlayMakerFSM_tF3B356F82C78D795D28F7E8FA6AD435FA9B0D235 * __this, const RuntimeMethod* method)
{
static bool s_Il2CppMethodInitialized;
if (!s_Il2CppMethodInitialized)
{
il2cpp_codegen_initialize_method (PlayMakerFSM_get_GuiTexture_mF9CCD9D13099FA16165DADB957F89C7CD79BC62C_MetadataUsageId);
s_Il2CppMethodInitialized = true;
}
{
GUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51 * L_0 = __this->get__guiTexture_13();
IL2CPP_RUNTIME_CLASS_INIT(Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0_il2cpp_TypeInfo_var);
bool L_1 = Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C(L_0, (Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 *)NULL, /*hidden argument*/NULL);
if (!L_1)
{
goto IL_001a;
}
}
{
GUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51 * L_2 = Component_GetComponent_TisGUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51_m640D83B27C9B1652475EAF178394548BE687AF16(__this, /*hidden argument*/Component_GetComponent_TisGUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51_m640D83B27C9B1652475EAF178394548BE687AF16_RuntimeMethod_var);
__this->set__guiTexture_13(L_2);
}

IL_001a:
{
GUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51 * L_3 = __this->get__guiTexture_13();
return L_3;
}
}
/Users/christopherrichardson/UnityProjects/Just Popping Bubbles/iosBuild/Classes/Native/PlayMaker2.cpp:33160:15: No matching function for call to 'Object_op_Inequality_m31EF58E217E8F4BDD3E409DEF79E1AEE95874FC1'

I appreciate your thorough responses, and I would love to solve everything by breaking the prefab relationship, however that causes problems with the CoreGamekit plugin with the new prefab workflow as the prefab connection is required... Maybe I'll just hook up some global variables but I'd really like an option to forgo fsm changes from breaking the prefab connection without my permission.

Hi, I'm having problems working with a gameobject that needs to retain its relationship with the prefab, but every time I mess with an FSM in playmaker disables the connection. can I disable this behavior?

Looking forward to it!  yes, I'm using a navmesh agent and have a rigidbody as well.  I've tried setting the navmesh agent's updateposition to false and applying force and seem to get inconsistent results...  sometimes it works perfect, sometimes it doesn't seem to click... so, looking forward to seeing it.

It would be amazing if we could drag a bunch of gameobjects onto a field and have it be populated into an array variable or arraymaker proxy.  Like for reals!  Dragging in like 50 game objects one at a time is tedious and prone to error.
Chris

they do, i asked and was told they'd help but also wanted to ask here.  I also was hoping there is a simple way to get static variables as this isn't the first time I've ran into this problem.  Is a generic GetStaticBool or GetStaticInt not possible?
Thx.
Chris

Hi, sorry for necroposting.  I'm interested in looking at your logic for this if you still have it and are willing to share.  I'm happy to host it on dropbox for others as well... I've just cleared out like 4 GB's of space...  obviously it's outdated and no pressure to update anything.  I still have Unity 4 installed.  Feel free to PM me.
Thx,
Chris