moggel

That was it. Thanks! I don't have a Warthog or Rhino HOTAS so all those switches are a bit obscure to me. What's the left pinky used for?

As already stated, I'm a noob to the A-10C, currently trying to figure out the system dependencies and function. I've run through the manual start sequence a few times now, in DCS 2.0, Nevada, and there are a few details I just can't figure out: 1. I can't seem to turn on the EAC. The switch moves to the ON position but then immediately toggles back to OFF. 2. When trying to turn on the anti-collision/strobes the switch reacts just like the EAC, and toggles back to OFF 2. Ignoring the above, I've taken off and then noticed that the flight path marker is not presented in the HUD. Can't help suspecting this might somehow be related to problem no. 1 above. Is there some step I've missed somewhere in the sequence that makes these functions impossible to turn on?

I have run this same sequence a few times now and, indeed, the only way I can get the throttles to hop from OFF to IDLE is actually by first moving the stick back and forth a few times. I guess this is not an expected behavior?

Suddenly it worked. I have no idea what I did differently. I was sitting in the pit, just seeing if flaps or ailerons reacted to my stick input (which they didn't) with the APU running. Could it be that I just hadn't waited long enough before? The APU *was* at 100% before, when I couldn't get the engines to start but is there something else I need to wait for, like PSI bullding up more or something?

I didn't find a "repair.exe" in that folder (nor in the 'bin' sub folder within). I did try running a command console in the 'bin' sub folder though, and then "dcs_updater repair". I let it run and then tried again but the throttles remain in the OFF position no matter what I do. :huh:

My keyboard does not have a RWin. I have double-checked the bindings and also tried to clear and rebind them, as per the following screen shot: (screen shot) APU is running at 100% before I try it but the throttles remain in the OFF position. Running the exact same sequence in 1.5 does fire up the engines as expected; I only see this in 2.0. How do I perform a repair? Do I need to uninstall 2.0 completely and then reinstall, or is there a better way? [EDIT] Not sure why the screen shot isn't working. I added an image with a link to a screen shot that I've uploaded to IMGUR. Using the URI in the browser address field works fine but not as a link here.

I'm starting manually. It's just that the engines won't start up when I press RAlt+Home or RCtrl+Home.

I'm a noob, trying to learn the A10C but I just can't crack how to start the engines in 2.0. I've read up on the sequence and tried it without any problems in 1.5 but when I press RAlt+Home (or RCtrl+Home) in DCS 2.0 nothing happens. The throttle gauges remain in the OFF position and the fans doesn't move an inch. The same startup sequence in 1.5 works fine though. I've double-checked the key bindings and they really are RAlt+Home / RCrttl+Home to ignite engines in both versions. Is this a bug in 2.0 or is there some additional step they've added that I haven't found out about?

It was the A-10C navigation training mission so the nav config should be the default (EGI, I think). Are you saying I can't just put the marker (in HUD or TAD) somewhere in the terrain, such as the bend of a river or a crossroads, and make that a SPI? Do I need to point at a building or a vehicle or something like that?

I was using the HUD in this case. I slewed little marker to someplace on the ground and tried L.Ctrl+UP (and also TMS-UP long command) but nothing. No marker on the HUD or the TAD. The instruction video never progressed from that point either so I took that as an indication it didn't work. Is there something else I need to do? Are the commands different depending on the SOI?

Hi everyone, I'm in the progress of learning to fly the A-10C. I was going through the training videos but couldn't get past the section about how to set up a SPI. According to the videos, and what I've seen in other places, the SPI should be set by long-pressing the TMS up key, or L.Ctrl-UP. Neither works. What happens is that the left MFD goes black for half a second but I've seen no other effects. I assume this is me misunderstanding something, since a search for the issue here at the forums came with nothing. Can anyone please spare a few seconds straightening out this noob? :helpsmilie: Cheers

My latest experiment had me removing the profile all together. I then tried binding the stick's buttons directly in the sim and that works! It means I can't use the X52 MODE feature but I guess I can live with that.

Yes, when programming the POVs as buttons my idea was to only support RDR DES in modes 2 and 3. When that failed I allowed all modes and finally I removed buttons programming and set the POV to "unprogrammed" to set it in the sim instead. None of these approaches have worked out.

Yup, those are the bindings I tried. Those and the "button" approach (through the Mad Catz editor) and so far I haven't been able to move the RDR DES a single millimeter using the X52 HOTAS. I'll try a complete uninstall/reinstall of everything X52 and see how that goes. If not, I guess it's that final incentive I needed to motivate buying a Thrustmaster Warthog, finally. So, keep your fingers crossed this doesn't work. :music_whistling: :joystick: Thanks a lot for your effort to try and help. I really appreciated it!

Ok, I tried binding the POV1 hat to RDR DES with pinkie as MODIFIER but no luck. I then removed the settings and tried the POV3 hat instead (as buttons) but still nothing. The funny thing is if I bind keyboard to RDR DES in the Controls editor I do get the correct keys (already bound to RDR DES). But when I close Settings and get back to the pit nothing happens when I press POV3. Isn't the X52 supposed to act just like the keyboard when configured to? Weird ...

I must've been blind! :doh: I'll try this out as soon as I get back to the sim rig. Cheers mate!

Ok, I have updated the SST drivers but that didn't help. I also went ahead and deleted the F15 config/input folder before I ran a repair. The configuration is now like in your screenie, with the POV hat tied to view (which isn't very useful to me; I rely on the TIR for looking around). But how do I add the pinkie to "MODIFIERS" in game? Thanks

