It would be nice to directly call a second conversation device from an event within a conversation device.
As well as pull the speakers image from a conversation device into a widget by using view bindings.
See video
Creative
Assets
See video
See video
See video
windows
Another feature that would be nice is a way to tell which node will be called first, second, third, etc. Much like the AI nodes in UE.
I’ve found that if we call the HUD Message device from an Event within a Convorsation tree, the HUD Message device will do it’s thing, BUT it will override the Conversation.
It would be nice to be able to add a HUD element to the screen at the same time as the conversation is in progress.
Not finding any difference between the Conversation Ended and Conversation Canceled when the player presses ESC or the end of the conversation tree is reached.
Expected result:
On Conversation Ended would fire when the player reaches the end of a conversation by reaching the last speech node, and/or event node.
On Conversation Canceled: would fire when the player presses ESC to jump out of the conversation, Exit Conversation event is called, and/or Exit All Conversations event is called.
Most of the issues that I was experiencing were addressed in the long run. This was done by calling the Enable and Disable Events in the Conversation Banks AND by calling Disable from Conversation Devices that were being used closer to the root of the conversation tree.
Note that during this exercise I was avoiding using Verse, for reasons I won’t get into here. That said, by using verse to change the speakers name (and potentially the speakers image in the future), it becomes unnecessary to many (in this case 4) different Conversation Devices and Conversation Banks to achieve the desired experience.
I’m looking forward to seeing how this device and its use cases grow in the future.
Some more feature requests and workflow thoughts live from my brain.
Feature Request:
Priority setting
Use case:
Combining a priority setting with the enable and disable events of conversation devices, could allow designers to set up which conversation device would be initiated when talking to an NPC. This would work well for simple interactions with 3-5 conversation devices associated with a single NPC.
