Pixel Crushers Forum

Yup, the Dialogue Manager GO has the Dialogue System ink integration component (which I added).

I still get the error:

StoryException: ERROR: Missing function binding for externals: 'SetQuestState', 'ShowAlert' (ink fallbacks disabled)
Ink.Runtime.Story.Error (System.String message, System.Boolean useEndLineNumber) (at Assets/Plugins/Ink/InkLibs/InkRuntime/Story.cs:2434)

when I run, but the error persists. I checked the file for "story" that I put in the integration component - yes, it had the functions at the beginning and the fallback functions at the end... I'm wondering what could cause the functions and fallbacks to not be recognized - "disabled"??

I did load the updated DS integration file you pointed to .... I like the changes you have made (I started looking at this today since I saw the work you had been doing to improve the ability to have characters identified.... a great thing to have).

So, I guess I'm out of luck until somehow we figure out how to get functions and fallbacks to be recognized...... just wonder what on earth I can be doing wrong, since I never had this problem in the past when I spent a lot of time on functions and passing variable to behavior designer (you helped me figure that out then )

Let me know what else I might try....

Thanks,

John

John,

What version of Unity are you using?

Does the DS - Ink integration's included example scene work correctly? Or does it report the same error?

hi Tony: and thanks for the reply.

The Unity version I'm running right now with this example is 2019.2.8f1.

Yes, the error was the same with the updated integration and the example still works fine, but does give the same error....

John

p.s. I did notice that the version of Unity is a couple of releases behind... I'll tryout the 2019.2.16f1. I'll let you know if that works. If you don't hear from me, that means I had the same error.....

John,

The latest DS/Ink integration, 2020-05-09, is on the Extras page now.

See the included example scene. The 'story' button should work similarly to what you want to do in your project. Lines on the top are spoken by NPCs. Lines on the bottom are spoken by the real player (not a fake NPC-acting-as-player actor). To set it up, I set the Dialogue Manager's Subtitle Settings to: Show PC Subtitles, untick Skip PC Subtitles After Response Menu, untick Always Force Response Menu. I set the Dialogue System Ink Integration component's PC Subtitle Settings to Use Dialogue Manager Values. The example scene trims text, but you'll want to untick that option.

I tried a new project with your Unity version, Dialogue System 2.2.6, the latest Ink integration, and the 2020-05-08 DS/Ink integration package, and it didn't report the function binding error. I also tried projects with higher and lower Unity versions.

Can you send a copy of your project to tony (at) pixelcrushers.com?

Well, starting over and reloading everything and then saving and restarting from scratch seemed to solve the problem.... I have no clue what happened but it seems to be working fine now....

Thanks for your help.

John

Inkle's Unity plugin uses something called an AssetPostProcessor. It automatically detects changes to *.ink files and processes them into the JSON files that the Ink plugin (and thus the DS integration) can use. What probably happened is that the AssetPostProcessor didn't process the external function references for some reason, and from then onward it reported them missing. I wonder now if right-clicking the *.ink files and selecting Reimport would have fixed the issue.

Tony, did you manage to take a look at the actor changes, so that Ink no longer uses a generic player actor?

(John, FYI this is just a thread I made for my issue, in future you might want to make your own thread, otherwise things get confusing fast)

Hi,

jumpovertheage wrote: ↑Tue May 12, 2020 4:37 amTony, did you manage to take a look at the actor changes, so that Ink no longer uses a generic player actor?

Yes. The latest integration package on the Extras page should take care of that. See the included example scene. I changed it so it uses the real player actor, not a dummy NPC-as-player actor.

Hi Tony,

Unfortunately I think those changes break some things with the ink integration. I'm seeing that now the lines after the response are also being considered responses, which is causing more issues than in the previous version:



You can see that after I select a response another response is offered, which really should be a line from the NPC.

For now I'm going to roll back to the previous version and use actor tags to make sure the NPC portrait stays up at all times. If you can find a way to make sure the "Subtitle Panel info" checkbox "Only Show NPC Portraits" function for ink integration that would be great, but unfortunately I don't think this is heading in the right direction, and this is more of a workflow issue than a major bug.

Thanks!

Hi,

Would it be possible to send a copy of your project, or a reproduction scene/Ink story package to tony (at) pixelcrushers.com? I suspect that some combination of settings will make it work the way you want. Then again, it might be a bug or a workflow issue that I need to straighten out in the integration.