N22YF

Are you sure you're pressing the right button by the third line (which is the first right button), and not the third right button (which is R7, by the seventh line)? R7 is copy. I originally made that mistake because I didn't realize what button R3 actually was, since it's never explained in the training mission and I couldn't even find it explained in the flight manual PDF (I had to do some Googling to figure it out).

This is an odd one: when you start a mission set to takeoff from runway in the MiG-29A/G, if you're flying for a BLUE side faction (Germany, Poland, Ukraine, etc.) then you get the notification "Arrival. Parking" and the ATC transmission "taxi to parking area". The score window shows that you took off and landed right when the mission started. This does not happen if you're on a RED side faction (Russia, Iran, etc.), and it does not happen in the MiG-29S (or any other plane that I've noticed). Here's a demo: I'm attaching a track file and my DCS log. I'm running version 2.5.5.41371.1. MiG-29G land on takeoff.trk DCS log (MiG-29 land on takeoff).zip

I think this is just a bug in DCS with the MiG-29, not any limitation of consumer FFB technology. The Su-27 autopilot works the same way (the stick physically moves) and has no issues for me in DCS with FFB (I use the Sidewinder Force Feedback 2), but I have the same issues as you with the MiG-29.

I have a Sidewinder Force Feedback 2, and the MiG-29's autopilot is unusable. When I activate an autopilot mode and don't touch the stick, the trim center moves in the controls indicator, but the stick remains motionless. However, if I move the stick at all, the stick then moves to give extreme pitch and roll inputs, sending the aircraft out of control. If I grab the stick and try to level the aircraft, the autopilot fights me. I have no problems with my Logitech Extreme 3D Pro Joystick (no force feedback), and I haven't noticed any problems with any other autopilots, including the Su-27's, which I believe is similar and works beautifully. This is a problem on all MiG-29 variants. Here are a couple video demonstrations: I've seen this mentioned tangentially in other threads (e.g. here and here and here), but I didn't find a dedicated thread about this issue, so I thought it would be a good idea to start one. I'm attaching a track file, the DCS log, and my DxDiag info. Would love if this issue could be sorted out soon! It really makes the MiG-29 frustrating to fly, since it's impossible to trim it perfectly so I'm always having to correct to maintain altitude and can never take my hands off the stick. MiG-29S autopilot.trk DCS log (MiG-29 autopilot).zip DxDiag.txt

The only one I've found is this one which was translated by a robot. Better than nothing though!

Thanks Dudikoff and Ironhand! I don't think I've seen any mention in the manual of a dichotomy between ОБЗ and СНП modes, so I'm wondering if СНП could even be a sub-mode of ОБЗ (that is, you're still in ОБЗ when you're operating in СНП mode). Are you sure it's even possible to operate in ОБЗ and not in СНП mode? I looked over the discussion of the ЗАХВ АВТ-РУЧН switch (although did you mean 5.1.5 instead of 5.1.7?). I read it as more of an option of СНП mode—in ОБЗ mode in DCS you still have to manually aim the radar as opposed to it automatically following the selected target in СНП—but perhaps that's the closest thing the Su-27 has to a manual mode switch.

Thanks for the help, Ironhand! Ah I was just referring to DCS commands by their names in DCS - not implying that I expect the Su-27's radar to necessarily operate like a Western aircraft's. Looking at the Su-27SK manual again, I see that the list of radar modes in 5.1.2 includes СНП and РНП (STT) but not ОБЗ, so it would make sense that СНП and ОБЗ are not separately-selectable modes as they are in DCS. Interesting! (I do also wonder how the MiG-29S switches into СНП2 mode - I don't see any switches for this sort of thing on its radar panel - but I suppose DCS could be inaccurately modeling that as well.) Right, the range scale! Not all modes have a designator cursor, so relying on bumping that up and down wouldn't be sufficient in all cases. But I could indeed see it being tied to another action as you suggest, or perhaps automatically set in different situations (such as different modes) without a way to manually adjust. For example in (which of course could be different than our -27S), the range scale appears to me to be set at 150 km (which is the same range scale shown in figure 21 in the Su-27SK manual of the HUD in ОБЗОР mode) even though his target is much closer.

"Doesn't have a HOTAS design at all" is a bit of a hyperbole - this still counts as HOTAS, although of course not to the extent of modern fighters. However, note that the original F-15C (pre-MSIP) was almost exactly the same in its HOTAS functionality: almost none of the controls for radar modes, radar scanning (range scale, azimuth scan, elevation bars), radar frequency, navigation, autopilot (except disengage), etc., were on the stick or throttle. (The only real advantages the original F-15C had over the Su-27 is that you could switch into WVR A2A modes—i.e., vertical scan and boresight—and adjust radar elevation via HOTAS controls, but all other radar controls were adjusted via the radar control panel on the left console.)

Thanks for the prompt reply! However by "RWS/TWS mode select" I meant choosing RWS or TWS mode, both of which are operated under the "РЛС" mode of the mode selector in the diagram you linked.

A couple more questions! How does one perform these functions in the real Su-27? Radar RWS/TWS mode select Display zoom in/out (i.e., changing the distances shown on the HUD and MFD) Thanks!

The MiG-29G HUD displays distance to the next waypoint in kilometers, although the speed and altitude on the HUD are in knots and feet, respectively. However, the HSI waypoint distance indicator, which is labeled "KM", displays the distance in nautical miles. This is pretty confusing and I believe incorrect - my understanding is that both the HUD and HSI should display the distance in nautical miles (and the HSI label should read "MILES" instead of "KM"). I'm running 2.5.5.41371. In this screenshot, the HUD reads 25.4 (km) and the HSI reads almost 14 (nm): Here's a 2007 picture of a Polish MiG-29G cockpit, but my understanding is that the HSI labels (if not the whole cockpit labeling) is the same as in German service: (While I'm on the topic of MiG-29 cockpit issues, just wanted to mention in passing that many of us are still eagerly awaiting the promised return of a current waypoint indication - navigation without that can be frustratingly difficult!)

I figured it out! This is an abbreviation for "уборка", indicating that pushing the airbrake switch forward retracts the airbrakes. The same abbreviation is seen on the airbrake control of the MiG-29 throttle.

Ah. When I was trying this earlier, that was not written anywhere. Thanks. (Would have been thoughtful of them to release this information at the same time the free trial began. But I guess it's free anyway, so I can't really complain.) Well the other free trials (except the JF-17, which, as you said, is understandable) were available on the stable release. :dunno:

I'm trying to fly the A-10C for its free trial. When launching DCS, the module manager notified me that I could install the A-10C now, but after installation, it asks me for a serial number. When I exit out of the serial number dialog box and try to start a mission with it anyway, I'm not able to fly the aircraft (presumably because I didn't give it a serial number). What do I need to do to be able to take advantage of this free trial? I'm running the standalone stable release of DCS. Thanks!

Thanks, this worked for me too! A bit of a pain since I run the standalone version, so once in WMR for SteamVR I have to then open the desktop to launch DCS, but definitely less of a pain than having to launch DCS twice in a row (the method I had been using). Thanks! I didn't understand exactly what you meant (did you mean: connect to a PCI-e USB expansion card?), but I tried connecting my MSFFB2 to different USB ports and I found one that worked! I had been connecting to a USB3 hub, but when I connected to a USB2 port that's wired directly to the motherboard, it worked! Go figure. So, problem solved for me too! :thumbup: For me this problem is only in DCS in VR. No issues in other games (e.g. Il-2) with VR, and no issues in DCS without VR.

Ah I have the same problem! It's A-10A Camp 6B.miz ("Interdiction"). I'm using MadDog's repaired version. I don't have any problem with the A-10A instant action mission myself (where I'm able to attack from a reasonable altitude), but I've tried this mission literally dozens of times with no success. There are two SA-11 sites, each with four launchers, so it's pretty impractical to do anything besides stay low, as far as I can tell. And my wingman is useless because he invariably gets shot down right away. I even tried taking out the SA-11s first (which I don't think was the intent of the mission designers), but I couldn't find a good way to do that because they're covered in fog and can't be located until quite close. I was really enjoying this campaign until this mission - if anyone has any pointers, I'd love to hear them as well!

Glad to hear it was useful! (And by the way, thank you for your excellent English cockpit mods, which have certainly been very useful for me!) Also, I just edited my post to add some more color on the "КЛЕН ПЗ" button on the Su-25T throttle - after more thought and research, I'm thinking it's mislabeled and is actually the "target lock" button.

Here's a list of all the controls on the Su-25 and Su-25T stick and throttle (unless I missed some), and my best guess at their corresponding mapping in DCS. If anyone finds any mistakes here, please correct me! Su-25 and Su-25T: Stick: Main trigger ("БК Огонь"): cannon* Folding trigger ("БК Подвеска"): weapon fire* ТРИМ hat (top center): trim Lower left hat: target designator (TDC) slew Throttle: МЕХ КРЫЛА switch: flaps (really only to switch between retracted (ПК) and maneuvering (МК) settings; the takeoff and landing setting (ВПК) can be activated by the three-position flap switch on the left side of the cockpit) РАДИО button: communication menu ТОРМ. ЩИТКИ switch: airbrake 0-1-2-3-M dial: target box size/funnel target wingspan/gunpod elevation Su-25 only: Stick: НУЛЬ АСП button (top right): laser designator on/off** C 60/Б П switch: weapon change Unlabeled top left white button: I don't think this button exists on the real Su-25 stick? Here's an example. (I have seen this button on the Su-25SM stick, though. Does anyone know what it does?) Throttle: КЛЕН ПЗ button: laser designator on/off Su-25T only: Stick: ОТКЛ САУ button (top left): autopilot disengage СБРОС ЦЕЛИ button (top right): target unlock В В (up) switch position: longitudinal missile aiming (i.e., air-to-air) mode В П (down) switch position: air-to-ground mode Throttle: КЛЕН ПЗ button: target lock*** СБРОС ЛТЦ button: chaff/flare There's also a "УБР" label on the throttle (under the КЛЕН ПЗ label), with an arrow pointing forward - anyone know what that's indicating? I have no clue! *On the Su-25, depending on the position of the C 60/Б П switch, the main trigger fires either rockets/missiles or bombs and the folding trigger fires either R-60s or the cannon. Not sure how the triggers function on the Su-25T, but I'd guess the same as the Su-27 (i.e., the main trigger is the cannon and the folding trigger is everything else). **According to my understanding of running this post through Google Translate, the КЛЕН ПЗ button is used to activate the laser and the НУЛЬ АСП button only deactivates it. ***I suspect this is mislabeled in DCS because the Su-25T doesn't have a Klen (Клен) system! (It's replaced by the Shkval system.) It looks like in older versions of the game, this button was labeled something else - I've seen the letters "ИВЯЗКА" sticking out under the flap switch in pictures/videos ( ). Perhaps the full label is "ПРИВЯЗКА"? According to this post, a "sight stabilize" button exists on the throttle, so I think this must be it. (But if so, how is the laser designator turned on/off?)

Oh very nice! Well hey, I figured it out! The "СБРОС" target unlock button is actually a little button tucked away on the front of the throttle above the afterburner pins, which is hidden from view in pretty much every existing picture of the Su-27 throttle, including the one above (it's just barely out of sight under the red box for the button labeled "RADIO" there). Here's a labeled screenshot: And I corrected that labeled throttle image that was posted earlier in this thread: Thanks for your help, Ironhand! (Curious that the lock/unlock controls are so different for the Su-27 and MiG-29. On the Su-27, lock is a thumb throttle button and unlock is an index finger throttle button, but on the MiG-29, lock is an index finger throttle button and unlock is a button on the stick. I wonder why?)

Wow, where did you find this English version? The only English version I've found is translated by a robot and is not as easy to understand - for example, that sentence is written as: But I don't see this "СБРОС" button anywhere on the throttle? The only thing close is the "СБРОС ДО-ЛТЦ" button, which I understand is for deploying countermeasures (as discussed in section 5.18 of the manual). Maybe this is a difference between the Su-27SK and our Su-27S?

Thanks! But where is that button in the actual Su-27's cockpit? Thanks Ironhand! What documentation are you quoting? The button marked "unlock" in that image was discussed a couple pages earlier in this thread and is actually for unlocking movement of the throttle into the afterburner range:

Thanks everyone for all the great info in this thread! I have a question along the same lines: how does one perform the "return to search" (target unlock) function in the Su-27? On the MiG-29, there's the white "break-lock"/"сброс" button on the stick, but that's replaced with the BVR/CCM switch on the Su-27 stick.

Wow that works for me too! Спасибо! Hopefully this issue will be sorted out soon so we don't have to go through all these steps.

Ship wakes are showing up super small for me - compare the attached screenshot to . (This is the third mission of the Su-33 Sea Dragon campaign, which becomes incredibly difficult when the speedboats don't have large wakes! The speedboats are almost invisible for me.) I have a Zotac GeForce GTX 1080 Ti 11GB and a Samsung Odyssey+ headset. dcs.log.zip

My force feedback joystick works totally fine when I play using my monitor, but I get no force feedback at all in VR. I've tried multiple aircraft - no difference. I found a Reddit thread where others were having the same problem (https://www.reddit.com/r/hoggit/comments/a6amfx/no_force_feedback_while_in_vr_vive/), and someone found a solution for the Steam version of DCS: make sure DCS and SteamVR are closed; then launch SteamVR, and then DCS (in that order). This solution is a little annoying, but works perfectly for me with the Steam version. However, I recently switched to the standalone DCS version (so that I'll be able to take advantage of ED Miles), and I haven't found any way to get force feedback working while in VR with the standalone version (I don't think I can launch standalone DCS from SteamVR?). If anyone knows a workaround, I'm all ears! But would be good to address this bug so force feedback works in VR regardless. I'm using a Microsoft SideWinder Force Feedback 2 joystick and a Samsung Odyssey+. DxDiag.txt dcs.log.zip