Tales of Vesperia: Definitive Edition

Tales of Vesperia: Definitive Edition

View Stats:
volcanomom53 May 18, 2019 @ 11:02am
Player 1 and 2 slots are swapped
For whatever insane reason the game is stuck thinking that player 2 should control character slot 1 and character slot 2 is controlled by player 1.
I've tried searching for a resolution to this issue but most things just turn up changing the characters AI back to auto.
For more details:
player 1 - controller
player 2 - kbm
all 4 characters are set to "auto" AI
start battle
hit select (whatever the share button on a DS4 is)
character slot 2 toggles to manual/semi-auto.
slot 2 has a P1 over it, slot 1 has a P2 over it.

If anyone has any ideas I'm all ears.
Last edited by volcanomom53; May 18, 2019 @ 11:03am
< >
Showing 1-10 of 10 comments
Simon May 19, 2019 @ 11:22pm 
Go into the "Buttons config" in the game settings. Make sure Player 1 is set to Controller.
volcanomom53 May 25, 2019 @ 10:30am 
Player 1 is controller, player 2 is set up as keyboard.
I reinstalled the game a few days ago and that fixed it, for awhile.
Now I'm seeing the same issue again.
I'm definitely still controlling player 1 but for whatever reason it thinks I want to play character slot 2
volcanomom53 May 25, 2019 @ 10:42am 
Here's an album of images that demonstrates what I'm talking about:

https://imgur.com/a/Z9jOP4p

I'm reasonably certain I've configured everything there is to configure. I have no clue what it possessing the game to swap P1 and P2
Simon May 25, 2019 @ 4:50pm 
Lol, that's funny.
Maybe you can find some clues about this problems by going to steam settings > controller > general config. Check the mappings and so on.

Or just unplug the keyboard/mouse if you are playing on desktop. XD
Last edited by Simon; May 25, 2019 @ 4:51pm
Kyle G Dec 15, 2019 @ 1:20am 
I had the same problem just now, and my solution was very simple. Just go to button configuration settings, and select "default". I instantly went back to playing as the P1 slot again.

Bumping this thread just in case my solution might work for someone out there as well as it did for me.
Last edited by Kyle G; Dec 15, 2019 @ 1:21am
Kegfarms Jul 8, 2020 @ 3:54pm 
Originally posted by Sandvich of Peace:
I had the same problem just now, and my solution was very simple. Just go to button configuration settings, and select "default". I instantly went back to playing as the P1 slot again.

Bumping this thread just in case my solution might work for someone out there as well as it did for me.

Your solution doesn't work.
erm Oct 24, 2022 @ 12:39am 
I have the same issue, and pressing default on the button configuration section also does nothing for me, it's clear that the controller is player 1, but the game is forcing player 1 to be the 2nd character slot.

Even if I just try to accept this and play like that, the character in the 1st character slot, marked P2 which in my button configuration is designated to the M+Kb, will not act, even if set to "Auto"

This is definitely a bug in the game's input / device detection.

The issue is only present on my desktop PC, if I play on the Steam Deck the game behaves normally. Thankfully, I'll be able to finish the game on the Steam Deck and it will be fine, it's just that I would have liked to do it on desktop for some parts to make following a missables guide a little easier.

Lastly, since people in other places where I've researched this issue love to discredit the issue as user-error with the artes menu Auto/Semi-Auto/Manual setting + button configuration settings, I am not inexperienced with Tales character slot control / the auto/semi-auto/manual system. I've played this game to completion on the 360 like 5 or 6 times, several of these runs being entirely co-op with lots of character/slot switching. I understand the system intimately, but the game's input device detection just will not behave correctly on my PC.
Kegfarms Oct 26, 2022 @ 9:20pm 
Originally posted by cat pig oink meow:
I have the same issue, and pressing default on the button configuration section also does nothing for me, it's clear that the controller is player 1, but the game is forcing player 1 to be the 2nd character slot.

Even if I just try to accept this and play like that, the character in the 1st character slot, marked P2 which in my button configuration is designated to the M+Kb, will not act, even if set to "Auto"

This is definitely a bug in the game's input / device detection.

The issue is only present on my desktop PC, if I play on the Steam Deck the game behaves normally. Thankfully, I'll be able to finish the game on the Steam Deck and it will be fine, it's just that I would have liked to do it on desktop for some parts to make following a missables guide a little easier.

Lastly, since people in other places where I've researched this issue love to discredit the issue as user-error with the artes menu Auto/Semi-Auto/Manual setting + button configuration settings, I am not inexperienced with Tales character slot control / the auto/semi-auto/manual system. I've played this game to completion on the 360 like 5 or 6 times, several of these runs being entirely co-op with lots of character/slot switching. I understand the system intimately, but the game's input device detection just will not behave correctly on my PC.

Yep. It's just bad coding from Bamco. It happened in Zestiria too.
rogerio. Jan 2, 2024 @ 4:18pm 
Bros, after a long time I found out what was happening, in my game the Menu Screen Button Configurations was "Player 1 Keyboard", change the settings in the menu screen, for some reason even with the right configs in game, this problem happen, but yes, change the configuration in the Menu before loading the save game
Kegfarms Jan 3, 2024 @ 9:44pm 
Originally posted by rogerio.:
Bros, after a long time I found out what was happening, in my game the Menu Screen Button Configurations was "Player 1 Keyboard", change the settings in the menu screen, for some reason even with the right configs in game, this problem happen, but yes, change the configuration in the Menu before loading the save game

I think I tried that and it didn't work. Been awhile though. Still having some issues even in games like Arise but minor compared to this.
< >
Showing 1-10 of 10 comments
Per page: 1530 50