Redglyph

How do you do that, by taking off normally, doing a circuit and stopping over the crate? I tried but I think I had to apply more than the limit to keep enough altitude. I haven't tried very hard to be honest, that's certainly one skill to improve, that's why I enjoy those campaigns :) UPDATE: Nope, it really needs alomst 40 PSI torque to hover high enough, and EGT is at least 640°C.

From the technical perspective, I'm not so sure, but the public would love it, 10/10 for entertainment :D

Unloading the weapons, either in the mission planner or with the ground crew menu, seems to make it possible without exceeding too much the exhaust gas temperature. Perhaps that's how it's meant to be for such missions?

Like you, I'm also using the manual hook procedure if hovering takes too long, since I'm not yet mastering it ;) - landing near the cargo - F6 "All Cargos", selecting cargo - RSHIFT+RCTRL+L to hook the cargo (manually) - careful, vertical take off You can remain between 610 and 625 for 30 minutes. Above that can only be sustained for only a few seconds (pg 60 in the DCS User Manual). I also have to go past the recommended EGT limit for a while, when climbing vertically high enough not to damage anything, and if I'm looking ... it's usually 640-650°C *without cargo*, way too much. Below that it remains near the ground and benefits from the ground effect. So is this an issue with the Huey, or the initial weight? I have no idea. It should be bad if it lasts too long I suppose. I've noticed there was some damage if you didn't take a careful, slow vertical climb after hooking, that's probably the problem you had, and not the EGT excess. In some cases the cable may even break or unhook.

That's weird, I never had this. Which mission? Which DCS version are you using? What exactly are you doing, step by step, so we can try and replicate? Do you have the same problem in other missions, like the training or quick missions? Hard to help without at least some info ;)

And another update: - 1.5.6.4818 changed the localization and did some clean-up of the file.

Updated for DCS1.5.6.3690 and DCS2.0.5.3889 (and later versions). The direction of the flood light knobs was fixed by Magnitude 3 LLC, hence the new file. Enjoy :)

I've just checked and it's fine on 1.5.6.4546.280. Yeah, there is no notification for the user file section unfortunately, which makes mods a bit awkward sometimes ;) You'll see two folders, DCS1.5.6.3690 and DCS2.0.5.3889, take the first one for the beta, it hasn't changed since 1.5.6.3690. Magnitude 3 fixed the rotation of the two flood lights, and they had to change this file for that. I don't know anymore whether the EDM was fixed in 2.0.5... I'm so used to copy it from 1.5 that I can't remember. But flood lights should work nicely with this EDM in the alpha as well, which is cool.

Did you take the latest version? I'm trying to maintain this mod up-to-date when the original file changes with a DCS update. Hopefully they'll integrate the fix at some point but until then, it means checking the thread or the user files section for new versions... :) Next time I'll add a post in the fix thread, so that anyone can simply subscribe to it and see updates.

Strange place to move this thread to :D

Speaking of broken things, since the cargo view has a problem, it is possible to use LSHIFT+LCTRL+C to get a miniview down instead. Probably a good work-around until it's fixed, and it has the advantage of keeping the view ahead as reference. Found that very handy for cargo/hovering-related missions.

Are you using a mod like SweetFX or ReShade? They're known to cause such problems.

Very helpful video! :thumbup: First time I see the trailer. Well, I'd buy it again! :D

I think this could be a concern for anyone and for any campaign. Don't worry, that comes with some practice, even if that's not immediate, and a campaign is the best incentive. For example, I'm far from good but improved a lot by doing the UN campaign coming with the Huey, even though it cost me some time with stupid crashes when landing badly at the end of a mission and other little frustrations like that ;) So now if I know there's something difficult ahead, I prefer to look for a training mission to brush up or improve the required skill - not to perfection but just enough, or I simply make a little mission for that and avoid ruining the campaign experience ... especially for long missions when the difficulty is not at the beginning. This ARGO campaign seems somewhat forgiving, at least at the beginning. For example and without spoiling with details, you have to hover above a target for a little while. You don't have to be perfectly still for this to succeed, and you may proceed in iterative steps, so even if you're not mastering the helicopter you still have a chance. Not sure all missions are like that, though, but that seems to be the spirit.

In DCS version 1.5.6.4546.280. If I switch to cargo view (LALT + LSHIFT + Q), I have the expected down view, to help with cargo operations. However, if I hit the shortcut again to get back to pilot view, the camera has moved left and is almost in the centre of the helicopter, not in the pilot's seat anymore. After that, if I switch back and forth between the pilot and copilot view, or any view, it cannot be set back to its original position. The copilot view is correct though. The only way I found to get back the pilot view is to start a new mission. If I try the same from the copilot's seat, the problem is the same in the other direction, its position has moved right. UPDATE: I also found that tuning the view with RCTRL+RSHIFT+NUM4 / NUM6 was not working anymore after a camera has been switched to the cargo view. So for now, this cargo view really shouldn't be used.

I should probably report that in the UH-1H bug forums instead :) About the campaign, lot of fun so far :thumbup:

Mission 1: I'm just mentioning this bit I've just seen and could confuse people. If you happen to change UHF, you're told to tune back to 262 MHz, but I think it should be 260 MHz, and not at 262 MHz or it keeps giving this message every few seconds. Similar issue with the search mission where you have to tune to 47 MHz FM. It keeps displaying the reminder even though it's correctly set. It seems to be customary with new campaigns ;) By the way, does anyone else had this problem on the Huey when you use the cargo view (LALT + SHIFT + Q by default) and try to get back to the normal view, it's completely off and apparently not possible to get back to the pilot's position? Is there any trick to get around this?

Perhaps you missed the two long threads of support and the unprecedented availability from their part, or the fact they cannot control all external constraints like the protection mechanism provider or ED's delivery system. To me, that looked very professional, the only glitch was not asking ED to mention this in the first update but considering the circumstances it does not shock me. They solved an old problem with a very simple method, and still get criticized for that, I'm amazed. Especially when it comes with complex products that require reading hundreds of pages of manual, this in comparison is quite basic. I don't understand why we had to do this, I suppose it's a limitation of the StarForce system or poor support from their part, I don't want to speculate. Those protections are always the matter of choosing a lesser evil. Thankfully they're not using something bad as Denuvo, that would be the day I uninstall the product.

To add to what razo+r already said, make sure to check the other April thread, the first post contains all the doc you need (check case 4 in the pdf). You only need to do this once, for either 1.5.6 or 2.0.5.

Yeah, this January bug is annoying ;) You can simply edit the mission in the Mission Editor, and change the date to early February for all the missions that are concerned. Since this campaign is not protected, you can save the edited missions (the modified files will be replaced on each update).

@ED: is that a known issue?

Have you actually read part 4?

From the message it looks like attempting to deactivate from a new version, he'll have to use step 4 and remove the registry key. (https://forums.eagle.ru/showpost.php?p=3103176&postcount=30 and replies, for ex) Oh, or were there key "exchanges" that led to their being blacklisted? o.O

It's one of the described cases in the pdf (and many, many posts in this thread cover this specific problem). Look for part 4 in the document and you should be good to go.

Perhaps they gave the choice of the cockpit then, that would make it easier. :)