Space Bar Not Working

[GLUTIUS MAXIMUS]

I haven't played in a few months so i jumped on to do the training missions to get a refresher in the A10c. but when they ask me to hit space bar to advance to next step it no longer works. its only a problem in the A10c the space bar works fine in the mirage, I have not yet tested the F5e to see if its a problem there.

[GLUTIUS MAXIMUS]

wow still no fix for this

[ApoNOOB]

The issue is probably a a faulty default binding on the HOTAS function spacebar should be on. That should be either firegun or weapon release. I ran into the same problem when I bound silence Master caution button to spacebar. :)

[GLUTIUS MAXIMUS]

The issue is probably a a faulty default binding on the HOTAS function spacebar should be on. That should be either firegun or weapon release. I ran into the same problem when I bound silence Master caution button to spacebar. :)

 

ill check, but it only gives me issues on the a10c training's, all other training's i have no issues and a10c campaign missions i have no issues

[pocketedition]

Same happened to me, it worked if i pulled the trigger.

[BIGNEWY]

If this is happening during the training, while the text is being read, wait for the speech to finish before pressing the space bar to continue. It should help, the trigger seems to be getting messed up.

 

If you can tell me which mission it is specifically and what version of DCS I will take a closer look

[schurem]

having this problem in the cold start training, VR (oculus) and a Warthog HOTAS. Using the latest release version, 1.5.8.something.

[VFA15-Juliet]

This doesn't work for me in 2.5. Just wanted to do a refresh of General Purpose Bombs lesson. Doesn't matter if I wait for the speach to finish or not.

[Whozdär]

Just would like to add my name here.

 

I too have this very odd issue.

 

I just noticed DCS isn't registering space bar and failing to advance through scripted missions or trainings

Space is mapped by default to gun trigger

so I wanted to check why it's not working, I cleared that keyboard binding

and attempted to re-bind it

but space bar isn't registering at all

Steam / Openbeta

also when I am in the controls menu

I press space.

the expected behavior is that it should automatically jump to whatever space is bound to

well it doesn't

but space bar is registering if I want to rename a mission, or "save as", then I can add spaces in the name

so the key does send input

 

 

I have ruled out 3rd party software. Tried without trackIR and have nothing else running that could "steal" the space input.

 

I have ruled out any USB weirdness by removing my controllers and trying various USB ports.

[Whozdär]

Ok, one more thing I just found out. If I try a modifier + space then I can remap / give input.

 

 

But if I do space alone, it doesn't register any of it.

 

The problem is, even if I set Gun Trigger to LCtrl-Space, that doesn't make any script move forward.

[Whozdär]

Alright. I just found that if I clear my Input folder (renamed it to BACKUPInput) and start the game then I can use SPACE again.

 

So there's something in that folder that the game doesn't like at all.

 

I'm attaching a .zip of that folder so someone at ED can attempt to reproduce.

BACKUPInput.zip

[Whozdär]

Ok, I have found the culprit.

 

It was in UILAyer.

 

I mapped SPACE one day to "RESET VR HEADSET". And that broke the whole game.

 

So if you are coming from google and have the same issue as I had, a key that seemingly has no effect on the game, make sure to check ALL your different planes and UI layers mappings to ensure you have not mapped the key to something else.

 

 

Game should probably tell the user it's mapped to something else instead of not giving any feedback whatsoever.

Or when you're supposed to press SPACE to advance a script, make it actually work would be cool too.

Edited October 9, 2018 by Whozdär

[Nighthawk]

Had exactly the same issue wehen I did the A-10 training missions today (cold start & take off). After hitting the space bar key, the dialogue wouldn't proceed. Changing the gun trigger from LShift + Space to Space only did the trick. Now when I hit the Space bar, the dialogue proceeds.

[JG78_horΛz]

have still the same issue.. tryed startup/Navigation/storepage tutorials (Tryed no other tutorial until now). Every tutorial have this issue... dont want to be rude but the first post was 2016.. thats awkward ED!

[Mad-Mex]

Never had this issue until the last update, hit space at and nothing,,,, wait and wait and nothing,,, some of us newbies depend on these tutorials,,,,

[Ramstein]

my space key is also porked…. I mean really,,,, someone didn't see this before, or just a few of us are unlucky?????? up for hours looking to see what craziness is going on... and see that I am not alone....

[Lixma 06]

I haven't tried the tutorials for a while so this may not work but try giving the space bar a long press rather than a tap.

[Rotor57]

I have the same problems with space bar in Tutorials (A10C). Using trigger button on my Joystick seems to work most of the time. But not always.

[Ironwulf]

I fixed this problem by editing the mission using mission editor.

 

 

Where it has trigger

 

X: START LISTEN COMMAND (554, #, 1, -1000000, 1000000,0)

 

where # is a flag number

 

I changed it to

 

START WAIT USER RESPONSE (#, 999)

 

where # is the same number as the flag above that you removed. (it usually changes)

 

Then any key should work.

[GLUTIUS MAXIMUS]

I cant remember what I did to fix it. i wanna say my space bar was programmed to another function, it had to be programmed to the gun trigger.

[Modano1st]

Tutorial space bar

 

I just jumped into the A-10c training startup video and the training will not continue as it is not noticing that I am pushing the space bar to continue. This is getting frustrating. This is the second module that I have purchased that I can not get through the startup training because of a bug (software issue), the Huey being the other. Any help would be great. Thank you.

Edited February 23, 2019 by Modano1st

[0414 Wee Neal]

I have the same issue on the maverick training mission, as well as your post!

[intx]

I had the same problem with running the A-10C startup training mission running on v2.5.4.27430 of DCS world. Based on an earlier post in this thread, I was about to re-map the gun to LCtrl+Space instead of Space. When I got into DCS World, I noticed that my gun wasn't mapped to any key so I mapped my Gun to Space. I went into the start-up training mission and the space bar was working.

 

I don't know if this will fix anyone else's issue with A-10C training missions and spacebar but you may want to try it if the gun isn't mapped to spacebar.

[Supmua]

OK I figured this out, just happened to run through the tutorials again to refresh my memory and of course nothing worked. In the startup training mission, it was looking for 2nd trigger button (command 554) instead of SPACEBAR. You can change this yourself in mission editor by using START WAIT USER RESPONSE instead of X : START LISTEN COMMAND (make sure to set the correct FLAG number), or just squeeze the trigger button instead of SPACEBAR.

 

If the trainer's sound is cutoff too quickly, you can also prevent this by specifying delay 1-2 sec on the next sound file.

 

A-10C is such an important module and I consider the A-10 training missions (of the old) the gold standard, I'm going to start going through every mission one by one and fix whatever I could.

 

EDIT: Ok pretty much all missions except one or two are broken. Just use the joystick trigger button instead of spacebar or manually change everything that says X: START LISTEN COMMAND 554 to START WAIT USER RESPONSE in the mission editor, and it'll work (do not change other commands, only the one with 554). I think that if your Trigger2 is mapped to Spacebar, it'll also work (mine isn't).

Edited May 20, 2019 by Supmua

[Ziptie]

I also encountered an issue during a training mission for the CCIP / unguided bombs in the A10C last night. Got to waypoint 2 and the space bar input wasn't being recognized by the tutorial. Thankfully was just trying to refresh after some time out of the cockpit.