Al. Lopez

and it came at the worst possible time...

*Look at valve's big announcement*

To developers who insist on using a decades old deprecated Input API that is XInput, instead of using either SDL Gamepad API (preferred) or MS GameInput:

i made a typo, so i'll fix it.

"he'll be fine"

Tatsuki Fujimoto really delivered on this new Chainsaw Man villain.

but I can ask other of my gyro buddies over at Gyro Gaming discord to also verify for me.

I can confirm that my DualSense controller works via USB only, same as DualShock 4.

The only weird oddity I'll give is Player LED shows Player 1 and Player 4, as if it's trying to form 👀 (eyes).

Steam’s Controller Support Wizard and you! — A Guide about adding Gamepad info to your storepage A dummy’s guide on how to tag Controller Support Informatino to your game’s Steam storepage!

i've seen honest mistakes like this happen before, and it's a major contributer on why i written a "Dummy's guide" for it.

medium.com/@AL2009man/s...

on Full Controler Support page, alongside "Your Xbox Controller", you'll see "Your DualShock Controller", which typically means "DualShock 4 controller is supported on both USB and Bluetooth, but the demo build is inaccurate.

sorry for being 4 months late, but you might wanna update the Controller Support listings to be more accurate.

right now, DualShock 4 and DualSense are only supported via USB but no Bluetooth...

but due to lack of DualSense being listed: Steam Input is just gonna prevent DS users to try out Gyro!

so, does that mean Gyro Aiming support is also coming to the rest of the platforms that can support it (PC via PlayStation controllers, PS4 and PS5)?

we Aoi Hono/Blue Blazes now bois

close enough.

Welcome back, Aoi Hono/Blue Blazes.

Which...is the most likely route to that.

although, it might require a massive amount of spite.

Does this mean we are finally gonna see lilith.pk3 on GZDo-- I mean UZDoom? 🤔

Close enough.

Welcome back, LittleBigPlanet Karting.

So, I hope this clarifies things up and hopefully: BF6's Gyro Aims gets more cooking time as it desperately :)

While I still standby what I've said in the first two tweet: the third tweet is where an apology I ultimately felt warranted, so I hope the Console/Controller Lead dev read this thread and understand where I'm coming from.

I believe it's objective feedback, but said feedback came out of love and betterment for gyro aim.

I do want to see Battlefield 6's current gyro aim implementation to get better, but as it stands: it's not in a good state, UI-wise.

This is why I came across as meanspirited in the first place, but I was meant to be blunt and respectful as possible: I believe the gyro UI stuff is in an unfinished state that really should've been put on hold for when Battlefield Studios can move onto the next patch phase, which they plan to do.

I've (with help from the funni Copilot thing) implemented Gyro Aiming on a source port to understand how this sort of stuff could've easily been solved in the UI-sense...in roughly 1–2 days (depending on UI Code).

a simple “Gyro On/Off” and “Flick Stick On/Off” toggle would've been sufficed.

in Battlefield 6's case: this is different, as I've shown the video itself. Additionally: rebinding it also loses joystick camera in the process, ya practically forced to use “Flick Look” if you want camera controls back.

This is really shouldn't been shipped in this state.

While the approach I've taken is very different, it did lead into two results:

The former removes mentions of gyro on Steam's storepage (but still mentioned on GOG, last I checked), while the latter gave the ability to turn off Aim Assist.

The former is false advertisement on PC as the storefront directly mentions it, while the latter demonstrated a good case study on why you shouldn't put Aim Assist on Gyro Aim.

Whenever I see a game that promises that it has gyro aiming features, and it does not delivery on what is promised, or has a problematic feature: I will start calling it out, and I will tend to be harsh towards it.

The House of the Dead Remake and Deadzone Rouge are two case studies.

Initially, I was dumbfounded on why I got blocked, so I asked a few in the gyro community.

After that: I gave it a bit of a thought…maybe there was a misunderstanding? And how that tweet might have been seen differently under a stressed period. So, I want to clear things up!

I'm just one of the people who have expressed disappointment, but the disappointment turned into frustration and anger the moment they said “get the base functionality out and collect feedback than bar people from having it” tweet.

The current UI/UX design makes it difficult to gather feedback.

so, third tweet sound abrasive, dismissive and potentially sarcastic, It was never meant to be.

It's meant to be a “let's hope for the future” type of message, despite how much anger it comes across.

"@The_n0ttus has blocked you" message

And all of a sudden: I got blocked.

LadForThejob: "Little bit of negativity with regards to the gyro aiming stuff. I think ppl were just excited to see it implemented and were disappointed when it didn't work as expected. I, like many, at the very least appreciate you put in the work to supporting a niche feature we enjoy." - Matthew: "All good. I appreciate all the feedback and now with launch we shift to refinement and improvement. The controller experience is very important to us here on Battlefield and we will keep improving it. Like everything in game dev just need resources and time :)" - AL2009man: "let's hope the actual gyro setting UI is properly implemented and easier to collect the important player feedback that way!"

At the same time: given Battlefield Studios' Controller team is promising updates to the existing gyro implementation: I am hopeful that things will get better and start addressing key issues raised.

Thus: I responded and made this tweet.