Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Topic on Glossary talk:Controller

Xinput ==> Directinput independent triggers [+rant]

11
Mirh (talkcontribs)
  • Playstation based [Dinput Wrapper for SCP Driver]
  • Some others (including wired X360) [XBCD drivers]
  • Wireless X360 [1] Still requires japanese force feedback driver (which has ghost inputs and make games crash), and.. triggers become digital

Besides, the page may even be more.. appealing and less.. textual than 6 months ago. Though really, sections are really shallow.

I mean.. we should think: "what could the average Joe need first?" Drivers? Info about APIs? Info about keyboard-only games? Would this make more sense in a dedicated page?
And Durazno is everything, but a DirectInput wrapper. If you don't/have the time to know what you are writing, stop it or write in the talk pages

EDIT: Xinput Plus probably address all issues altogether
EDIT2: seems like it lacks some of the different kinds of vibration

V00d00m4n (talkcontribs)

Thinking too much about average Joe and not giving detailed options to power user is what ruined PC gaming i recent decade. Average PC gamer is no average Joe. PC gaming wiki is about deep tweaks, deeps tweaks is not something that average Joe can handle. And what are you talking about? Did someone call Durazno a Dinput wrapper?

RaTcHeT302 (talkcontribs)

We should always presume that the user might be doing certain things for the first time, I try to keep my instructions complete but easy to follow without going over pointless details. I seriously don't give a shit about how certain things work once in a while, I'd rather just get to the point and be done with the, thingy I was doing. It's worse when someone gives you half assed instructions and expects you to figure out the other half by yourself, that happens way too often on other wikis, or anywhere really.

This page is a mess but I have no idea how to clean it up myself, I just don't know enough things about it to make the page look nice.

Edit: Also it's good to cater to a wide audience.

RaTcHeT302 (talkcontribs)

Unrelated but, holy fuck those keypoints are way too overkill. There's like 15 of them :v

Mirh (talkcontribs)

Did someone call Durazno a Dinput wrapper?
Yes, somebody did.

And for the records I was exactly saying that the page has been a little too much streamlined (Xinput+ description is a bit too verbose though)

PC gaming doesn't need to be elitist either.
What I'm wondering is: how may we handle the implicit reminder that if game is using DirectInput and you have a x360-like controller, you'll need these solutions?

Since it's a problem with every DI game and technically with OS/driver itself, it shouldn't be mentioned everywhere (it's not an issue on the game side). But then you'd have the case of the casual noob which just checks "NFSU2" or "TW3" and just reads those pages (the later of this having the inverse problem with Xinput of course)

Blackbird (talkcontribs)

DInput should redirect to generic information about it like it was mostly used in year etc. and you can use those wrappers for your XInput controller blahblah. Since I doubt DInput/XInput checkmark will be added to Input settings template (haha API section)
This page could be used for that kind of stuff yeah.

Mirh (talkcontribs)

It wouldn't still be enough.

I mean, who tells you you'd need additional step just because you choose a X360 controller instead of a PS4 one?
I mean, it's not intuitive.

Similar considerations also apply to DirectSound hardware buffers then

Blackbird (talkcontribs)

Pretty sure that'll become obvious when the controller can't be fully mapped.

Mirh (talkcontribs)

Assuming you are... smart, sure.

But even reading half a PCGW page can already be a tremendous mental effort for some people, if you know what I mean.

Blackbird (talkcontribs)

Tbh even simply drag and drop is hard for some people I know so eh :D

Garrett (talkcontribs)

Alternate drivers are controller-specific so should be covered on individual controller pages rather than the central controller page.