Controller Issues

[Chibi310]

So am I the only experiencing this. But, I play the game using an X-Box Series X controller, and it seems like the game can't figure out if I'm using an X-Box controller or a DualShock. Is there any way for me to manually force it to stay in DirectX mode?

Normally I'd just ignore it. But this constantly causes my Psionic Abilities to fail or not work at all, or just straight up drop the LT/Strong Psychokinesis abilities mid go. And this seems tied to my Analog Trigger inputs. Anything else functions flawlessly, except for when using LT/L2 and RT/R2.

No, Steam Controller settings has no effect on the game. No, I don't have any weird drivers or 3rd party software running on my computer. No, I'm not using any 3rd Party Controllers. No, I don't have a DualShock or a DualSense controller paired up to my computer. No, there isn't anything funny in the background. It's just 1 Controller, my X-Box Series X controller paired up to the USB X-Box Controller Dongle.

[Chibi310]

Originally posted by Dr. Dro:

If you're sure you don't have any other peripheral connected, flight stick, wheel etc. - and that Steam controller settings are off, this shouldn't happen. Why are you using the dongle anyhow? The Series controller has bluetooth support, might be double inputting because of that?

Alright cool lemme just check my non-existent extra peripherals here... Mouse, Keyboard, and XSX controller... Nope, don't see anything extra.

And how could they be double inputting, I've never heard of a controller simultaneously connecting to more than one input sensor. The only device I know of that connects to more than one sensor at once are smartphones and Wi-Fi Antennas.

And the Dongle is more reliable than BlueTooth for XSX controllers. Less problems than with Bluetooth which has a tendency to drop connections randomly.

[Rin]

The dongle is just a cheap BT dongle for those who lack native BT support from their laptop/motherboard. And since it's USB connected it can drop out for various reasons unlike mPCie cards. Not to mention having worse performance overall for obvious reasons.

Either way, what you're experiencing is either Steam (controller settings) or Windows related due to some software issue or both. No one here is a mind reader (to popular belief). First figure out if PEBCAK isn't the issue then move on from there.

[Chibi310]

Originally posted by Bork Bork:

The dongle is just a cheap BT dongle for those who lack native BT support from their laptop/motherboard. And since it's USB connected it can drop out for various reasons unlike mPCie cards. Not to mention having worse performance overall for obvious reasons.

Either way, what you're experiencing is either Steam (controller settings) or Windows related due to some software issue or both. No one here is a mind reader (to popular belief). First figure out if PEBCAK isn't the issue then move on from there.

Never expected anyone to be a mind reader, the comment clearly ignored the final paragraph. I'm aware of the problems others are experiencing which is why I said that:
-I have Steam Controller Settings disabled as much as possible. Which should've ruled out steam, unless there's some secret setting I'm not aware of that someone else is.
-I do not use 3rd party, or odd drivers like DS3/4, which should've hinted at a fresh install with no odd quarks.
-No Strange or off-brand controllers (i.e. Steering Wheel or HOTAS)
-No DualShock or DualSense that could possibly interfere with the game, as this one seems to be the most common issue/cause found online.
-Nothing strange in the background like a Streaming program or JoytoKey converter or anything that could possibly cause an error in reading the controller.

