Platform: PlayStation 4
Issue Type: Gameplay
Game Mode: Single Player
Server Type: PvP
Map: Exiled Lands
Server Name: Grape Jelly
Bug Description:
With the construction hammer equipped and in hand, the scrolling of the crafting menu is unresponsive when scrolling down. Appears as scrolling UP with L1 is triggered on the leading edge of L1, while R1 only recognized the input when done fairly fast and is ignored with a casual press and release of R1.
Bug Reproduction:
Easy to reproduce, just equip the construction hammer and try navigating the crafting menus.
Greetings JamCar!
Thank you for reaching out to us.
Could you record a video where we can see both the game and the buttons of your controller being used, so that we can properly observe the issue occuring please? You can upload the video in a platform (such as youtube for example) and send us the link.
Additionally, is this only happening in your Conan Exiles game or in other games as well?
Have to say no to the video since I don’t know how to do that.
Try this with the DS4 for troubleshooting/testing purposes, press and HOLD R1 and observe behavior. Press, HOLD and release R1 and observe behavior. Repeat with different length HOLD times (0-3 sec) and observe behavior. Do this for both L1 and R1 and compare results.
It will be found L1 activates when button is initially pressed (no release) and R1 activates AFTER the button has been pressed and released relatively quick (<0.2s).
This issue is happening only in this menu of Conan. Functions as expected on other menus within Conan, such as the Knowledge Feats section. Also functions as expected outside of Conan.
I can confirm this (I have checked on the Isle of Siptah, and the behavior is exactly the same as stated by OP).
This shouldn’t normally be a problem if you just tap the buttons, however, it is conceivable that this could mess things up under certain circumstances.
From my point of view (and depending on the type of implementation) the game is either polling the wrong input key (i. e. the release of R1 in this case), or scrolling down in the list is tied to the wrong event in case input is handled on a per-event basis.
EDIT: If you are wielding the construction hammer but are not in its chooser, R1 serves a twofold purpose: Tap it to place the selected element, and hold it for longer than approx. 0.5 secs to switch to Dismantle mode (you see a cursor that is an X surrounded by a circle). In this case it actually makes sense to handle the press of R1 on its trailing edge.
Looks like this mode switch isn’t taken into account when determining how to handle a press of R1.
My suggestion would be to attach an event handler for R1 to the leading edge of its press and check whether or not the construction menu is open: If it is, handle it as usual, and if not, skip processing the press.
Then modify the event handler for the trailing edge so that it ignores the release event while it is still in the construction menu, but when it is closed, handle the event as usual.