desertcucco's Forum Posts

• • desertcucco
  • 
  • • Joined 29 Aug, 2023
    • 
    • 2 topics • 3 posts
  • 1

  • 21 Jul, 2024
  • Quote

  Our game is Steam Deck verified and works well with its gamepad. But the built-in gamepad starts glitching when any external gamepad is connected. Maybe that's what happening in your case - try to remove bluetooth controllers.

  Hey, thanks for the reply. External gamepad was disconnected when I was testing the SteamDeck buttons.

  Can I ask how you exported? Did you use NW.js (and if so which version) or did you use WebView2? thanks again!

• • desertcucco
  • 
  • • Joined 29 Aug, 2023
    • 
    • 2 topics • 3 posts
  • 1

  • 20 Jul, 2024
  • Quote

  Construct 3 game will run fine on the SteamDeck exporting via NW.js, no issues there.

  However, the Gamepad object fails to recognize the SteamDeck's buttons -- in fact, it fails to recognize that a Gamepad is connected at all. There are two "workarounds" both of which aren't great: 1) connecting a bluetooth controller and playing on that which is unacceptible for obvious reasons or 2) going into the SteamDeck controller config and manually mapping all the face buttons to their keyboard counterparts which is also not great because every new player would have to do that and there's no way it's getting SteamDeck Verified.

  The question is: has anyone been able to get Construct 3 to recognize the SteamDeck itself as a gamepad?

  Construct team: do you have any suggestions? Are you planning on adding support? Given I'm paying $100+ a year or whatever it is this seems like something that should be supported. SteamDeck is a huge platform.

  Tagged:

  • construct3
  • controller
  • gamepad

• Try Construct 3

  Develop games in your browser. Powerful, performant & highly capable.

  Try Now Construct 3 users don't see these ads
• • desertcucco
  • 
  • • Joined 29 Aug, 2023
    • 
    • 2 topics • 3 posts
  • 1

  • 9 Jan, 2024
  • Quote

  Hiya, wondering if anyone has come across this and if there's a fix:

  When editing the collision points for a sprite, regardless of whether you manually enter the points, drag the points around, or use set to bounding box, one of the points will always subtract 0.1 from a corner after closing the sprite editor.

  Using Demonire as an example: if I go into the sprite editor for Player_Base and go to the collision tool, if I try setting each of the 4 points to the corner, the bottom-right point will set itself to x8 y7.9 even when I type x8 y8 or set to bounding box (which should set it to x8 y8 since the sprite is 8x8).

  This happens for every sprite so characters will sometimes stop moving if they're against a wall because they hit the 0.1 decrease.

  vid: youtube.com/watch