Hi and thank you for the Dialogue System.
I have mapped the interact button and the continue button to the E key and gamepad south. They seem to work fine but when the conversation ends it begins again immediately I think they are both being registered at the same time.
The continue button works fine when using the mouse to press it but not with the E key, i think maybe I've implemented the new input system incorrectly?
Possible to map interact button to the same key as continue button?
Possible to map interact button to the same key as continue button?
- Attachments
-
- ds3.png (91.89 KiB) Viewed 344 times
-
- ds22.png (158.28 KiB) Viewed 344 times
-
- dsunity.png (128.87 KiB) Viewed 344 times
Re: Possible to map interact button to the same key as continue button?
Hi,
Tick the Dialogue System Trigger's Actions > Start Conversation > Prevent Restart On Same Frame Ended.
Tick the Dialogue System Trigger's Actions > Start Conversation > Prevent Restart On Same Frame Ended.
Re: Possible to map interact button to the same key as continue button?
Hey thank you so much for your response! The prevent restart on same frame ended was indeed unchecked so thank you for pointing that out, however I'm still having the same issue for some reason.
Pressing the continue button with the mouse ends the conversation just fine also if i hold down the continue button using the keyboard or gamepad it ends fine too, it's just when i tap the continue button on the keyboard or gamepad that it restarts.
Pressing the continue button with the mouse ends the conversation just fine also if i hold down the continue button using the keyboard or gamepad it ends fine too, it's just when i tap the continue button on the keyboard or gamepad that it restarts.
Re: Possible to map interact button to the same key as continue button?
I wonder if this is an Input System issue or maybe another bug in the Input System. Here are two options on what to do from there:
1. As a test, temporarily switch to Unity's built-in input manager and see if the problem is still present. If not, then it probably has something to do with the Input System.
2. Or send a reproduction project to tony (at) pixelcrushers.com. I can try to reproduce the issue and see if I can figure out what's going on.
1. As a test, temporarily switch to Unity's built-in input manager and see if the problem is still present. If not, then it probably has something to do with the Input System.
2. Or send a reproduction project to tony (at) pixelcrushers.com. I can try to reproduce the issue and see if I can figure out what's going on.