Pixel Crushers Forum

I am porting a game from XDK to UWP and when I create a UWP VS solution and run a 'Debug - x64 - Local Machine' build I encounter this error -

AwakeFromLoadThreaded has not been called 'Text' (MonoBehaviour). Figure out where the object gets created and call AwakeFromLoadThreaded correctly.
UnityEngine.Object:DestroyImmediate(Object, Boolean)
UnityEngine.Object:DestroyImmediate(Object)
PixelCrushers.DialogueSystem.DialogueSystemController:Awake()

I am able to run Master and Release builds without crashing or slower performance . This bug will endlessly create breakpoints making it impossible for me to work in a debug environment.

When I look up the DialogueSystem.dll in unity, the Inspector shows the Information->Assembly Info: "Targets .NET 3.5" but when I build I must set the unity project 'Player Settings->Other Settings->Api Compatibility Level: ".NET 4.6" , which is required for UWP.

1.)Is this an exception being thrown that can be bypassed or turned off?

2.) Do I need to use an updated DialogueSystem.dll compatible with .NET 4.6?

3.)Has anyone encountered this error and know how I can go about correcting it?

Hi,

What version of Unity are you using?

I'll reproduce this and implement a fix, which will probably involve an updated DialogueSystem.dll that you'll simply need to import.

Hi,

We are currently running
Unity 5.6.3p3
Microsoft Visual Studio 2017 v15.4.0
Visual Studio Tools for Universal Windows App - 15.0.27004.2002
Visual Studio Tools for Unity 3.4.0.99

Also, when I look up my 'About Microsoft Visual Studio' I find -
Microsoft .NET Framework v4.7.02046

Not sure if this additional info will be helpful.

Thanks Tony!

Thanks! I'll test with those versions.

I believe I have a fix. I sent you download info for a patch. I wasn't able to test with the exact versions you specified since my Visual Studio installations are on different versions, and you probably know how difficult Visual Studio can be about changing versions. But the problem appears to be that DialogueSystemController (the main script on the Dialogue Manager) had a call to DestroyImmediate() when it should have called Destroy(). If the patch doesn't resolve the issue for you, please let me know and I'll dig into it further.