Page 1 of 1
Errors when enabling Assembly Definitions and Third Party Dialogue / Quest Machine support
Posted: Sat Sep 24, 2022 9:20 pm
by mroshaw
Hello!
I'm trying to setup Assembly Definitions in my project.
I've imported the Quest Machine, Dialogue System, and PixelCrushers assembly definitions. However, I'm getting a load of console errors related to the third party support scripts. For example:
Code: Select all
Assets\Plugins\Pixel Crushers\Quest Machine\Third Party Support\Dialogue System Support\Scripts\Sequencer Commands\SequencerCommandSpawner.cs(15,44): error CS0246: The type or namespace name 'SequencerCommand' could not be found (are you missing a using directive or an assembly reference?)
Assets\Plugins\Pixel Crushers\Quest Machine\Third Party Support\Dialogue System Support\Scripts\Quest Actions\StartConversationQuestAction.cs(16,10): error CS0246: The type or namespace name 'ConversationPopup' could not be found (are you missing a using directive or an assembly reference?)
Assets\Plugins\Pixel Crushers\Quest Machine\Third Party Support\Dialogue System Support\Scripts\Bridge\DialogueSystemQuestMachineBridge.cs(19,30): error CS0246: The type or namespace name 'CommonLibraryLua' could not be found (are you missing a using directive or an assembly reference?)
Any ideas how to resolve this?
Thanks again!
Re: Errors when enabling Assembly Definitions and Third Party Dialogue / Quest Machine support
Posted: Sat Sep 24, 2022 10:03 pm
by Tony Li
Hi,
Create an asmdef in Assets\Plugins\Pixel Crushers\Quest Machine\Third Party Support\Dialogue System Support\Scripts and add references to the PixelCrushers, DialogueSystem, and QuestMachine asmdefs (and also the Unity.TextMeshPro asmdef if you're using TextMesh Pro).
Re: Errors when enabling Assembly Definitions and Third Party Dialogue / Quest Machine support
Posted: Sun Sep 25, 2022 5:27 am
by mroshaw
Of course, thank you! I was so busy with this yesterday, I didn't see what was obvious! Amazing, that works!
I'm just left with to errors, this time from the Invector Support scripts. Not sure if this is something you can help me with, or if I need to go to Invector support? These are the two errors I have:
Code: Select all
Assets\Pixel Crushers\Common\Third Party Support\Invector Support\Scripts\InvectorInventorySaver.cs(122,41): error CS1061: 'vItemManager' does not contain a definition for 'temporarilyIgnoreItemAnimation' and no accessible extension method 'temporarilyIgnoreItemAnimation' accepting a first argument of type 'vItemManager' could be found (are you missing a using directive or an assembly reference?)
Assets\Pixel Crushers\Common\Third Party Support\Invector Support\Scripts\InvectorStatsSaver.cs(72,53): error CS1061: 'vThirdPersonMotor' does not contain a definition for 'currentStaminaRecoveryDelay' and no accessible extension method 'currentStaminaRecoveryDelay' accepting a first argument of type 'vThirdPersonMotor' could be found (are you missing a using directive or an assembly reference?)
If this is an Invector issue, please do let me know and I'll take it up with them.
Thank you so much again!
Re: Errors when enabling Assembly Definitions and Third Party Dialogue / Quest Machine support
Posted: Sun Sep 25, 2022 10:09 am
by mroshaw
Hi!
So, it looks like Invector have made some changes since the integration was created. There are a number of properties in vMotor that are private. I edited the scripts, made them public, and everything is working great.
I've got to say, I wish EVERY asset author followed your example of optionally enabling Assembly Definitions. Absolutely brilliant, as usual!
Thanks again1
Re: Errors when enabling Assembly Definitions and Third Party Dialogue / Quest Machine support
Posted: Sun Sep 25, 2022 3:39 pm
by Tony Li
Hi,
Thanks!
Have you imported the latest Invector Support packages from these folders in the latest version of the Dialogue System?
Plugins/Pixel Crushers/Common/Third Party Support
Plugins/Pixel Crushers/Dialogue System/Third Party Support
I think the integrations are up-to-date with the latest Invector.