Some games behave better when controller is "connected" before game start. Some games might not detect controller if "connected" mid game or behave strangely.
Only way ReWASD can do this for Virtual controllers is to apply mapping manually before game start or permananetely keep Virtual controller.
Maybe a good solution or workaround is a ReWASD "launcher". Basically a program that applies mapping before game starts.
So you start game like
ReWASD_launcher doom.exe
launcher sees doom.exe ... apply mapping for it ... then launch doom.exe. That way all virtual controllers are initialized before game start. Ofcourse it should be able to take any parameters that game accept ... e.g.
ReWASD_launcher doom.exe /fullscreen
Also interesting ... if real controller disconnects, not to "unload" corresponding virtual controller. If subsequently, another controllet connects - bind it to "vacant" virtual controller
1. Allows swapping controllers in mid game
2. Allows replacing controller in mid game if original controller ran out of battery
Only way ReWASD can do this for Virtual controllers is to apply mapping manually before game start or permananetely keep Virtual controller.
Maybe a good solution or workaround is a ReWASD "launcher". Basically a program that applies mapping before game starts.
So you start game like
ReWASD_launcher doom.exe
launcher sees doom.exe ... apply mapping for it ... then launch doom.exe. That way all virtual controllers are initialized before game start. Ofcourse it should be able to take any parameters that game accept ... e.g.
ReWASD_launcher doom.exe /fullscreen
Also interesting ... if real controller disconnects, not to "unload" corresponding virtual controller. If subsequently, another controllet connects - bind it to "vacant" virtual controller
1. Allows swapping controllers in mid game
2. Allows replacing controller in mid game if original controller ran out of battery
Comment