Ok, I turned off the TIR and retried it but nothing happens in the sim when I move the POV. The mouse is what's to be used for looking around. Also, I double checked the binding in config and nothing is bound to the POV in sim.

Good point, but nothing happens at all, within the sim, when I move the POV. I do have a Track IR active but I don't think that would interfere with any bindings the sim might support.

Hi everyone, Sorry for posting this here as I guess it really belongs in the Bugs >> Controllers section. But for some unknown reason I'm not allowed to post new threads in there. I have no idea why but, hopefully, some mod could move this post to where it belongs ... My problem is: I've just recently fired up the sim again after several years, as I would like to get back in shape before DCS 2.0 is released. I've started softly with the F-15C, just to get going, but I'm having problems getting my HOTAS operational. I have programmed my trusty old X52 POV as buttons to control the radar cursor but it doesn't work. I have double checked that the programming is OK by opening Notepad to check the output as I push and pull the POV button and everything looks as expected. But in the sim the radar cursor isn't moving at all. I have tried this both in v1.2 and the v1.5 open beta with the same result. I then tried to remove the programming and bind the POV directly in the sim but that's also not possible. The binding UI doesn't react at all when I push/pull the POV on the stick. So, either I've goofed up and missed something very basic somewhere or the sim just doesn't work properly with the X52. Any hints or suggestions are appreciated. Cheers, Jonas

Thanks for the info and links. This is exactly what I hoped for! It's gonna be a great!

Will it be possible for third party developers to produce new maps? if so, what would it take to do so, in terms of tools and licensing? Would be great to see more maps coming up, as part of new modules.

I re-installed and now it all seems to be ok. By the way: Is it possible to use the same install from two different Winbdows bootups? I have two Windows configurations and would like to be able to run DCS World from the same folder location. I imagine that's entirely possible if modules configuration etc. is loaded from local files (not from regitry). I do understand that saved games etc. is always on a per-windows boot (profile) but I can live with that. Cheers

Yes, views are enabled both in the game options and in the mission. I might add that NO views seems to be working. Tapping the NUMKEYS for example have no effect, despite the options tying them to internal views. I'm considering a re-install. What's the easiest way to unregister my serial numbers so that I don't loose an install? Will uninstalling a module from the "MODULES" tool also unregister the serial number and increase the no. of available installs?

Thanks for the tips. Unfortunately it didn't work. If there's a problem with the input config files, is there some trick to retain our settings as new versions are release, or are we left to manually recreate them every time?