I use XD almost every day for wireframing and prototyping game interfaces for both mobile, PC, and console games. For mobile and PC games I'm pretty happy with the current feature set but I feel like there are a few improvements that would really help those doing UX for console games. Here are a few points, in particular, I'd love to see improved.

1) 'Combination' Trigger type for Interactions
For interfaces in games you quite often need to press a combination of keys, buttons, or key + click to open menus. It would be great if you could set an interaction that could be triggered by a combination of a 'tap' and a 'key' - eg. 'Option + Right Click' to display a menu etc.

This also applies to a combination of buttons on a single trigger interaction such as a gamepad. So many games on Nintendo Switch require the simultaneous press of two trigger buttons to start a game. But currently, only one gamepad trigger is allowed in XD, so that basic and common input cannot be prototyped.

2) Use the Analog-stick movements on a gamepad to simulate a 'drag' effect of a scrollable group.
Examples of where this is used, if my game has a large map that is bigger than the screen and I place it in a Hor & Ver scroll group, on PC I can drag my mouse around to pan the map. On the gamepad, I would like to use the controllers analog still to control that panning movement.

3) Support for Diagonal control triggers from Gamepads
So for example, instead of just Up, Down, Left & Right, it would be great to detect top-right, bottom-left etc. from the position of the analog stick.

4) Disabling default arrow key controls in the Desktop Preview
When developing interfaces for PC games, using the arrow keys to navigate menus is a must. While I know there are some hacky ways to prevent this from happening, a simple checkbox from the dropdown menu in the Preview (underneath the enable microphone etc.) to disable or override the default arrow controls that jumps you between artboards would be SO handy. The desktop preview is so quick when testing as I am building, but having to generate new shared links and disable navigation just to test those features is just too slow, not only that but clients and team members may be viewing that link, so testing it locally in the Desktop Preview is essential.

5) Support for Nintendo Switch and Xbox One Controller inputs within XD.
Currently (using version 43.0.12.14 on Mac), I am only able to use a PS4 dual shock controller to input the interactions. If I plug in or Bluetooth connect a Switch Joycon or Xbox One controller it does not detect any inputs within the Interaction/Trigger menu. However, when I share the link to test the prototype the browsers do recognize those gamepads.

We need to be able to recognize the different gamepads (major platforms) within XD so we can assign different button triggers/interactions for different gamepad types all within the same one prototype file. As I prepare the UX for the different platforms support Switch, Playstation, Xbox and Steam (PC) I would love to be able to set those different interactions all in one document rather than duplicating it four times.

6) Ability to type in the gamepad triggers (autocomplete field) if I do not have the gamepad with me. If my fiance is in the middle of an epic Overcooked game and I have a UX deadline, I'd rather have the option to type in or select the controller triggers within XD like 'Playstation – Circle' without having to take the controller from her just to set that trigger (Overcooked is a stressful game as it is and I'd like to get married soon :)

Hope your team can help with some of these ideas, it would make the user experience for me so much better and improve my workflow and output dramatically.

I came across a superior licensing (adapted below). It is kind to customers who need the software briefly rather than regularly. To sum it up the software works perpetually but updates require periodic renewal. It also encourages developers to serve the people's needs so they renew the service. Currently you have to pay constantly for software that doesn't have to improve.

Yearly License Explained
The yearly license model is becoming a popular pricing model for design tools. It’s fair for developers and customers.

You get frequent, useful updates and we get rewarded for our ongoing full-time work on Adobe. You aren’t tied to a bothersome subscription and we aren’t incentivized to hold back features for huge yearly releases.

Free Minor Updates
You will also receive free smaller updates with bug fixes and small new features.

License Expires After a Year
Your license expires, but you still get free minor updates. When a new major version is released, renew your license to upgrade.

Adobe Never Stops Working
You can choose not to renew and continue using your current version as long as you want. We’ll even release free critical bug fixes if necessary.

I often have to export modules/images for dev. This includes a text portion which I use auto height with padding. Then I have the elements stacked. If the objects aren't pixel perfect it leave a gap. 

So for example:

Vertical Stack 1: 50px height

Vertical Stack 2: 50px height

Vertical Stack 3: 50px height

Exports completely fine because pixel are perfect.

But if it's not pixel perfect

Vertical Stack 1: 50px height

(transparent gap)

Vertical Stack 2: 51.2px height (because of auto-height element with text)

(transparent gap)

Vertical Stack 3: 50px height

Anyway to fix this issue? Perhaps auto-height feature rounds up to the next perfect pixel point and not allow decimals???

Test image attached for reference.