Force T2 to output when connected console isn't recognized?

[Lollie]

Mad scientist question incoming, forgive me for the oddball use-case.

I recently bought a Brook Wingman SD - an adapter for the Sega Saturn and Dreamcast that accepts modern USB gamepads. PS3/PS4, 360/XBO, and Switch.

I decided to see if I could connect my Titan Two to it: Via GTuner IV, set it up to act as a PS4/XBO controller, and see if that would be enough to fool this Dreamcast adapter into accepting inputs. My idea was to use my Titan Two with GTuner IV's Virtual Controller tool, so that I could get a cheap Dreamcast input display out of the combination.

...Obviously this didn't work. What I did see though was that Titan Two's output light was slowly blinking red. I'm assuming that Titan Two has a whitelist of supported consoles, so if it doesn't recognize what its output is connected to, it simply won't output.

If the above is true: Is there any way to force Titan Two to output as whatever controller type is selected, regardless of whether it recognizes the output device?

[antithesis]

Gtuner IV > Device Configuration > Output Protocol.

[Lollie]

Gtuner IV > Device Configuration > Output Protocol.

Nope, been there! Different issue!
(edit: I'm actually a dummy, this helped me!)

When outputting to a device that Titan Two doesn't recognize, I just get a slow red blink from Output, like the gif below.

ezgif-2-cab3cc4b4bac.gif (200.66 KiB) Viewed 1503 times

My Titan Two definitely works with other consoles, and the other adapter works when the PS4 controller is connected directly, so I can only assume this has something to do with how Titan Two detects the device that it's outputting to.

[J2Kbr]

What your gif shows seems to be an USB bus reset loop. Mostly like is the adapter that is reseting the Titan Two, perhaps it is expecting some predefined USB enumeration sequence and, by not finding a match, issuing the reset.

[Lollie]

Gtuner IV > Device Configuration > Output Protocol.

My apologies, this actually did turn out to be the answer! I just didn't reset the connection to the adapter after changing the protocol, oops. Thank you!

Having Titan Two's output protocol set to "USB Automatic" would cause the red led loop, but setting it to a specific output protocol (in this case, literally any of the other USB options) would allow Titan Two to talk directly to the adapter - after unplugging and replugging.



And it functions! Shoulder buttons currently don't work for some reason, I'm assuming they just need to be remapped. But all the face buttons and the left stick work exactly as they should.

edit: For anyone working with Brook adapters, they have button codes that alter how inputs work. In my case, one Select+Triangle later, and it's all working perfectly.

[J2Kbr]

Awesome, thank you for keeping us updated on the results.

[Vorenus]

I just received my new Titan Two, and sadly no matter which output protocol is set, it will not connect to my Wingman SD. Both are on the latest firmware. Interestingly, my old Titan One still connects fine to the Wingman SD when in PS4 mode. I purchased the Titan Two specifically for the input display capability with the virtual controller in Gtuner IV, and for now I'm not able to do this with Dreamcast.