Inputmapper xinput test4/1/2024 XInput controller affects its XInput player number AND the other controller’s, and both show up as “XInput controller”. Game creates the “ghost” controller on (re)start.XInput controller LEDs show itself connected as PlayerIndex 1, even if connected later, though the order is correct in-game. When 1 XInput-native controller is connected with one other controller (either Switch or PS4), connection works mid-game.Controller LEDs show the controllers registered as PlayerIndex 1 and 2. When only one or more XInput-native devices are connected (tested with 2), controllers work as expected in both mid-game connection and on (re)start.They each affect only their own PlayerIndex and have the correct player indicator LEDs on the controllers. In testing, when no XInput-native devices are connected, supported controllers work as expected both during connection mid-game and on game (re)start.It seems to act differently depending on the number of Xbox controllers connected. I have at hand 2 Xbox 360 controllers (wireless, using the USB receiver), a PS4 controller and a Switch Pro controller. _spriteBatch.DrawString(font, outputStr, new Vector2(20, 20), Color.White) Protected override void Draw(GameTime gameTime) GamePadCapabilities capabilities = GamePad.GetCapabilities(i) GamePadState gamepadState = GamePad.GetState(i, GamePadDeadZone.Circular) Protected override void Update(GameTime gameTime)įor (int i = 0 i < GamePad.MaximumGamePadCount i++) _spriteBatch = new SpriteBatch(GraphicsDevice) _graphics.PreferredBackBufferHeight = 900 _graphics.PreferredBackBufferWidth = 1600 _graphics = new GraphicsDeviceManager(this) Here’s a simple MG Game class to test what I have described above (you will need a simple font content file to load to render the debug info - in this code it loads an Arial.xnb spritefont): using Tested with MonoGame 3.8 - DesktopGL on Windows 10 圆4 Seemingly not a driver-level bug, because Windows doesn’t report multiple copies of the Xbox device, and this only happens if you Init the program with both connected at the same time. I wonder if this is a MonoGame bug, an SDL bug, or perhaps something even deeper. If you disconnect the PS4 controller, the “ghost” remains until you restart the program (presumably, until MG/SDL/both have re-Init-ed). If you connect the PS4 controller after the program starts (presumably, after MG/SDL have initialized), then everything works as expected, but if the programs starts with the PS4 controller and other controller connected you can see the bug. If you disconnect the Xbox controller and reconnect, then the new one will work as expected, but leaves behind the “ghost” duplicate that does not report button presses or anything. ![]() On 2 different GamePad indexes, and both report button presses to polling and such. So what’s happening is that if you start a MonoGame program with a PS4 controller connected and some other controller (tested with Xbox 360 and Xbox One controllers), instead of MG reporting the PS4 and Xbox controller, there are 2 instances of the Xbox controller. If anyone can shed some light on this, it’d be super helpful.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |