Warmbrak

Great design. Expensive smart weapon, but no USB connector cable to power the weapon long enough to overcome a launch abort. ;-)

Thanks, this was the issue. I should have known better, as I had to do this with the UH-1 and Mi-8 not too long ago. Looks like these profiles are not updated over time, and somewhere over many updates, errors creep in. Works perfectly now.

I haven't flow the A-10C in ages and flew her again this week on the current Open Beta (have not tested in Stable). Coolie Hat up is supposed to make the HUD SOI independent of what are shown on the MFCD's, but if either the TADS, TGP or MAV pages are on either or both of the displays, Coolie Up is not able to make HUD SOI. The workaround is to flip through the MFCD pages with Coolie short left and right to get them on the DSMS and CDU pages (or any other non-sensor page), and only then will Coolie up select the HUD as SOI. Anyone else ever had this happen to them?

I just came here to see if anyone has posted something about it. I have the exact same issue. Suspect ground crew forgot to pull a safety pin somewhere. If this is a bug I hope there will be a hotfix as a week without GBU-12's is a week without, well, GBU-12's...

It is not the view that makes you feel that way, it is the fact that you are not sitting in a real F-16 cockpit, looking at a flat monitor. The 3D model is correct as has been clearly demonstrated. Unless there is a way to replicate the exact camera settings inside DCS, it is not going to look like two parallel lines. We all paid money for this, and most of us seem to be happy the way it is now. It doesn't make you wrong, but you have to acknowledge facts and not how it "feels".

This happens every time. If I take up 4 x GBU12's and drop the last one, the TGP moves off target abruptly. I noticed that the mode is switched from CCRP to CCIP as soon as the GBU leaves the pylon, which will result in a guaranteed miss. Temporary Solution - Quickly switch back to CCRP with nosewheel steering button and lase the target. If caught quickly, one can still hit the target. ${1}

Best way (if you don't have a physical detent on your setup) is to monitor fuel flow. When the fuel flow numbers start spinning up like a slot machine, the afterburner has engaged. Usually when the PPH is under 10K, you are in the MIL power or lower range. With afterburner on, it could be well double or much higher than that number.

I know the emergency jettison is not working, but can't we jettison external fuel tanks at all?

Have you actually installed the addon? Modules are installed from the four squares icon at the top left of the main screen.

Fortunately got mine for $ 99.09 AUD :pilotfly: I only tested dogfighting against AI so far: expert SU27, MiG-29 and MiG-21 guns only. SUe was not too bad, 29 was a real hand full, but Fishbed was the worst. For some reason that thing could hold its energy extremely well while I was struggling to get my speed back above 250kts without it getting on my six. I once tried to extend from the outside edge of a level turn and that Fishbed got a pilot kill on me with a short burst less than 15 seconds later. I really need to stick closer to the corner speed! I only wanted to have a quick look at the module, and next thing I know four hours have gone by... Thanks for making such an immersive Viper for us ED - I really look forward to how this one grows!

If we get Walleye, I will be dumping my JDAMs, GBUs and Mavericks and ONLY use this weapon. Fire and forget is so yesterday.

I haven't flown the Mi-8 in ages and took her out in the open beta. The weapon release button in highlighted in red and does not function - I can't release weapons at all. Any idea on how to fix this? UPDATE: This happened with my UH-1 as well. The recommendation was to delete the contents of the input folder for the offending aircraft, and set up the axis and button assignments again. This seems to have solved the issue. It would have been even better if DCS could automatically detect and fix input files being affected by changes made by the developer between aircraft versions.

A code mismatch will only result in the GBU not tracking, not a late delivery queue. This issue has now been verified by many people and it is not a laser code or laser firing issue. We are trying to work out the exact conditions that cause this so that ED can fix it.

Without using waypoints at all (only selecting sequence to see the route on the SA page), I am able to get consistent hits with LGB's. As others have mentioned, it appears very likely that the auto delivery erroneous delivery cues are cause by some conflict to the waypoint system. Even if the designation appears to be exactly on target, the release queue is way too late resulting in an overshoot release point. I can reproduce this consistently. To summarise, in my experience, in order to induce the inaccuracy: 1.) On the lower display, box the Waypoint in the top right. 2.) Set the waypoint to 1. 3.) Box the sequence option (don't think this has an actual impact) To NOT break it: 1.) On the lower display, ONLY box the sequence option. Do not touch the Waypoint box nor change the waypoints. I have tried deselecting (switch the box off) on the Waypoint button top right mid flight and then designate the target, but once it has been selected it breaks the delivery queue for me. I hope this helps whoever is trying to troubleshoot the issue.

I have now tested with old and new missions - no difference, still missing by a large margin. I then tried an air-start instead of full startup (I always do full startup), and this seems to work. In saying that that, with the air start, the Waypoint box on the lower display is unboxed, waypoint zero is set, and there is no active waypoint sequence. I vaguely remember Spudknocker on his YT video suggesting there could be a conflict between the mission waypoints and the waypoint set by target designation with the TGP. I will try another groundstart and leave the nav page as is.

After much further testing I can confirm that the Auto bombing mode is totally borked. My bombs release well after where they should, and have no chance to catch the laser or turn towards the target. The ONLY time I managed to score a hit was when I managed to switch to CCIP and manually pickle and the bomb managed to track and guide perfectly. I is not always possible to switch from AUTO to CCIP for some bizarre reason, so this is not a failsafe solution. We will need to wait for ED to fix this. If you run into the same issue, the good news is that JDAMs in TOO mode is your new best friend.

I usually do a check before I run in and both munition and TGP had matching codes (1688) on each run. I will try a code other than 1688 next time as well :cry:

Same issue here; made four textbook runs, target designated, point track, laser firing and the bombs just go free range. Bombing from 24K ft. Also enjoying the finger cramps holding in the trigger button (2nd stage) on the TM Warthog stick to fire the laser, and looking forward to auto lase functionality with a timer. And I want Wag's PC; things always work perfectly when he does it.

Don't feel bad; the controls are a bit of a dog's breakfast in CA. Some buttons should toggle between driver and gunner stations, but it only switches from gunner to driver. As Xtaxy correctly said, using insert will select the gunner view again. I have a nasty issue where the mouse control (after switching views a few times) overlay a cursor on the screen where I am aiming, and with a dual monitor the cursor often veers to the other screen and causes all kinds of havoc. I sincerely hope ED gives this module the love it deserves soon and fix these many issues. To be fair, these issues should not be that hard to overcome; it just looks like they haven't paid any attention to it at all.

I was not aware of this issue, and haven't flown the Yak for some time. I flew it again today, took it through its paces, and entered a flat inverted spin from where I could not recover. This felt very unnatural; to some degree I could arrest the rotation with yaw input, but pitch was entirely ineffective. Power settings also had no effect other than increasing the radius of the corkscrew of the inverted flat spin. I find it very hard to believe that the real Yak-52 displays similar characteristics, as inverted flat spins would be prohibited if that was the case.

Confirmed, same issue in F-14B after adding waypoints (markers) in map (F10) view.

Many of us play multiplayer cooperatively and not on dogfight servers, where there is enough time to jump between pilot and RIO seats. Is this a limitation of DCS itself (regardless of whether it is advisable or not in multiplayer)? I would like to have the choice to do so if I want to.

Can't say that I am happy hearing this; I am sure there are others that don't want to fly with humans in the back.

Thanks for that, I had the same question. Time to read that manual that someone put the effort into writing. Hopefully that will also explain why I am not getting any pings on the RWR from an SA-2 site in one of my missions? Edit: RWR is working! I suspect radar cross section of MiG-29 is much lower than some other aircraft, and detection range is much reduced (or RWR is not as sensitive as other types).

I have always struggled to spot the WW2 vehicles as they only start rendering when getting in close. My DCS settings are maxed out during these tests, so that should not have an impact. Placing some modern unarmed trucks on the ground next to the WW2 vehicles, I can easily spot the modern objects from a few thousand feet up, but the WW2 ones only start rendering much closer in. Is this a bug, or deliberate?