Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

User talk:Yuuyatails

About this board

Not editable

Dualsense Haptic Feedback, Firmware Updates

2
Kelsyt (talkcontribs)

Hey,

Thanks for correcting the page on Pacific Drive regarding the DualSense. I was totally shocked when the triggers began resisting my fingers even though it was wireless. I had never heard of a game working with them via Bluetooth.

I am curious about the haptics. According to the DualSense page (which you've helped write I see, thanks again for that) haptics require a wired connection on PC.

I tried playing Pacific Drive with the wired connection, making sure to remove the Bluetooth device so it was truly wired. I didn't notice any difference regarding the vibration of the controller. Either it doesn't use haptics over wired connection or I just can't tell. I wish I could compare with a PS5 version but alas I don't have one!

Also, I wrote the lengthy bit about installing the firmware and explicitly stating why the double input was happening because I read some people complaining about it and blaming the devs of the game in the steam discussions.

On a separate note, regarding the DualSense page:

What do you think of bringing the note "Firmware Updates" around the "Use with PC platforms" area, since it mentions the firmware anyway. I think that change would help people who are new to using it with their PC's. It seems strange that it's all the way at the bottom of the page.

Thanks again for the edits.

Yuuyatails (talkcontribs)

Regarding moving the Firmware Updates to other section of the controller article, you might want to ask the senior editors on PCGamingWiki Discord server about it.

No Steam hook input in some in Atelier games

7
Enyufiro (talkcontribs)

Hi,

I noticed that you have set Steam hook input to true for Atelier Escha&Logy, Shallie and Lulua. None of these games respond to my Playstation 4 controller however, as they do not support this as far as I am aware. The way to check this if I am correct is to go to Manage>Properties>Controller on Steam. Games which do support the hook input will list "Enabled, set by developer" for Xbox controller, Playstation, Nintendo Switch and Generic controller in the "Steam input status:". Games without hook input will have those four fields empty. As you might guess, none of those three games have "Enabled, set by developer".

Overriding this globally by enabling steam input in the controller section (Steam>settings>controller) does not solve this. Although the steam input status will then say "Enabled, general setting" for that particular controller, the game will still not respond to the controller input. Atelier Rorona, a game which lists "Enabled, set by developer" does respond to my PS4 controller (and does not respond when steam input is explicitly disabled).

Are you sure that the three mentioned games do in fact support hook input?

Yuuyatails (talkcontribs)

Whoops, my apology. I had set them to 'false' just now.

What about Atelier Ayesha then?

Enyufiro (talkcontribs)

No problem, I just went through all of the ones I own:

Rorona : True Totori : True Meruru : True

Ayesha : True Escha & Logy : False Shallie : False

Sophie DX : True Firis DX : True Lydie & Suelle DX : True

Lulua : False Marie Remake : True

The reason why Ayesha differs from Escha & Logy and Shallie is most likely because of different engines being used. Also thanks for fixing the rest of my ps/generic controller mistakes.

Enyufiro (talkcontribs)

Rorona : True

Totori : True

Meruru : True

Ayesha : True

Escha & Logy : False

Shallie : False

Sophie DX : True

Firis DX : True

Lydie & Suelle DX : True

Lulua : False

Marie Remake : True

Seems like the wiki messed up the format. This should be more readable.

Aemony (talkcontribs)

Hi,

I think I can clear up some confusion here. As mentioned in the Editing guide, the Steam Hook input (legacy mode) is all about whether the rudimentary Steam Input functionality of the Steam client, the basic XInput emulator that is, can hook and manipulate the input of the game or not. Note that this parameter is not relevant at all for games that use the full Steam Input API functionality as those don't rely on the basic XInput emulator.

The only guaranteed way of testing whether Steam can hook input is to actually test it, as mentioned in the guide:

> Having a controller configured in Steam's Controller settings, launch the game and make sure that the settings profile for the controller propagates from Steam Big Picture into the game.

What this means in practice is that it requires a customized controller profile set up, e.g. one that disables a button, remaps a button, maps the analog stick to the mouse cursor, or something random like that. Once that's done, the game needs to be launched and checked if the custom controller profile is actually active and being used.

If the custom controller profile is not being used, the parameter should be set to false. If it is being used, it should be set to true.

> The way to check this if I am correct is to go to Manage>Properties>Controller on Steam. Games which do support the hook input will list "Enabled, set by developer" for Xbox controller, Playstation, Nintendo Switch and Generic controller in the "Steam input status:". Games without hook input will have those four fields empty.

I can see where the confusion there comes from, but in reality that particular configuration you're looking at doesn't really mean anything. The "Enabled, set by developer" might mean that Steam can hook the input, or it might mean the developer tried something that had no impact and never bothered to disable it since, well, it has no effect so it doesn't matter whether it's set or not.

Similarly, empty fields doesn't mean anything other than no dev having bothered checking it or does not want to forcefully enabling the functionality since there are various downsides with it such as conflicts with third-party XInput emulators and whatnot that would have affected their users.

So to recap: actually testing the game and whether Steam Input is able to manipulate input by using a custom controller profile is the only way to know for sure how to fill that parameter out.

Br,

Aemony

Enyufiro (talkcontribs)

Hi Aemony,

Thank you for taking the time to write all of this. This definitely cleared up my confusions. Just looking at what the developer has noted was sadly too good to be true.

Yuuyatails (talkcontribs)

Another thing to note; If the game is not installed from Steam, then Steam will not hook the game's input unless it is added to Steam as 'Non-Steam Games'.

There are no older topics