Dialogue System for Unity 2.1.5 Released

[Tony Li]

Version 2.1.5 is now available on the Unity Asset Store.

Release Notes:

Core:

• Changed: OnConversationLineCancelled now passes PC line, not previous NPC line, if PC line is what was cancelled.
• Added: Sequencer command SetDialoguePanel(true|false).
• Added: Only For PC continue button option.
• Improved: StandardUIQuestTracker inspector now has Clear PlayerPrefs Visibility Toggle button.
• Improved: Added Use PlayOneShot option to typewriter effects.
• Fixed: Chat Mapper XML export format incorrectly exported Dialogue Text field as Localization type instead of Text type.
• Fixed: UIPanel NullReferenceException if scene didn’t have an EventSystem.
• Fixed: Fade() sequencer command sets alpha to fully 1 or 0 at end to avoid floating point rounding errors.
• Fixed: ProximitySelector gracefully handles usables in range that have been destroyed or deactivated when choosing a new usable.
• Fixed: Rare error message with some complex sequences.
• Fixed: Lasso selection auto arrange no longer also arranges unconnected red nodes unless they're part of selection.

Third Party Support:

• articy:draft: Can now choose to name elements by technical name; jumps that link only to other jumps or hubs are now converted as group nodes; more gracefully handles XML file inconsistencies.
• i2 Localization: Added option to append actor name or dialogue text to dialogue entry terms.
• Opsive Controllers: Converse ability can now use different states based on whether player is using mouse or not.
• PlayMaker: Added Sync GameObject. Updated actions for .NET4.
• SLATE: Added pause and resume parameters.
• uSurvival: Updated for version 1.43.

[hellwalker]

EDIT: It was Odin + DS. Strange. Updating and reimporting both DS and Odin fixed the problem. I'll leave the post in case anyone else ran into this.

I'm experiencing a very weird problem on unity 2017.4.24f(same on 23f) windows 10. with a specific project. Basically, when I build the game and run it, it usually runs the first time but subsequent runs it will 95% freeze on launch and show up as "not responding" window. If I delete DS from my project and build the problem is gone. The scene I'm building is completely blank unity scene.
If I upgrade the project to unity 2018 or if I import DS into a new project on unity 2017 the build will launch 100% of the time.
So it's likely some combination of my project settings and DS, or DS and other plugins.
I'm deleting other stuff form my project one by one to see what combination is causing the problem, but I just wanted to ask meanwhile if something similar has been reported or maybe you have an idea what in DS could be conflicting?