Hi! It’s a little strange...
It works fine on all my computers.
Does your keyboard is in English ?
In the game, do you put some energy in components? You have to go to the BACK menu and add energy to activate buttons. It’ always a little bit confusing in the beginning…
If it’s not that, I will try to find the bug. A new version with bugs corrections and balance corrections will be released soon. I hope it will work for you !
Not sure what you mean by "your keyboard is English", but i am writing in English right now using it, so i suppose it is.
I didn't put any energy into the components because i didn't even get the steering under control. Again, the game doesn't acknowledge the existence of my keyboard at all, and doesn't really cooperate with VJoy, either. Shooting weapons is secondary to moving and, most importantly, being able to navigate the main menu to be able to start a game.
Which, by the way, doesn't work with the keyboard, either. The only way i managed to start a game is by fiddling with the game by emulating a gamepad via VJoy. Using the keyboard directly doesn't even allow me to select things in the main menu.
Again, i think you should toggle the Input Selector™ on for this project just in case people encounter the same issues i did. There's no guarantee it would help but... it wouldn't hurt, that's for sure.
Hope you fix it soon.
Well, it seems to be working now... and it seems like the issue was on my side.
The addition of the pre-launch Input Selector dialog made me look into the issue in more detail and try all the keys again. And, as it turns out, i didn't try all of them before. Several of them worked, and i was even able to enter a mission by pressing Q twice. Still, the WASD input didn't work a single bit. It felt... stuck. As if some gamepad was connected and the stick on it was pulled fully to the side.
Which made me check my gamepads(or the lack thereof) again using that html5gamepad site. Turns out there were two virtual gamepads, which were VJoy's fault, and they were outputting NaN(is that even legal?!) on most of their axes.
I went to the Device Manager and shut them down. And yep, the game is now fully playable.
Long story short, i am not smart.
Sorry for wasting your time like that. I'll go ahead and finally try the game out properly, probably tomorrow. Though i did play it for like 5 minutes today after i figured out my input issues and, unsurprisingly, it looks and feels really good.
I think you should keep the pre-launch Input Selector enabled, though. It's quite the useful thing, allowing players to tune the settings(input, graphics quality, screen resolution) through a reliable UI.
Yeah... sorry again. I should've handled this better
