byuu's message board

For discussion of projects related to www.byuu.org/


Previous  1, 2, 3  Next
"Trigger" buttons can't be mapped 
Author Message
User avatar

Joined: Sun 12 Apr 2009, 06:36:33

Posts: 199
Post Re: "Trigger" buttons can't be mapped
:( Sorry byuu.

Fri 05 Sep 2014, 01:18:10

Joined: Fri 10 Apr 2009, 15:00:08

Posts: 13668
Post Re: "Trigger" buttons can't be mapped
You're fine, I don't mind people asking about it (it'd be doubly nice if others answered for me ;) I even responded with all the relevant info already, even in this thread.

I don't have anything more to say about the trigger issue for GeneralFailer, though. Not upset with him either, just don't like being coerced into responding.

Fri 05 Sep 2014, 01:47:56
Post Re: "Trigger" buttons can't be mapped
byuu wrote:
> Byuu, will you comment on the 360 triggers issue? You ignoring these reports is getting a bit weird.

Don't try and coerce me into responding.

I've commented to death on the situation with triggers and APIs. I'm tired of repeating myself every time someone new comes along.

I'm sorry, I didn't want to sound rude.
It's just that it's a version-specific bug, so Higan not detecting triggers is unlikely to be XInput's fault. As was said in the report I have posted link to, v093 detects them just fine. And it's not like I'm asking support for some obscure gamepad, official Xbox 360 controller support is a given for any modern emulator on PC. I'm asking because this is a serious issue which shouldn't be hard to fix.

BTW, you should really consider writing an FAQ for such questions. Expecting everyone to do a really deep search before asking such things without it is unfair. If you write it, you can ignore them all you want.

Fri 05 Sep 2014, 11:45:56
Report this post
User avatar

Joined: Thu 22 Mar 2012, 04:37:56

Posts: 502
Post Re: "Trigger" buttons can't be mapped
Even writing an FAQ can easily get out of hand in terms of effort due to higan's size.

Fri 05 Sep 2014, 14:03:38
Post Re: "Trigger" buttons can't be mapped
wareya wrote:
Even writing an FAQ can easily get out of hand in terms of effort due to higan's size.

I'm not proposing to write a very elaborate one, only the essential stuff, like when to use accuracy version, possible input issues caused by APIs, etc. Just problems newbies usually face and questions advanced users often ask.

Fri 05 Sep 2014, 16:39:04
Report this post
User avatar

Joined: Thu 22 Mar 2012, 04:37:56

Posts: 502
Post Re: "Trigger" buttons can't be mapped
GeneralFailer wrote:
only the essential stuff, like [...] possible input issues caused by APIs, etc.

So, an elaborate one.

Fri 05 Sep 2014, 16:42:19
Post Re: "Trigger" buttons can't be mapped
wareya wrote:
GeneralFailer wrote:
only the essential stuff, like [...] possible input issues caused by APIs, etc.

So, an elaborate one.

I mean like the DirectInput ones I brought up in this thread, one of which byuu chose not to work around for political reasons, which I respect, but lack of accessible documentation about this makes higan less user-friendly, especially for newbies.

Fri 05 Sep 2014, 17:04:53
Report this post

Joined: Sat 06 Mar 2010, 23:49:00

Posts: 80
Post Re: "Trigger" buttons can't be mapped
byuu wrote:
> Also DS4 input apparently doesn't prevent Windows from turning off the display on Windows 8.1 x64.

Yep, that's a known bug in Microsoft Windows. I'm not sure if they're ever going to fix it, though.

Linux unfortunately has the same bug.

The operating systems should treat gamepad input as input for the purposes of screen saver suppression, but they do not. Instead they put the onus of this on every last game developer.

What makes more sense to you? Three operating systems putting a bit of code to link gamepad input to act like keyboard and mouse input already do? Or 100,000+ games all adding code to disable your screen saver when you run the application?

On Windows, I think it falls to the driver authors, not the application developers. It's up to the input driver to interpret the input and tell the OS when a user is present. Pretty sure the Xbox 360/One controller drivers already do this, as I can confirm that button presses will suppress the screensaver (though it won't be dismissed if it's already up). Not sure about the generic HID driver, though I would assume it does the same as well. Third party drivers are wildcards, as always.

GeneralFailer: It doesn't look like there are even official drivers for the DS4. The ones I could find are open source, so you could try filing a bug or submitting a patch.

Sun 07 Sep 2014, 07:19:14
Post Re: "Trigger" buttons can't be mapped
invertigo wrote:
GeneralFailer: It doesn't look like there are even official drivers for the DS4. The ones I could find are open source, so you could try filing a bug or submitting a patch.

DS4 works out-of-the-box via generic Wireless Controller driver in Windows AFAIK.

Sun 07 Sep 2014, 09:42:19
Report this post

Joined: Sat 06 Mar 2010, 23:49:00

Posts: 80
Post Re: "Trigger" buttons can't be mapped
Ah... the search results for "DS4 Windows" led me to believe that you needed to install an unofficial driver, but it turns out that was just to get XInput support. So I guess it does function as a standard HID controller, which I guess means that that generic Windows driver doesn't suppress the screensaver, and that's a bummer.

Sun 07 Sep 2014, 10:40:50
Post Re: "Trigger" buttons can't be mapped
invertigo wrote:
Ah... the search results for "DS4 Windows" led me to believe that you needed to install an unofficial driver, but it turns out that was just to get XInput support. So I guess it does function as a standard HID controller, which I guess means that that generic Windows driver doesn't suppress the screensaver, and that's a bummer.

This is exactly what byuu was talking about. It might mostly be because keeping DirectInput implementation flawed helps MS to promote both Xbox controllers and XInput API. On Linux on the other hand existence of this issue is really weird.

Sun 07 Sep 2014, 12:22:11
Report this post

Joined: Wed 06 May 2009, 04:13:19

Posts: 4543
Post Re: "Trigger" buttons can't be mapped
GeneralFailer wrote:
invertigo wrote:
Ah... the search results for "DS4 Windows" led me to believe that you needed to install an unofficial driver, but it turns out that was just to get XInput support. So I guess it does function as a standard HID controller, which I guess means that that generic Windows driver doesn't suppress the screensaver, and that's a bummer.

This is exactly what byuu was talking about. It might mostly be because keeping DirectInput implementation flawed helps MS to promote both Xbox controllers and XInput API. On Linux on the other hand existence of this issue is really weird.

The issue predates XInput by years and years.

_________________
This post best viewed at 800x600
;write ! ! !

Sun 07 Sep 2014, 12:38:44
Post Re: "Trigger" buttons can't be mapped
CaptainJistuce wrote:
The issue predates XInput by years and years.

And yes, MS are also lazy and don't really care about state of PC gaming industry, except when they need to sell new OS.

Sun 07 Sep 2014, 12:56:13
Report this post

Joined: Wed 06 May 2009, 04:13:19

Posts: 4543
Post Re: "Trigger" buttons can't be mapped
GeneralFailer wrote:
CaptainJistuce wrote:
The issue predates XInput by years and years.

And yes, MS are also lazy and don't really care about state of PC gaming industry, except when they need to sell new OS.

They care in fits and starts. DirectInput(indeed, all of DirectX) was a huge improvement over the mess of proprietary interfaces it replaced, and well, without it we would PROBABLY still be rebooting to MS-DOS for games.


And it's not like the PC gaming industry really needs any help shooting itself in the foot.
I suspect DirectInput not blocking screensavers was never considered an issue because everyone but the flightsim crowd decided if it can't be played with a goddamn TYPEWRITER it wasn't worth playing.

And now, they consider DirectInput a legacy interface.
If you aren't using XInput for your joysticks and gamepads, you are either a horrible monster or a flightsim junkie. Which is basically the same thing.

_________________
This post best viewed at 800x600
;write ! ! !

Sun 07 Sep 2014, 13:16:04
Post Re: "Trigger" buttons can't be mapped
CaptainJistuce wrote:
And now, they consider DirectInput a legacy interface.
If you aren't using XInput for your joysticks and gamepads, you are either a horrible monster or a flightsim junkie. Which is basically the same thing.

Too bad the majority of new gamepad models still don't support Xinput, almost 9 years since its release.

Sun 07 Sep 2014, 13:41:30
Report this post
Previous  1, 2, 3  Next

Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum