lolDayus

Yeah I know, Joyxoff works for that purpose but there's still an extra step of pressing another button as well as it being too "active" during the process; i.e. it has to be running in the background and it still is sensitive to button presses in-game where pressing the same "Launch app with button press" is still active if it's not specifically in fullscreen mode. I know it sounds like I'm being oddly specific/unreasonable with my intended interaction but it's just that DS4windows does it so perfectly that I figured there had to be SOMETHING out there that could do the same for the "fully supported" Xbox controllers as opposed to the "Dualsense masked as an Xbox 360 controller" finagling that DS4windows is essentially based around.

Posted this on reddit yesterday, didn't get any responses so figured it couldn't hurt to post here: I apologize in advance if I'm overlooking something but this is driving me nuts and I want to make sure it's not something simple: I just want to open Big Box whenever I turn on my Xbox Series X controller. I use DS4windows to accomplish this with my Dualsense controller (which "translates" the Dualsense as an Xbox 360 controller) perfectly thanks to its "Launch Program with Profile" feature. However, DS4windows doesn't work with actual Xbox controllers so I need another app that does the same thing but for Xbox controllers. I've tried several programs like reWASD and Joyxoff, but nothing will replicate the simple function from DS4windows that automatically launches Big Box as soon as the controller is powered on. Apparently Launchbox/Big Box used to have a "controller automation" option that I think could accomplish this but for whatever reason this option is no longer in Settings for either program. I saw some AutoHotkey scripts on the Launchbox forums but they did a bunch of other stuff that I don't want; I have large thumbs and am prone to accidentally hitting buttons so I don't want the Guide button/other buttons to just instantly close my game for obvious reasons; I literally just need it to do this one thing and then do nothing until the controller is powered back on again. Alternatively, if anyone knows how to get DS4windows to see/interact with actual Xbox controllers, that would more than likely be an even better solution for me personally as it would cut down on the number of apps/background programs involved

yeah I feel you on the pricing but if you get it on sale that definitely helps...not trying to shill for them or anything but with the triggered automation being integrated with all the other features that DF has, and everything actually working the way you'd expect/want it to (it does Windows better than Windows a lot of the time), it's definitely become one of the most "influential" apps on my PC since I use 3 displays, and I haven't regretted paying the fee for a second. And obviously it complements Launch/Big Box very well. I actually got it through Steam so you can find it on sale through there or the standalone program is usually on sale on like Cyber Monday iirc. anywaysss lol I've tried Win + P as well as Win + Tab and any other keyboard combos I can think of and still, the only thing that "overrides" that black screen having focus or whatever is Ctrl + Alt + Del. Thankfully that works every time at least but it's just a pain and kinda defeats the point of having even having a launcher to try to make my PC like a console w/ TV when I have to turn around and use my KB/M every time I want to open a new game. But yeah, I don't usually like getting GPO involved at all but that was the only thing related to the PC's "memory" of the shutdown configuration. It would be nice to figure out why just for curiosity's sake but it's taken up way too much time as it is lol, it's not like I even restart/shutdown my comp that often (sleep/standby doesn't affect the "weird" display state) so yeah I'm just gonna leave it alone for now lol

yeah I mean I use DisplayFusion with triggers to activate complete monitor configs (including it changing the "Make this my main display" checkbox obviously) and it's been amazing for my setup other than the fact that it can't seem to get around this caveat (I've tried cutting DF out of the equation completely but still get the same behavior regarding my TV being "weird" about being switched to). I've noticed that when the TV goes into this "weird" state, Alt + Tab causes the screen to briefly get some sort of horizontal lines moving down like it's got some sort of refresh rate issue but the main thing is that it doesn't do anything else, the same applies to the Windows key or even Alt + F4...literally nothing can get rid of the total black screen state other than Ctrl + Alt + Del and then just canceling back from that screen. All of these "change focus" methods work whenever it's not in the "weird" state I should mention. I know the whole thing being based off the state prior to the last reboot sounds absurd but I actually got the idea to test that specifically from a couple of threads on here with kinda similar issues, so it's not like it's unheard of. After a bit of research, the closest I can come to for addressing this "prior to reboot" thing is editing the Global Policy and going into the "Shutdown" folder like described in this post: https://www.displayfusion.com/Discussions/View/trigger-on-computer-shutdown/?ID=9f07647d-6ed3-4ca3-a586-d1b6d04ac790#6 But I'm not sure what to do from there (I tried DF command thing it suggests but that didn't work). So I think if anything is gonna be able to address this exact scenario it's gonna involve this setting, however I'm just not programming-inclined enough to figure out what script and parameters need to go in here. I'm gonna try to be more mindful about specifically having the TV powered on before I try to do any sort of monitor config switching like you suggested though so we'll see how that goes

Really an odd one here but it's driving me nuts: I have a multi-screen setup that includes my (usually set as main) 1440p monitor and my TV, which is what I want my game to display on. I can switch my display settings to having the TV as my only monitor and it still will not start my game properly (i.e. black screen until I hit ctrl alt delete, alt tab doesn't even work). Once I come back from the ctrl + alt + del screen, everything is back to normal. I have to do this literally every time I try to use my TV as my display, however I have discovered recently that my TV will display everything correctly the first time provided it was set as the "Main" monitor in Display Settings before my last reboot. It does not behave the same the other way around however; my 1440p monitor still behaves correctly if I want it to be my game's display even if my TV was the main display prior to the last reboot. I'm assuming there's some sort of scaling issue here but I cannot figure out how to resolve it; I've tried having Run as Admin on/off, "disable fullscreen optimization" on/off, DPI settings adjusted in the Compatibility settings, etc. It behaves the same way regardless of if I'm trying to launch through Big Box or Launchbox as well. What does the "needs to be Main display before last reboot" thing suggest/what settings would that even involve? Not sure if it's relevant or not but I guess I should mention my monitor is hooked up via Displayport on my GPU while the TV uses an HDMI port.