Pixel Crushers Forum

Now that I've made a break, I built and output the game I'm creating, but I'm having trouble because the dialog system's mouse click behavior has changed.
It uses ProximitySelector to go in front of the other person and have a conversation. It works fine with a keyboard or gamepad, but when using a mouse, the following behavior occurs.

-If you talk by left clicking the mouse, the conversation will be displayed while you press it. Release the left click to end the conversation.
-If you press the left mouse button while talking with something other than the mouse, the conversation will end. It ends even if you press and hold it for a long time.

On an unbuilt editor, the mouse behaves the same as a keyboard or gamepad.
Is there something I should do in advance to prevent the mouse behavior from becoming strange even after building?

Hi,

There shouldn't be any difference in this regard between the Unity editor's play mode and a build.

Try playing in the Unity editor's play mode from the first scene in build settings. Maybe a Dialogue Manager GameObject in an earlier scene is configured differently.

Hello.
I thought something was wrong with my environment, so I built a sample, but it worked fine, so I think it was the part I modified that was causing the problem. However, I don't know the cause.

I tried playing the scene set to build number 0 in the editor, but unlike after the build, it was working without any problems.
What should I see?
Should I look at the contents of "Hierarchy" to see the different configurations?

Hi,

Temporarily set the Dialogue Manager's Other Settings > Debug Level to Info. Then make a Development Build.

Play the build, reproduce the issue, and then examine the Player.log file for any errors or warnings.

I created a Development Build with Debug Level to Info.
In this mode, if an error occurs, a console should appear at the bottom left, but it doesn't.
So, it looks like there are no errors at the moment.
Should I open the editor log and check?


When I run it on the unity editor, only one warning appears, but could this be the problem?
Although it seems unrelated to this issue, I will paste a warning message.

-Dialogue System: Another conversation is already active. Not starting 'Dialogue Lecture02'.

Because I set the conversation start button and conversation continuation button to be the same, I think the warning is being displayed because the conversation start process runs when I talk to Dialogue Lecture02 and continue the conversation.

Check the Player.log file for warnings. If that doesn't help, feel free to send a reproduction project to tony (at) pixelcrushers.com with instructions on how to reproduce the issue.

I checked the Player's text data in "\Users\user\AppData\LocalLow\company\game", but it's a little difficult to decipher it myself, so I would like to send the data.
However, the data is mixed in with seat licenses and other data that cannot be handed over to others, so I will organize the data.
Therefore, please wait for a while.

Hello.
We have just sent you a data link via Support Contact Us, so please check it out.

Thanks for sending the data link. I've downloaded the file. I'll try to get back to you by end of day tomorrow with an answer.

Hi,

Your input system actions are configured to send the message "OnClick". In builds, it sends OnClick to the dialogue UI with this info:
(In the Unity editor's play mode, it sends the OnClick message to a different GameObject, so it's just luck that it works in play mode.)

Your input system should not send the message OnClick. The dialogue UI has an OnClick() method, and the OnClick message is calling it, causing it to end the conversation.