PawlaczGMD

Increase the target box size to envelop the whole helicopter, including the rotor. If done on the screen, you have to aim ahead of the target, as there is a delay after pressing the lock button. Otherwise, it can be done with the HMS, put it over the enemy and hold lock until it's captured. You still have to adjust the box. Another trick is to fire in manual mode with no lock, and keep HMS on the target. Try to lock it, but if you don't manage, you might still hit thanks to the proximity fuze. You of course want to be in AA mode!

The Cobra kills are tricky, but doable. I barely managed on 2nd try. Some tips: -Disable overhead fuses for one pair of rocket pods, or as desired. No need to fire all 3 pairs at once. It's better to give you extra runs. - I initially do a rough spread to make sure all infantry is killed, which is not hard. Then, you have to be quite precise to hurt the Cobras, as DCS explosions are so weak. - Lwin+H to show gunner rules of engagement. Switch him to open fire. The heavy MG can actually hurt the cobras a bit, if you run out of rockets, you can finish them off. - Don't fly past the enemy position into the city, there are SAMs. Turn away after each run. - At the end of the day it is down to your skill. It's not that unreasonable to kill 3 armored cars (well, you only need to kill 2) with a full rocket loadout, but it's quite hard in this bird. Practice the training mission to get good. I also recommend decreasing sight depression to 40-50 mils. The default is set up for longer range, but you will be very imprecise.

I've just finished the campaign, and I really liked it. It gives a good mix of combat and civil (Mi-8) missions to play. The civil missions are not that easy, as they can require really precise landings in bad weather. All the triggers, dialog, etc, worked for me, which is something to be mentioned with DCS campaigns. The voice acting is of good quality, and the writing and story are reasonable. Some things that could be improved: -The briefing is often not written very well. I found it confusing, and it was not giving me enough information on what the plan of the mission is. In missions with more complicated plot, I sometimes had no idea what's going on. The kneeboards could also give you more info, and the maps are in Russian only. -The music doesn't really work for me. It is playing too often, and cuts off with the dialog. It could be nice to play it during moments where not much is happening, once or twice per mission. I know you can tune off the radio, but still. - As for comms, to add some things to do, especially in the civil Mi-8, it would be nice to implement "real" comms - you have to be tuned to the right radio and frequency to progress the plot? -I would like a few more Mi-8 combat/CAS/CSAR missions. We did enough safe landings already! - A few bugs I've noticed. The first 2 or 3 Ka-50 missions don't have satellite navigation enabled. Unless it's intentional? My wingman was not armed in the penultimate mission, and even if I selected a loadout from the ME for him, he refused to attack datalink targets. This is probably DCS AI beyond your control, but check the loadout? He also did nothing in the last mission...

This is a separate and known issue with Winwing. But it shouldn't cause the game to be completely and permanently unresponsive to inputs.

I don't have the Harrier, but this sounds perfect.

Fixtaking doesn't fix a poor alignment though. You will still lose accuracy way faster than if you were fully aligned from the start. I have actually found that it's almost useless to do fixtaking with quick alignment, unless you do the trick where you use your own GPS coordinates, and even then it's questionable. It's a waste of time to find a spot and fly over it. With no fix, the accuracy is good enough to navigate, but not good enough for anything tactical. Taking a fix basically doesn't change this. As for the mission editor option that fixes this, there are two issues. 1. It's not under your control. If the server owner didn't bother to tick this, too bad. Also, some campaigns and missions don't use this option. Sometimes you can edit it yourself, but it's a pain. 2. The option is a definite cheat (rather than "simplification"), because it completely eliminates INU drift. That's not realistic behavior. Some people don't want that. How to fix this: Create an option to tick in the "Special" settings tab for the Ka-50. This will make you start with precise alignment, and have realistic drift without waiting. It will override the mission editor cheat for no drift at all. This should be fine to override, as it's less cheaty.

Not to excuse winwing if the angle is indeed opposite to what it's supposed to be, but I am simply using the throttle rotated by 15-20 degrees counterclockwise. This matches the rail angle of the throttle on many planes, and is comfortable for me. I do agree that the angle is a bit uncomfy if you have the throttle unit straigh.

Public service announcement. I may have figured out what was causing this issue. I believe it was caused by a hardware instability in my system. Specifically, RAM was causing failures. Since tuning my RAM settings in BIOS, I have not yet experienced a disconnect. It's not a definite proof yet, but here is what I recommend checking. - Download prime95 and run the blended stress test for a few hours. If you get any errors, your PC has a stability problem. - Download furmark and run the gpu burnin test for a few minutes. If you crash, you have a hardware issue. - Download and run memtest86 with default settings. If it finds memory errors, you have memory problems. I have contacted my RAM manufacturer support, and they have given me settings to try at lower speed. This has improved stability, and while before prime95 and memtest were erroring, they are now fine. Alternatively, try setting your memory speed to 2666 Mhz, which should be more stable. Explanation I was given: mem sticks are sold and tested in pairs, but I have 4, so they are not tested to work together in the factory. Indeed, any pair works for me at 3600 MHz, but they fail when I use 3 or 4. I am currently running 4 sticks at 3200 MHz. Just try the tests above, and try to fix the issue as appropriate. See if the Winwing still disconnects.

