escaner

I reported this same bug in the F18 years ago, not solved yet. Looks like they both use the same broken algorithm. This is an important feature when you fly low altitude pop up attack profiles where you roll inverted at the top of the manoeuvre. https://codex.uoaf.net/images/c/ce/Noncomputedpopup.gif

Maybe the mirages or the s3 can have unlimited fuel?

This mission is broken. When I reach the convoy, they start moving for a few meters and then the leader stops the convoy on the nearby bridge. Nothing else happens.

You do zoom in the tgp with the antenna elevation hotas controls, no need for further button mapping

If the target stays in the same relative position, you are in a collision course. Otherwise manouver accordingly.

All versions at least since the 9P go lead pursuit.

I am back with the Huey after a long time and the second day this bug shows up. I am unable to complete a mission that requires to stay on a Tico for 100 seconds because it crashes into the hangars. I even tried pulling back on the collective, not even with that can be avoided. https://www.youtube.com/live/LGReMQe-5Uk?feature=share&t=840 Looks like the same bug that happened in the carriers with the Hornet on them sliding around. Come on ED, this is a game breaker for landing on ships: the helicopter just keeps creeping around and ends up colliding.

Thank you, didn't think of free campaigns, I definitely will check all those you mention!

Hello I am considering the purchase of a campaign for the Huey, looking for some advice. I flew a few years ago the stock UN campaign, which was OK but a bit boring with long displacements. Also tried Argo, which had some fun missions, but I ended up losing interest and left a few missions from the end because of the unrealistic conditions, always on overweighted Hueys, flying VFR in pitch dark nights or into hurricanes. Anyone can recommend me a campaign that is not more of the same? Thanks a lot!

Oh BTW, the mission ended abruptly without any warning immediately after an interchange such as: "Filp: Tron 51, do you have us in sight? Tron: Negative". I have checked videos in YT from a couple of years ago and back then there was a message: "Mission success, the mission will end now" or something like that. This did not show for me. I thought that somehow the mission had bugged until I saw the title of the next mission.

I have been on this mission today. Launching from CAT1 did not work for me, "Enfield 31" (Blade) remained in the carrier. I think that the Anvils begin starting up in sequence when you start moving, and the problem is that if you launch before any of them has started, he stays in the carrier. What worked for me in the end was to move to the sixpack area (between the island and the angled deck), wait for all other 3 Anvils to start moving, and just then go to the cat. They went to cats 2, 3 and 4, and I ended up in cat 1. By that time everyone else had already launched because I was just waiting for my flight to move.

I understand you, and really appreciate your effort in providing realism in your campaigns, but take into account that in real life, when there is a doubt about the coordinates or something else, you can ask for clarification. You can't do that in DCS. That is why I think that these things should be more clear when interaction is not possible. Anyway, if someone is expecting to enter coordinates to create a WP in default format, e.g. DDº MM.MM', but you provide them in DDº MM' SS" saying the units, I bet that 90% of the people will enter them incorrectly without converting them, achieving the same confusion effect.

Hi, tried again with 4 x JSOW and this time I could complete the mission, but there was another issue: again, no tanker available going back to the carrier. I found the taker it in front of me on approach when the ATC told me to "call the ball", we nearly collide. I don't understand why ATC will give me a push time for the approach and allow AI do whatever they like, but well, that is ED...

I tried this one today and had the same problem as in the first message: when I tell Raven 34 to attack via F10 menu, he stays in formation with me and never attacks. I am not using any mod. I will try with 4 JSOW as barronpixy suggests. Also, may I add a suggestion? When coordinates are given, please, don't forget the units. It is very confusing because sometimes are DegMinSec while sometimes are DegMin and they could also be just Deg. When no units are given, I just assume it is the default while inputting, but I remember that there was a mission where it was not the case (the one with the exfil in the island next to an airfield) and it was very confusing.

In the DCS Hornet you need to Undesignate the target in order to be able to slew a Maverick.

What a surprise it was returning low on fuel, selecting to AAR with Texaco in the F10 menu and noticing that there were no tankers in the radio menu... From what I can see in Tacview, Texaco gave fuel to a UAE Mirage 2000 and returned to the boat. See the screenshot showing that it landed short after taking off.

Hi. 1 in the long version; 2 & 3 in the short version (I did not arrive to that point in the long one).

I just flew mission 3 and found a few problems: 1. Target #1 (red truck): I used F10 to say that I would attack, then missed (forgot to arm the bomb) and told Smoke to attack it. He destroyed the vehicle and went AWOL on the attack heading towards Iran, never to come back. Back in the tanker it was his turn to refuel and I could not advance in the mission triggers. So I restarted the mission and advanced to the tanker refuel for RTB (great feature!). BTW, I suggest to remove bombs from the planes, in this restart as they should have expended them. 2. When arriving to the carrier, I pressed SPACE to tell Smoke to go on his own but nothing happened. 3. Trying to land on the carrier, there was an aircraft on the runway that could not vacate because there was some kind of jam on the deck (see picture). Therefore the LSO kept waving off for foul deck. BTW @baltic_dragon I have the mission recorded and Tacview ACMI if you are interested.

And then, out of thin air, almost seven years later it appears in the changelog as fixed...

Yes, they moved the position forward. Now it is not possible to lean forward because the camera is already in the most advanced position and e.g. the glareshield blocks the top lines of the annunciator panel. It was much better before the change

Instead of a key combo, configure in DCS DirectX joystick events for Left Engine Cutoff and Right Engine Cutoff and in the TARGET script activate the event without the PULSE modifier. This way the DX event will stay on while the throttle is in CUTOFF and will turn off when you move the lever to IDLE. E.g.: In TARGET: MapKey(&Throttle, IDLERON, DX29); MapKey(&Throttle, IDLELON, DX30); In DCS: Right Engine Cutoff: JOY_BTN29 Left Engine Cutoff: JOY_BTN30

I dont know about vr, but symbology brightness is much lower in 2d, which makes the mfcd much harder to read and it is not possible to increase to previous levels

Please, read my post. It is not about the FOV function as all those threads. I am talking about the switch between CCD and IR modes in the TGP.

I have found this weird behavior of the TGP (Litening): Use WPDSG to select waypoint as target. Activate the TGP and move it. Use SCS right 3 times to cycle to Area, Point and back to Inertial mode. When going back to inertial, the TGP is moved to the target designated point. Note that if TDC is pressed before moving the TGP away from the WPDSG point and then cycled with SCS to Area, Point and Inertial, the TGP does not move away from current position (last cycle in the track was done using this method). Track attached b-tgp-moves-to-tgt.trk

With Maverick selected and Litening pod as SOI, it is not possible to use RAID/FOV long press to switch between IR and CCD TGP modes. As I understand, it is correct that RAID/FOV short affects the FOV of the Maverick missile instead of the TGP, but it looks like the long press is also interpreted as a Maverick FOV switch even though there is not such function as RAID/FOV long on the Maverick. tgp-no-ir-ccd-switch.trk