Direwolf

Have you seen a single time in one of the videos, an UFC input? I really don´t understand your statement…...

So check these videos made BEFORE the viper update, and watch the procedure done. Try to replicate it, and later tell me why we could manage the bombs dropping perfectly, and now not!

I thought the recent update (11/01) had fixed this problem :"Corrected JDAM's drop sequence.". Nope! The bug is still there!

I´m trying to hit several targets in one single pass (4 bombs, one each station), so I watched some videos and thought I had learned how to. Or something is bugged, or I am doing something wrong. Let´s see: 1 - Turn on TGP, Master Arm, A/G, and select JDAM; 2 - After some minutes everything is on (TGP and JDAM is ready), so I start to set the things: EFUZ Inst, select all stations (QTY), PP mode selected (PP1), and fly to the OA; 3 - Find a Target, change PP to TOO, TDC depress, and return to PP mode. Ok, the coordinates are stored to the station linked to PP1. 4 - Remember I´m on PP mode! Press Step to change station (it changes), and automatically mode is change to TOO! First weird behavior! 5 - Press mode to PP, and my PP1 is already set in the new station with the old coordinates!!! Second weird behavior. 6 - Keep trying to set the other stations with the same result! What I´m trying to do? Set all the bombs in PP1 mode (using TOO mode for each one), and release them all in one pass. What´s the issue?

After you get the lock with TDC depress, turn your MAV cam SOI; Uncage the MAV; Press Undesignate/Nosewheel switch. You now have control of your MAV cam and can do the little adjustment to the target. If you don´t press Undesignate switch, you will not be able to move your MAV cam, and lock the target with your MAV cam. It will be stuck to the TGP point. That´s for the F version. E version works with TGP lock.

How to attack several targets in the same area with Harpoons? I mean, how to be sure I launch two Harpoons for 2 targets in the same trajectory, and each Harpoon hits a different target?

That´s really funny. It never happened to me the way it was displayed to you! This track recorder is really bugged! I was never hit by the debris (in my track). Anyway, I repaired, removed the mods (JSGME), and the things started to work fine. I don´t have too many mods, but some of them made some mess with my AIM 9! So, the next complain is regarding track recorder (lol)! This thing is really crazy!

This is really weird! I never hit the target! I shot 6 AIM9 missiles! Not a single one hit the target! I don´t know why you see me hitting the target in the track! I never came close to what you saw! Really weird!

Another track with the same results. This time is DCS´s "DCTF Gauntlet" mission, where I have a Mig-15 right in front of me and closing. At around 1nm I got the "shot" cue, fire and the missile never locks. If you saw my previous videos, you saw I missed the guys, and the problem was not related to master arm on, aim9 selection, radar lock, etc. The target is locked, the missile is properly selected, I got the cues, but as soon the missile goes off the rail, it goes down to earth! Please check the video, and tell me what I am doing wrong! Like: "Your master arm is off", or "your target is not locked", or "your too far away from the target". I don´t see any of these things occurring, so I am doing everything by the book, unless someone tell me what is wrong. Bottom line: I am doing everything by the book (watch the videos, please!), and the missile´s behavior is very weird! AIM9 Bug 2.trk

Another track. I noticed another glitch: I need first to shoot a missile (without a "shoot" warning), and after that the warning "shoot" appears normally in HUD, for the remaining missiles. I mean, I cant 'get the "shoot" warning in HUD until I release the first AIM9. AIM9 Bug.trk

How do I record a short track? I tried to use nvidia recorder, but the video was 370MB for 10 seconds. But this is very simple to check. I used a training mission for the AIM9 (one that came with DCS), where it starts with me right behind 4 Migs. I just locked one of the guys, got the shoot warning and fired. The missile went down to earth as soon it took off the rail. server-20190914-190250.trk

AIM9´s are not locking on the target anyway. I have the "lock" and "shoot" warning, but as soon the missile goes off the rail, it goes lost. Any ideas?

Ok. The problem was related to the key assigned! In sim mode (not easy mode) the key \ doesn´t work! Despite the manual, there is a key assigned to the radio button in Ka-50 (SPU-9 PTT ; Ralt + \), and using it I can access the comms menu. So I learned 2 things today: 1 - There is a radio key to the Ka-50 ( I don´t need to use comms \ key); 2 - In sim mode, the \ key doesn´t work for ALL the acft. I need to have an assigned key to the radio PTT buton). Anyway, thx for the help.

You´re right! This key is assigned to SPU-9 PTT, and that means the Radio Button for KA-50. Thx for the help!

I can even change the command to any key I want (e.g. key "a"). The problem is not related to the key, but to the program, I think. For no reason, as soon I take off, the comms menu is not available anymore. It doesn´t matter if it´s binded to \ key, or Ralt \, or whatever key I decide to bind the comms menu to. If you´re not understanding me (English is not my native language), try to replicate the problem in your computer. Set an instant action mission that starts in the air, and try to press \ key (or whatever key you assigned to the comms menu).

I think it´s a bug! I want ED fix it! I don´t want to use easy radio mode!

It´s easy to replicate the problem! Get any acft you have, an instant action mission tha starts in the air, try to press \ button to access comms.

Like I said all the acft are presenting the same problem. But KA-50 is the worst case, because I don´t have a key assigned to the radio button located at the cyclic (non functional). The F-18 and Mi-8 have specific button assigned to their radio systems. So, in KA-50 is mandatory to use \ key to talk to someone. I can do that while on the ground (requesting start-up, taxi, takeoff). As soon I take off, I press this key \ again, and the menu does not appear anymore!. I can´t contact tower (for landing), wingmen, etc just because the menu is not available in the air

This glitch is happening to other acft, but in the case of F-18 and Mi-8 (the modules I have) I don´t need the comms key \ to access communications. They have specific radios assigned to specific keys (Comm1 and Comm2 for the F-18, and RADIO/ICS trigger for the Mi-8). Ka-50 doesn´t have a specific radio button to access comms. I have to use \ key. And after the last update it is not working anymore, when off the ground!

I think you didn´t understand the problem here! I am already talking to the tower (it assumes I set the right frequency for the tower, right?) when ready to take off at the EOR. The tower answers me and give me the clearance! I take off, and at the same moment, the menu I was using to talk to the tower disappears. I try to push the \ key again, and it doesn´t work anymore! I can´t access comms anymore. I cant´request a landing anymore!

Like I said, I´m accessing comms with \ key while on the ground. Everything works. As soon I am off the ground the menu disappears and I can´t access it again!

I noticed also "communication" key (\) stops working as soon I take off. While on the ground, I can access tower, crew, and no problems. As soon I am off the ground and try to access \ key, no joy. Can´t talk to the tower, to wingmen. In FA-18 and Mi-8 I use specific radio keys (comm 1, comm 2 in F18, and RADIO/ICS trigger for Mi-8) so I don´t need \ key. But in KA-50, there is no specific radio key, so I have to use \ to communicate with the world (I think it is time to assign a radio button to the game, anyway there is a button in cyclic for this function)

I noticed "communications" key (\) is not working as soon I take off. I mean, while on the ground, I can access the key, talk to the crew, to the tower, and no problems. As soon I am off the ground (in the air) it stops working. I can´t access wingmen, tower. I checked this behavior with FA-18 and MI-8 modules, and there is the same problem. But in those modules I can use specific radio keys (COMM 1 AND COMM2 in F18; Radio/ICS trigger in Mi-8), so I don´t need access "communication key". Is this a bug?

+1

I really don´t know what happened, but I erased the file snapviews.lua (user/savedgames/dcs.openbeta/config/view), and tried again. It worked. Thx for the help anyway.