OK, I didn't know that. Most other campaigns I've played had duplicate channels across the radios, or had separate sheets for the 2 radios. I know that the RIO radio has a wider freq range. It would help if the kneeboard/briefing specified the radio, because channels 2-4 work just fine on the pilot radio.

Yeah, that was it. Looks like only the RIO channel 1 is tuned to Flight.

Thanks, I was using my own radio for this. I usually have Ch. 1 on the front radio, and something else on RIO's (AWACS). I will check if the frequencies are different tomorrow. I am aware of the different bindings for the two radios.

Got it, it makes sense. I assumed that the salute command is "gamified" to let them know to launch... somehow. So to command launch, I switch on external lights instead?

I might not be correct on the intended way to signal launch to the crew at night. But here's what looks like a bug to me: At night, if my external lights are on, the crew will not listen to my salute command. They will forever signal me to spin up the engines. However, if I turn off the external lights, then the salute command/keybind will work. It will also cause the ext. lights to go on at launch automatically.

I have a problem with this campaign. My wingman is not communicating on channel 1. He does not reply, call out targets, or listen to commands. I have done the first 2 missions like this, but I am barely making it- running out of missiles. My wingman does nothing, just follows me passively and does not shoot. I can contact everything else fine, AWACS, carrier, so it's not my comms issue. It's just the flight channel that doesn't work. Any ideas?

OK, the fight in the storm with multiple Mig-21s without Phoenix was pretty tough. Gotta respect the 21.

Yes, I have played them before, and they are much harder! I think I have read somewhere that this is the suggested order, so I was under the impression that Fear the Bones is the hard one. I guess not.

The campaign is really fun and immersive, but I find it a little too easy. For an 80s movie homage, there is not actually that much action in the missions. And especially in the missions where you're flying in a 4-ship, the F-14 AI is a killer against the AI Migs. I find that you need to rush in to get any kills before they clean everything up.

Yes, don't use any wingman commands in any missions with ROE. E.g. "Cover me" will cause them to be aggressive. I've had this same issue with another campaign. Just don't touch your wingman.

MT is a different .exe ST is in bin folder, and MT is in bin-mt folder. This is separate from open beta. You definitely want MT, I am unable to play in VR without it, as there is horrible stuttering. You need to adjust your expectations for the graphics. Q2 is an old budget headset with relatively low resolution. In-game settings can't overcome this issue. I tried playing with Q2 and also found the graphics to be too bad to have fun, just a proof of concept. I purchased Pimax Crystal which has significantly higher res, and the visuals are a LOT better, but still have room to go. DCS is extremely demanding on VR, as you need to be looking both at cockpit up close, and spot objects very far away. I just don't think Q2 is usable for DCS. If you like the VR experience, at least get the Q3.

Thanks for giving me a better idea on what to expect from this module. While it looks like it won't fill the role I was hoping for, I can now see how it will fit into Cold War scenarios with restricted loadouts.

I was really excited when I heard that the full fidelity 29 is coming. Red is lacking a modern-ish fighter to counter F-15/16/18, which makes multiplayer balance rough. So most people just fly western planes, which makes the combat unrealistic and a bit boring due to the symmetry. But then I realized that the 29 will not really solve these issues - at least if it is equipped similarly to the FC3 version. Now, it will still be a great module, and I will be getting it, but I wonder how this plane will fit into the game. If it won't have a datalink or fox-3 missiles, it will have a really rough time against western opponents. The F-15/16/18 will load all AMRAAMs, and that's it for you - only niche way of attacks will be feasible, or if you want to handicap yourself to show off skill. On the other hand, earlier western fighters like the F-4, F-5, etc, will not be flying in the same era, as they are not capable enough - against the current cold war lineup, the MiG-29 is on the other hand too good. Against an F-14, the fight will be a lot more even, and that is perhaps the only approximately on-par opponent for the MiG. So, was there any info released on the systems and armament that will be equipped? If it will carry a datalink, and R-77, or maybe R-77-1, that would make it fit so much better with other fighters in the game. And I'm not trying to say that modules that don't fit into the metagame should not be made - but this is the entry that gave me some hope of bringing modern red up to par!

If you lose an engine, you need to land ASAP, you're not supposed to be taking off...

This seems to be the underlying issue. Yes, you can argue that the failure is reasonable given the documented G limits. But literally no other jet experiences this type of failure this easily, while having similar documented G limits. So the question is, why does it only happen to the F-5? Clearly, either something is unique to its design, or it is modelled differently.

I have the 7900 XTX, and I'm running a Pimax Crystal, which has a significantly higher res than Q3 (nominal 2880x2880). I have most graphics settings maxed out, running at 1.0 res scaling, and with foveated rendering, I'm getting 70-80 FPS in most situations (except busy airports). So you should not encounter any bottlenecks with this GPU using Q3.

FYI, there is an indicator button to the left of your TACAN knob. "PLT" uses your setting, "NFO" uses Jester's. The front and back seat TACAN knobs are not connected. Click this button to switch.