Controller Not An Option In Config

[Zuhan]

I finished Re;Birth 1 with my PS5 controller, granted I had to continually go into the Neptune.ini and change it up a bit before I launched the game every time. I can't find where the .ini file is for Re;Birth 2 to do the same thing. It worked when I initially started the game then I had to hop off for a couple hours and now it just doesn't want to do jack. Anyone have any suggestions?

[NanaPixel]

You could try DS4Windows. I use it with my PS5 controller and it works.

[Zuhan]

Originally posted by Meow~:

You could try DS4Windows. I use it with my PS5 controller and it works.

No worries, I found the .ini file and got it working like I did with Re;Birth 1

[Zuhan]

If anyone finds this post having the same issue I was here is what I did.

1) Find the Neptune2.ini file under "C:\Program Files (x86)\Steam\userdata\<steam-id>\351710\remote"

2) Open the file in notepad

3) under [System] find your controller id and scroll down till you find your controller id

Example:

[System]
Controller = {6f1d2b60-d5a0-11cf-bfc7-444553540000}
LastVoice = 1


[Controller {6f1d2b60-d5a0-11cf-bfc7-444553540000}]

4) Delete everything under [Controller {6f1d2b60-d5a0-11cf-bfc7-444553540000}] and replace it with:

Input00=4,0,0,0
Input01=4,1,0,0
Input02=4,2,0,0
Input03=4,3,0,0
Input04=3,2,0,0
Input05=3,1,0,0
Input06=3,3,0,0
Input07=3,0,0,0
Input08=3,8,0,0
Input09=3,9,0,0
Input10=3,6,0,0
Input11=3,7,0,0
Input12=2,2,0,0
Input13=2,3,0,0
Input14=2,0,0,0
Input15=2,1,0,0
Input16=2,4,0,0
Input17=2,5,0,0
Input18=2,10,0,0
Input19=2,11,0,0

5) Save the file.

This should force the game into allowing you to change from Keyboard to Controller. It'll show Xbox 360 but it works with the PS5 controller.

Now if only I could figure out how to disable the Tilt lock in dungeons.

[CascadeHush]

The game is very fussy about the controller. The controller has to be plugged in/turned on when the game launches, not plugged in/turned on after you start the game. Also, if you launch the game without the controller plugged in//turned on, or you move it to a different USB port, the game will forget and you'll have to configure it again, including swapping the A and B buttons around. I had to do this about 10 times in my 30 hour playthrough (Normal Ending). If the game doesn't see the controller at all, you need to restart the game.

Pretty slack really. The game was released in 2015, not 1995. This is the sort of nonsense I'd expect in a Windows 95 game, not one designed for Windows 10.

[VerdantCross]

I think PS5 controllers handle input differently than other controllers. Because for any older controllers, like PS4 controllers this game works fine with the steam controller configurations, since it has both DInput and XInput support, unlike some of the Neptunia spinoff games that only have XInput support. I think for most games honestly PS5 controllers need extra setup.

[【ネップ】— Excal —]

Originally posted by VerdantCross:

I think PS5 controllers handle input differently than other controllers. Because for any older controllers, like PS4 controllers this game works fine with the steam controller configurations, since it has both DInput and XInput support, unlike some of the Neptunia spinoff games that only have XInput support. I think for most games honestly PS5 controllers need extra setup.

DualSense user here. Disable Steam input. The early Neptunia games do NOT utilise XInput for controller support. In fact it just uses DInput **only**, even for your Xbox controllers. The DualSense just uses DInput, and it works perfectly with the game - you just to have to keep in mind that the default button mapping does not map to the correct buttons, since the DualSense have more buttons that you can map to than an Xbox controller (the PS Button and the touchpad clicker). The axes for the analog sticks are also swapped, so you'll have to reassign those too.

...also the PS4 controller has no XInput support. It's a DInput device through and through, having Steam input enabled just means that every connected controller turns into an Xbox controller, and that's probably where your confusion came from.

[VerdantCross]

That's incorrect though, some Neptunia games do not use DInput, but every one of them uses XInput, since these are all PC ports, they're made to work with Microsoft/XBox controllers, and have the button prompts to match controllers with an Xbox button layout. You can find the supported input methods for every game here. https://www.pcgamingwiki.com (Some are incomplete, but you can check most games and you'll see the only input method specifically mentioned as unsupported for some of the games is DInput).

It's mostly ports of spinoff games that don't have DInput support.

The problem the OP is having is that it's a PS5 controller, which I've seen people mention having issues with multiple games with for some reason. I don't really know why as most games that have issues with them seem to work with PS4 controllers, and both of them use DInput, but for some reason it just seems like often PS5 controllers need extra setup for some games.

And I didn't say that XInput was PS4 controllers. XBox and Microsoft controllers, and anything trying to replicate the same button layout for PCs generally uses XInput. But controllers made for other devices tend to use Direct Input.

[【ネップ】— Excal —]

Originally posted by VerdantCross:

That's incorrect though, some Neptunia games do not use DInput, but every one of them uses XInput, since these are all PC ports, they're made to work with Microsoft/XBox controllers, and have the button prompts to match controllers with an Xbox button layout.

Re;Births 1 2 and 3 don't use Xinput though. everyone is assuming that because they have xbox button prompts, that it uses Xinput, when it doesn't. DInput games can pick up Xbox controllers just fine. I'm literally using the PS5/DualSense controller right now without Steam input and the games are all picking the controller up as a regular wireless DInput controller. The Xbox button prompts are just cosmetic, it's why in the settings menu everything is labeled as "Button 1/2/3/4 etc" because that's just how DInput is. You're not mapping an Xbox button to an in-game action, you're mapping a DInput button/axis to its corresponding button/axis on an Xbox controller. The game is simply just assuming everyone is playing with an Xbox controller, regardless of the input API it uses, which in this case, is DInput.

You wanna know why PS5 controllers are so problematic with PC games? It's because Steam literally hijacks the controller the minute you plug it in (bluetooth/wired). It's been programmed to do that so it could utilise Steam Input natively (supposedly). I've been using HIDHide to literally make Steam unable to see the controller, and just playing the game with native DInput. For games that use XInput? I just use x360ce and everything works just fine and dandy. To hell with Steam Input in general, man.

To further prove my point, here's what happens if you leave Steam Input enabled, with a PS5 controller connected (all three Re;Birth games are like this):
https://i.ibb.co/NmZtcNQ/steaminputon.jpg

Here's what it looks like when you disable it:
https://i.ibb.co/v1F5SmV/steaminputoff.jpg