CaptainCernick

When starting up as the QRA flight in M12, you start with a partially prepped cockpit. You're supposed to just start the engines, perform the fly by wire test and go. However, the HUD seems to disagree with the jet being take off ready. I get limited symbology and 'Horizon Secours' on the HUD after take off. I tried to fly the steam gauges, but the workload quickly became more than I could handle in IMC I think it might be to do with INS alignment as I'm also getting a yellow warning message on the INS display. I tried pushing the INS through a stored position alignment procedure, but that didn't seem to fix the issue. Haven't tried doing a full alignment as waiting 8 minutes for that to complete would probably mess with the entire mission's timing. Anyone ran into the same issue? Any tips?

I got past the issue, now tackling Mission 12. I think the solution posted above by Akir Nakesh worked for me: try cycling the radio channels before contacting Reaper.

Same issue here unforitunately. I couldn't do the radio check despite having ground power and being on channel 1 on both radios. Pressing space bar when prompted just didn't seem to generate a response. I tried continuing without the radio check, I could hear ATIS and contact ground as expected, but I could not hear REAPER's instructions on Red 1 channel. Also wanted to give a quick message of appreciation for the training missions and Caucasus campaign included with the M2000. This is the first DCS module that seems to really 'click' for me. Partly thanks to the intuitive cockpit and HUD design (why do other aircraft not have acceleration chevrons? They make formation flying so much easier!) but mostly thanks to your excellent campaigns gently introducing or refreshing concepts in an immersive and engaging campaign.

Hi all, Getting back into DCS after a while. I just got myself Black Shark 2, so now I have another aircraft on top of the A10 to make very expensive craters into the ground with. :pilotfly: I remember having the ministick on my Saitek X-52 programmed for use as the HOTAS slew command of the A10, so I felt it was only natural to use it for Shkvall slewing. The problem is, after my recent reinstall the ministick doesn't seem to work correctly in DCS. I think I've set it up correctly in the profiler (bands, correct keybindings etc), but when I test them out in either aircraft, it doesn't do anything. Direct inputs using the keyboard do work. The funny thing is, the controls configuration of DCS World seems to recognize the input. When I use the ministick, the controls page jumps immediately to the correct entry. Any idea what I might be overlooking here? Regards, Jef

I assumed this was only necessary for engine start. Noted. Ah... so this is where I went wrong the entire time. I thought when the "nav" option on the align page had it's little bullet next to it, alignment was complete and I could activate "nav" mode. You'll see me doing this in the pre-take off checklist. I don't know why, but in other sims also, I always check trim while holding short. I'm using the checklist that came with the manuals. I'm starting to feel too confident now and I'm starting to rush things and do stuff by memory (with the obvious result of forgetting stuff) On the take-off front, things are looking up. I'm rotating later and mytake-offs are smooth now. IIRC, the take off tutorial tells you to rotate at 110 kts, and that got stuck somewhere. Those are great! Thanks for the tip.

Thanks for the replies! Alright, so rotate later is the message. I'll keep it in mind. The track of a rampstart and take off are attached to this message. Keep in mind, take off weight in this track is pretty light. No external stores, no gun ammo, 60 percent fuel. NWS disengaged at 65, I attempt to start rotating at 120 kts. (please overlook the zigzagging on takeoff, I'm still having trouble controlling the rudder/nosewheel during take off. It's just so sensitive) As for the EAC switch, you'll see me trying to activate it twice: first after EGI has aligned, nav selected in CDU, EGI navigation enabled, SAS switches on and again when I've taxied some distance. It wouldn't work. Rampstart.trk

Thanks for the swift reply! I have tried turning on EAC during taxi, but it still won't work. Makes me think I am forgetting something important during startup after all. I'll try again and triple-triple check my checklists. Maybe rotating later could be the answer, I'll give it a try and get back.

I recently took up flying in the A10C again and I'm having a lot of fun training. Looking forward to some combat missions later. But I'm having some issues with the sim, and I'm not sure wether I or the software is to blame. The first has been with me since the beginning. I call it the 'sticky nosewheel issue'. Basically, rotation during take off is very difficult to control. In my take off run I speed up to 110 kts and start pulling back gently on the stick. The nosewheel does not seem to want to come off the ground though. Ultimately, the stick is full back and still no rotation (even though I should be well past Vr by now). At about 140 kts, the nosewheel suddenly "unsticks itself" from the runway and the aircraft leaps into the air violently. It's not a pretty sight and I'd like to do it right. Am I doing something wrong or is it something else? I already checked my joystick axes (using a Saitek X-52) and they register full deflection. The second issue wasn't there when last I played DCS A10 (Patch 0.6). The EAC switch just doesn't want to stay in the "on" position. I know it wont unless EGI is aligned, EGI navigation is selected and SAS switches are engaged. I triple check these things every time I do a rampstart, but still no EAC. I'll record a track and upload it here later. Thanks in advance for the help!

Hi, I recently bought the DCS A10C beta, but I'm unable to access the A10C beta forum. I made sure to enter identical e-mailadresses in both profiles, logged out and in again a few times, cleared my browser cashe, tried using a different browser, still no success. There are a few issues with my beta I'd like to resolve, so I'd really like to browse the beta forum. Thanks