The Dongle uses a custom RF signal, it's not Bluetooth. I'm an EE and I can assure you, Bluetooth is complete garbage. It's good for convenience sake, but I wouldn't trust it with low-latency jobs. As for what signal the Adapter uses, I don't know the exact specs myself, I haven't bothered to actually take my scope onto it yet, but if it was Bluetooth then 1st generation X-Box One controllers (The ones without the Headphone Jack at the bottom of the controller) should be able to connect via bluetooth (Which they can't). If you need further convincing, the Bluetooth specification is one of the weakest of the 2.4Ghz Protocols, letting it get easily overpowered by other near-by 2.4Ghz signals (I.E. Wi-Fi in the 2.4Ghz band, a Microwave, or other 2.4Ghz sources like an RC Car controller). The X-Box One and Series X controllers use a custom 5Ghz Band Protocol which is what the Adapter uses. The 5Ghz Band offer supreme signal strength, bandwidth, and latency when compared to Bluetooth and other 2.4Ghz bands. The only advantage 2.4Ghz has over 5Ghz is that 2.4Ghz can propagate through walls easier than 5Ghz and has slightly better range. But Wireless technical specifications is neither here nor there.

So, with respect. Are there any possibilities that could hint at the issue at hand? Anyone else having problems similar to mine with similar configurations. Or anyone experienced it too and have figured it out. Possibly a Mod that fixes the issue (that I haven't yet found).

Windows is reporting that there is only one controller connected to my computer. And it's the one that I'm using, the Series X controller. And again, ALL steam settings (except for the Steam Controller because it's mandatory) are turned off.

[Chibi310]

Originally posted by Dr. Dro:

The next step is double checking all your HID devices and/or macro software looking for anything that uses directinput

All clear there too. Don't really use Macros. Though I did think my keyboard management might've been a problem too. Uninstalled those and the problem still persisted.

[Bread]

Have you updated controllers firmware?

There's Xbox Accessories app in microsoft store that lets you update your controller.
Try it. It fixed my controllers random disconnects.

[Chibi310]

Originally posted by Tislez:

Have you updated controllers firmware?

There's Xbox Accessories app in microsoft store that lets you update your controller.
Try it. It fixed my controllers random disconnects.

No random disconnects ever. Firmware's also upto date. The problem seems to be with how SN processes the triggers. As it's only with the triggers, it just flickers between Playstation and X-Box controls, and just decides to lock up and deny me access to the psychic abilities. All other actions function as intended.

And this problem is exclusive to Scarlet Nexus, every other game in my library that supports controller functions without a hitch.

[Chibi310]

Originally posted by Dr. Dro:

I use a DualSense (so basically unsupported controller) with DS4Windows in exclusive mode (xbox 360 pad simulation), and it goes without a hitch

I think the game's supposed to support the dualsense/shock controllers on PC Nativly, but the devs screwed up the controller programming. Because searching online I'm not the only one with this problem. And the symptoms are the same as mine, the Analog Triggers are the problems. So it's definitely an internal problem with the game. So it might or might not work on other systems.

It's like they wanted to implement Dualsense support, but also wanted XInput in the game Ored the input coding with no regards to actually checking what controller is being used and assumed that internally the Dualsense/shock and X-Box controllers would report analog input the same. Causing the game's own internal system to get confused and lock up since it can't tell what it should actually be using. I know that the X-Box controllers (at least the older drivers) has the analog sticks share the same axis in software. But I don't think Playstation operates the same (It's been a while since I looked into controller programming).

I dunno, I think it's probably best for me to just call Namco support to get an answer to this issue.

[C]

I have the same problem as you with Logitech F310. What I did was disable vjoy and it works perfectly, no more switching between ps and xbox prompts. Not sure if it will work on your case though.

[Chibi310]

Originally posted by C:

I have the same problem as you with Logitech F310. What I did was disable vjoy and it works perfectly, no more switching between ps and xbox prompts. Not sure if it will work on your case though.

Negative. I'm using the built in drivers of Windows. I don't have vJoy installed on my computer.

[spiken0]

Can you try settings from this video? It works for me.
https://www.youtube.com/watch?v=rnmVt1zfSC8

[Chibi310]

Originally posted by spiken0:

Can you try settings from this video? It works for me.

There's nothing wrong with the controller, it works flawlessly in every single game I play. This bug is exclusive to Scarlet Nexus. Controller works as intended in any game I try, be it Nier, Resident Evil, DMC, Metal Gear, etc.

Scarlet Nexus is the only one that has the problems. It seems to be with how the game is trying to support DualShock/Sense controllers natively, so it's getting confused somewhere in the code.

[spiken0]

Originally posted by Chibi310:

Originally posted by spiken0:

Can you try settings from this video? It works for me.

There's nothing wrong with the controller, it works flawlessly in every single game I play. This bug is exclusive to Scarlet Nexus. Controller works as intended in any game I try, be it Nier, Resident Evil, DMC, Metal Gear, etc.

Scarlet Nexus is the only one that has the problems. It seems to be with how the game is trying to support DualShock/Sense controllers natively, so it's getting confused somewhere in the code.

I have the same issue and the settings from this video resolved the problem.

[Chibi310]

Originally posted by spiken0:

Originally posted by Chibi310:

There's nothing wrong with the controller, it works flawlessly in every single game I play. This bug is exclusive to Scarlet Nexus. Controller works as intended in any game I try, be it Nier, Resident Evil, DMC, Metal Gear, etc.

Scarlet Nexus is the only one that has the problems. It seems to be with how the game is trying to support DualShock/Sense controllers natively, so it's getting confused somewhere in the code.

I have the same issue and the settings from this video resolved the problem.

I'll try em out later when I have the time then. See if that works.