Mobile issue with Dialogue manager

[shammi]

Hi i have integrated UCC with Dialogue Manager, but it seems use is called when I click anywhere on the screen? so then I am unable to click on the next or any other action buttons. also the camera moves even when i use the virtual controls, how can i fix this?
on a slide note i am not sure if the issue is with dialogue manager because i use a selector component, but i think this issue is with UCC on a mobile device.

i have an android build for you to check and let me know.

HWU Cyberpunk2.apk

drive.google.com

 

[Justin]

I am unable to play your build, but what use is called? A button use? If so you will either need to disable the virtual button when dialogue is shown or make the button in a specific area.

 

[shammi]

Selector from dialogue manager. That I can disable when the conversation is on. But the issue is with the overlap when any weapon in on like combat then no matter where I click it's friring weapon. https://drive.google.com/file/d/1AkboJxMYkj8EipO9Um5154ow50XbkmtC/view?usp=drivesdk

 

[shammi]

Hi not sure if you get the issue.
I recorded a video on mobile. You see I am able to switch to combat body or flashlight but the touch on any of the virtual controls also triggering the weapon on or off or in case of combat it's punching even when my finger is on trackpad or next button.

Recorder_16102024_093139.mp4

drive.google.com

 

[Justin]

I am not familiar with the selector so this may be a misunderstanding, but you should disable the virtual control when you do not want the weapon to fire. That way it can only fire when the virtual control is enabled.

 

[shammi]

I get that. But the touch is active on virtual controls ui like the joystick which switching the flashlight on and off even when the user wants to move the character using the joystick. Have you tried on android. I don't think this is an issue with dialogue manager

 

[Justin]

I have tried the default virtual controls on mobile and didn't have any issues. I have a few questions:

1. Could it be that your use virtual control is larger than the area that it is on other platforms because of the resolution difference?
2. What does the button look like in the editor?
3. Beyond that, can you attach the debugger and set a breakpoint within Use.AbilityStarted and send the call stack? This will indicate what is starting the ability.

 

[shammi]

I did try it on its own without dependency, https://drive.google.com/file/d/1FJU5uz_OgcIPadbkxnwfHt_gmc9kQjz6/view?usp=sharing and the issue is still there on the device. investigating it further. it works in the editor because we use the mouse. but ill check the resolution and call stack

 

[Justin]

Yes, if you can answer the three questions above that will help narrow it down.