John C Flett

When you watch the video there should be five icons on the bottom left of the picture. Click on the second from left, the one that looks like a cog. This should give you a pop-up window. The bottom option will be "Quality" with a number beside it. Click on the number to select resolution. If your connection is slow it may have defaulted to a low option.

I think they're called "billboards". As you say a 2D object pasted onto the sky. As I recall a new cloud render is on ED's "to do" list.

Not unique to your system and not unique to DCS. And not I think an easy fix. I don't know all the ins and outs but I gather it's tied very deeply to the way graphics render which is why it crops up so often. It's not that it can't be fixed but the alternative render is much more demanding.

Try this. Viewed with a slant. https://imgur.com/a/aHjsXrv

I'm going to take a look at that again. Both of us having the cargo come through the window seems too much of a coincidence. Especially since I have never had the problem outside this mission. Alright, re-flew this. After the pickup I ignored the instructions to land and put the cargo down. Put the Huey on autopilot so it flew straight and level. As you said the cargo swings increasingly wildly. This was not caused by any movement on the Huey's part. After about two minutes the swing went so high the cable was cut by the rotors. This is such an unnatural behaviour that, coupled with the fact you are told the line is faulty, I assume it is intentional. It seems that the two minutes you have should be sufficient to allow you to get back down and lose the cargo as instructed. Indeed, I found that if you pickup slowly, you can get the instruction before the cargo even leaves the ground. Changing the cargo seems to override the behaviour from your description but given that you don't actually need to move the cargo to advance the mission it shouldn't be necessary.

Not opposite. South and WNW. This might help, I'm Avatar over the FOB. North is up. https://imgur.com/a/KwyauPR

Hammer, I would have sent you a Tacview if I could figure out how. One mortar team is on the hillside just south of the FARP. You can probably see them quite clearly. The other is WNW in an open area just north of the buildings. If you have difficulty locating them watch for your door gunners opening fire or the Hogs diving on them.

I've played around with the Huey in the mission editor since having this problem. It's hard to be sure since I don't know what detection ranges should be but it does seem that sometimes I get ADF at very long ranges while other times I need to be right on top of the transmitter. I find it can be difficult to be sure I'm on the right frequncy sometimes and my morse isn't good enough to recognise the identifier codes. Also, without knowing how ADF and FM should work in real life but I seem to get FM direction finding at huge distances sometimes. In mission 5 I could pick up the FOB right from the start despite having at least two mountain ranges between us. Somebody with a better understanding needs to check this out but it seems that direction finding on the Huey seems to be a bit weird beyond the campaign.

I've done this mission a few times with no problems (beyond my poor pickup). One weird occasion where, even though I was sure I'd dropped the cargo, I get a line break message followed by the cargo crashing through my windscreen! Just checking though we are talking about the same mission. You should, almost after take-off, get a message about a problem with the line. You shouldn't be going that far with the cargo in mission 6. Perhaps part of the problem?

Alright. Problem was between keyboard and chair! Things move pretty fast in that mission and I simply missed the radio call about the second mortar team to the Northwest. I'm guessing the Hogs weren't up to the task and hence the trigger never fired. Mission worked much more as planned this time. A smaller, less important bug though; the first comms I got was Dmitri telling me the cargo was hooked and I could go. No preamble and without a cargo hook request from me.

Just had the same problem as Hammer. I was told to orbit but my AI gunners had already engaged the mortar team. All hostiles were destroyed and I just kept orbitting, no further comms. Eventually I landed but, again, no result. Running stable release. I really don't envy you guys who have to keep these missions working every time an update breaks something.

Shame, that is different from the static ADFs on the map. I don't seem to be able to edit them. Might give me an alternative to experiment with though.

pdmarsh, how did you edit the wattage? We've been having ADF issues over in the Huey Argo campaign and I wonder if we're having the same problem.

I think that's a bort number you're referring to there. Though I believe the origin of the word is from "board". Really just means "on the side".

I'm not sure if Huey ADF works the same but could this reported problem with the Mi-8 be related? https://forums.eagle.ru/showthread.php?p=4347634#post4347634

I've tried this mission a couple of times and it quickly becomes I nightmare. I can tell sky from land but thats about it. I aborted my last attempt after a pylon suddenly loomed out in the searchlight which gives you an idea of how close I must have been to it. Any update on this Petritis? Even just allowing NVG's until the lighting issues get fixed?

There is a way to edit the campaign file but I find the easiest way is just play missions through the mission editor. I've had too many issues with broken triggers and the only thing you'll lose is a campaign count in your log. Also has the advantage that you can jump back into favourite missions any time you want.

Limited help but I just flew this mission in the stable release and while it took a few seconds to trigger it worked fine. I landed off the C130's 1o'clock. I have flown two missions with this campaign and the most obvious thing is triggers don't seem to fire straight off. Make sure to give them a couple of seconds.

You're getting a wider range of opinions and it's probably worth addressing some of the issues as a VR fan. VR can be a bit of a PITA to set up. No more so than getting out my flight stick, throttle and pedals. Not a big deal but it's enough to put me off if I'm tired after work. Comfort can be an issue. I can wear the Index for a couple of hours with little problem but that wasn't true at the start. It took me a while with both my headsets to find the best fit. Additionally the Index gets hot and I had to fit a USB fan to cool it. Shimmering was mentioned. Without seeing it that sounds like ASW which isn't great but I've turned it off for all my sims and I've had no problem since. Image sharpness is poorer than the 4K monitor but I find it sufficient for guages. Against that spotting is easier as objects are properly scaled in you field of view so it's kind of six of one half a dozen of the other. Keyboard commands can be an issue though I can find some keys easily enough by touch but otherwise Voice Attack really helps and the Index has a good inbuilt mic. As suggested try to get a demo of VR but be aware that if you go for it you won't be getting best results from day 1. You will probably want to spend some time tweaking your setup to get best results.

As the others have said VR is a whole new experience. Since going VR (Vive then Index) there are a number of titles that I have no longer play on the monitor as it just raises the experience so far. DCS is slightly different in that I find when learning a new module I like to be able to refer to notes or the manual so I'll still use the monitor but when I do go VR it is much more enjoyable. I believe also that I fly better. I'm revisiting the Huey at the moment and it makes such a difference to how I fly. I can safely go lower because I can judge altitude, my landings are much neater and I've even been getting to grips with slingloading as I can judge hover and low speed better (still room for improvement though).

Just had this happen to me too. Checked my Tacview file and there was no collision. Just two Hueys exploding. I'll try again later but even starting this campaign has shown me that I'm very rusty with the Huey.

Sadly just got stuck here too. Same problems. Max reported his No.2 getting hit but the mission never went any further.

Never flew online but been around since Flanker ( and before ). I think I may even still have my copy around somewhere.

Not played with the Spit but this just sounds like DCS in general. I've been playing the M2000 Red Flag campaign and I've seen my wingmen reporting low fuel while I've only recently ditched my external tanks. A number of times I've watched them all drop out of the sky long before the missions over. AI wingmen just seem to burn fuel far too quickly.

The story was that after Black Shark came out the Russian Government was unprepared for how detailed it was and changed the law to prevent any more current generation aircraft being simulated.