Ugh, the RE situation sounds horrific. One thing I've noticed with a lot of FPP/TPP console games whether shooters, rail shooters, arcade shooters etc. is that most if not all of them were built around a story that takes place with a "London fog". Oooo! Interesting plot element! Except... all it really is, is an attempt to hide the crappy draw distance needed in the game so that objects don't appear to pop into view magically 2 feet in front of your face because the console has crappy CPU/GPU power. It's not a special effect, it's what I like to call a "special defect". :) As such I classify games with fog as having +1 degree of "consolitis". :)

I know what you mean. I just played Deadlight a couple times in the last 24 hours and I went with the keyboard at first. The on screen key assistance shows both the keyboard keys and gamepad buttons and watching it I started thinking the gamepad might be better for this game as it fits into the category of platformer which is where I usually find gamepads work well. So... next time I started the game, I plugged in my Logitech F310. Game detects it no problem. Up doesn't work, down doesn't work, A and Y are reversed, some other buttons are reversed as well. If I'm not mistaken this means that a game thinks it is connected to an Xbox 360 controller and it isn't, or it thinks it is connected to a normal PC gamepad controller and it is connected to an Xbox controller - either way it has the buttons messed up.

<deep sigh>

This is where my engineer hat comes on and I think - how is it even possible that a team of anywhere from probably 5-20 or more developers design a game like this and have the skill and dedication to do all of that programming and complete the project... and not know how to detect a friggen game controller properly, or not give a crap about common input controllers people are likely to have? I mean, I am not a Windows developer and have never written Windows code before in my life or really looked at the APIs, but my brain refuses to believe that the APIs available in Windows do not present enough information to a game developer to detect what kind of controller it is. In my brain which could be totally mistaken, there is going to be a damn DirectInput API or whatever to invoke to detect connected game controllers, to get a list of connected controllers, to walk the list and look at each one's proper name, number of buttons, number of axes and other gizmos and crap, any other special stuff, haptic feedback yada yada, and then let you choose the controller from a list manually or just wait until you press a button and go "oh, you're using that one, cool, here is the info Windows gave us abuot that one" and just do the right damn thing.

Again, I don't know if there is an API for that but my brain thinks "In 2015, in Windows, for games - there HAS TO BE A FRIGGEN API TO DO THAT!" If not built into WIndows, then built into the Unreal engine or some other API that is being used. Why? Because it is 2015 for shit sake, not 1993! GRRRR!

No excuses! I bet I could google how to do this shit and find answers on Microsoft's website or Unreal engine docs or whatever in probably hours and code the shit myself. Give me the damn source code for the game and let me add proper input controller support. I'll have the damn thing working with my TrackIR before the night's over even if there's no sensible way to make that useful damnit!

Or, maybe I assume the APIs available to game programmers these days are nowhere near as advanced as I think they should be. I'll put my money on my assumptions being right though.

<deep breath> I feel so much better now, wow that was therapeutic!

:)