notNSANE

The new lighting is cool (but bugged) and it makes the stencils in the relax section of the Orbiter seem like they're made from Vanta black.

I had to uninstall, and now I can't reinstall the game. Great job DE. I'm forced to play the standalone version because you wouldn't fix Steam Input on the Steam version and now I can't even play the game in any way. What's even better, when all this works, my entire configuration would probably be reset, including all my custom HUD colors that took me hours to setup.

I uninstalled the standalone WF version and now I cannot install it again no matter what I do.

this new big update broke Steam Input config again?

Thanks, it seems you're starting to grasp the system (about time). I have hundreds of hours using Steam Input (SIAPI), and most of those were solving headaches with Steam Input's UI. Here's some outliers from the current config: 1. Remove "Launcher" Action Set. No need since Valve has added support for all the launchers years ago, it's redundant. 2. Remove the "Melee" Action Set. No need for it since Melee Channel isn't a thing anymore, just move the SIAPI call to Secondary Fire. Again, it's redundant. 3. Add a "Drifter" Action Set ASAP. No sure why you added Shawzin and not Drifter. 4. Add Xinput support back. No reason to keep it disabled. And please do try to give continous support to it, else, it's going to break in a couple years when you add a new mode or item.

This is the gamepad issue? You need to assign a SIAPI action to the Camera's "A button" interaction, which currently isn't mapped. Also, DONT FORGET TO ADD A "B BUTTON" since else we won't be able to close the camera feed!