Assembly Definition CustomLuaFunctionInfo Problems

[DarkProphet]

I've just been integrating the Assembly Definitions into my pipeline, but I have a last Error I can't get rid of:

Assets/Plugins/Pixel Crushers/Dialogue System/Wrappers/Editor/CustomLuaFunctionInfo.cs(13,71): error CS0234: The type or namespace name 'CustomLuaFunctionInfo' does not exist in the namespace 'PixelCrushers.DialogueSystem' (are you missing an assembly reference?)

Not sure how to fix this.

[Tony Li]

Hi,

Are you using an older version of the Dialogue System? Can you please:

1. Back up your project.

2. Delete both instances of CustomLuaFunctionInfo.cs in your project. (There are 2 files with this name.)

3. Import the current DS version.

Then try again.

If that doesn't fix it, delete Plugins/Pixel Crushers/Dialogue System then import the current DS version.

[DarkProphet]

Thanks!

I removed and re-installed the latest DS (Version 2.2.50.1.) No Lua errors now, however, I'm getting Cinemachine Errors like this:

Assets/Plugins/Pixel Crushers/Dialogue System/Scripts/Options/Cinemachine/Sequencer Commands/SequencerCommandCinemachineTarget.cs(4,7): error CS0246: The type or namespace name 'Cinemachine' could not be found (are you missing a using directive or an assembly reference?)

Unity.Cinemachine and Unity.Cinemachine.Editor is present in all four PixelCrushers and DialogueSystem asmdefs, just to be safe. The error persists. Looks like there is some broken references to the old non-native Cinemachine system in the scripts? See image attached. I tried updating them to use Unity.Cinemachine, that fixes the redlines but introduces a host of reference errors inside the scripts (such as to the old vCam class).

using Errors

Screenshot 2025-02-01 at 19.10.26.png (36.11 KiB) Viewed 1155 times

[Tony Li]

Hi,

If you’re using Cinemachine 2, define USE_CINEMACHINE and not USE_CINEMACHINE_3. If you’re using 3, do the opposite.

[DarkProphet]

Thanks Tony!

Always there when I need ya <3

[Tony Li]

Glad to help!