I am in the mid of setting up the new input system right now.
I am not using mouse for my game at the moment so going to set key for joystick but it complains about the mouse position.
it seems like its related to EventSystem is still trying to use "standaloneinputmodule"?
Is this because I did not override/set specific input in the InputDeviceManager? and if it is, which would it be?
1. On your EventSystem, replace the StandaloneInputModule with an InputSystemUIInputModule as the EventSystem requests.
2. Select menu item Tools > Pixel Crushers > Dialogue System > Welcome Window. Make use the USE_NEW_INPUT checkbox is ticked.
BTW, the Plugins / Pixel Crushers / Common / Documentation folder has a PDF manual for the Input Device Manager. It has a section on setting up the new Input System.
1. The "EventSystem" is instantiated with it when the conversation starts. I was looking for any code line or prefab that ConverstaionManager is using to replace as you say but no luck
2. I already did!
333.png (107.07 KiB) Viewed 708 times
3. Yup, I found it and did as it is saying the page. Still same problem..
Add an EventSystem to your scene. If your scene uses Unity UI, it should have an EventSystem.
As a safety measure, the StandardDialogueUI and StandardQuestLogWindow components have a checkbox that will automatically create an EventSystem if it's missing. But that EventSystem uses the default StandaloneInputModule. In the next update, this safety measure will check if you've enabled USE_NEW_INPUT; if so, it will set up an EventSystem with InputSystemUIInputModule instead of StandaloneInputModule. But the best way to do it is to set up the EventSystem yourself so you have control over its setup.
