Sharkku

Why don't you try the 2.5 beta?

I edited the mission with ME, yes. And exactly those triggers! :) Not sure what height would be required, maybe as much as 340 isn't needed. Oh well, if it works, it works!

The mission doesn't detect when I have landed at checkpoint 8. I suspected that the terrain mesh had something to do with it, and changed the required value for maximum height to 340 instead of 325. After that it worked.

Hi! A fun mission, once you get the hang of it! Some feedback: You should include a more detailed mission description in the in-game briefing. The first times I tried it, it wasn't clear to me what I was supposed to do. And what about the aircraft that gets controlled by Skynet? Do I need to shoot them down, or fly close and detain? When I tune in to the frequencies of the vehicles, I only get homing signal in very short bursts, making it all but impossible to track them down if not using labels. Is this by design, or a bug in the latest version of DCS? If it's by design, you could provide just a fraction longer signal bursts, as it is now, it's too hard. Thanks for the hard work and some fun flying!

Yeah, I noticed, and I hope so as well!

Controls indicator and AI status overlay for the Huey are now visible by default in VR, and DCS doesn't remember that I turned them off when flying next mission. It would be preferable to have them turned off by default, since they subtract from the VR immersion. Also, they are both cut at the outer edges. (For those of you who want to hide them: Ctrl-Enter and Win-H respectively.)

With the latest release, the dirt and scratches on the windshield are gone. Only tested on the Huey, but with multiple graphics settings, including High+lens effects. Using VR (Rift). DCS version: 1.5.7.7741.

@Daredevilsl: I can do it as well! Granted, it was my second try... :)

In "straight and level" mode, the autopilot heading is slowly drifting to the right or sometimes left when in high time-compression.

Yes, I have this too. You have to "bring it to life" by moving it with the mouse or keyboard first, after that it works. It's been reported in another thread as well. Guess it's not a high priority bug, since it's not game breaking.

I've noticed that the landing light doesn't light up buildings and landing pads and units, but no problem with terrain. 1.5 latest version.

I'm one who removed the spring of my HOTAS Warthog, never regretted it. But friends who try my setup are a little surprised at first by the soft feeling of it. :D

I just found this on reddit: Seems it does exactly what I want! Setting it up now to see if it works. Edit: Apparently only works if you load DCS via SteamVR...

It's realistic behaviour, the way it works in real life.

I agree that having to re-do the same thing over and over again gets tedious quickly. There should be a save feature in the sim. It's already on the wish list since long ago. Anyhow, you have to agree that successfully completing a mission gets so much sweeter the more you worked for it! Congrats!

Yeah, I have this issue, but it's not specific to the ARGO campaign. You should post this in the uh-1h bugs section perhaps?

Yeah, I had the same trouble with this mission! But what a great mission!

Want to start off by saying it's a really great campaign! Have flown 6 missions so far. Counting the hours until the next flying session every time! However, some feedback: -It would be really helpful if you could list the letter identifiers for the NDB:s and other navigational aids along with their frequencies, in the mission descriptions. Especially NDB:s are notoriously difficult to tune if you can't check your tuning by listening to the morse code. -In general, the mission descriptions are great, and I really like the detail and fleshed out backstory. However, sorry for saying this, they could do with some proof-reading for grammar etc. Especially the use of "worst" instead of "worse" is particularly frequent. I know it's a minor detail, and doesn't affect gameplay, but still. Thanks for this overall great campaign!

Yep, the CDI is working properly now, both VOR, FM and ILS!

Great! It's fixed now, version 1.5.6.4818!

Yeah, I feel somewhat guilty since I was pretty active reporting the VOR bug, and even suggesting simply multiplying the deflection value by -1. Seems both FM homing and ILS are reversed now. I'm sure it'll be fixed in the next update.

Yes, and yes. However this graphics bug could be a little more complicated to fix, and hence the delay fixing it.

Last update fixed the reversed deflection of the CDI needle when following a VOR radial, but now the deflection is reversed when tracking an FM homing beacon.