andqui

Having some trouble with the triggers on this one: peform my rocket attack, didn't destroy everything. On my next pass, was told the Apaches were on station, they would attack the sam and that I should break off, which i did. The apaches then proceeded to effectively destroy the targets at the airbase and at Alcatraz. Then I was called about the incoming aircraft, went off to visually ID it. While doing that got asked if phantom should head in or wait. As I was out to sea looking at the aircraft, I said wait. Spotted the C-130, flew close to make it break off, then when inbound again got phantom to move in. At this point all three Apache's nose-dived into the ground next to Alcatraz, and Phantom/Gazelle just did laps off the coast and never moved in to land. Tacview included. Tacview-20220213-103145-DCS-M03 FINAL.zip.acmi

Haha I paid for every mission of the campaign and I want to finish every mission of the campaign. Next time I'll try coming in straight onto the road and landing with the wind. What I had been trying before was to pass down the left of the road and then make a 180 right turn to land against the wind, which I guess is the opposite of what the mission expects. I do really like this campaign so far, but I can tell there's a bit of a language barrier involved. There are tons of grammatical mistakes and misspelled words in the radio messages. The accents are very thick to the point where I have trouble understanding sometimes unless I also read the text, which is difficult to do when I'm flying barely over the treetops in poor visibility being shot at. Watching the video you posted, now when I'm not concentrating on flying I can hear the copilot say "stay right over the street". But this is still a very ambiguous statement and could be interpreted a number of different ways. Does he mean right over the street as in low altitude so we don't get shot? Keep to the right side of the street and not fly directly over it? I know in my example I was doing neither of these and going around to the left, but that's because I couldn't even hear or understand the message in the moment. In cases like this, I just want him to clearly say "Now fly directly down the length of the road and land with the wind behind you by the orange smoke".

Was able to play mission 5-1 after the last update fixed the pathfinding issues, it was a lot of fun with the raging ground battle. Advanced to 5-2. Found the scout on the hilltop, picked him up ok. I'm now having a lot of trouble with the next part of the mission where you need to land at the convoy to drop him off and pick up the troops. 1) I don't know if the terrain/map has changed recently, but there is almost 0 room to land on the road by the orange smoke without hitting some power lines or trees. The two times I've tried I've clipped something and the rotor came off. There is absolutely no margin for error. Just making sure it's meant to be this difficult. Also, the communication from the copilot/commander is not very helpful... he says "drift left to land" or something like that.... when going down the left side of the road is a row of power lines. Maybe there's a little room just ahead of the origin of the orange smoke, but it's cutting it very close, and the message communications don't make any sense about where I'm supposed to be actually landing. The power lines obscure the whole side of the road where he says to land. 2) The third time I tried this mission, as I was coming in to land at the orange smoke, I guess i got a bit too high and I started taking fire from the enemy vehicles. So I shoved the nose down to get some speed, get out, and try again. As I passed low through the trees down the road, it seems some triggers fired prematurely. The scout said something like "thanks for the ride" followed by the Hans the door gunner saying "everyone on board"and the copilot saying the choice was mine if I wanted to go one of two paths. These triggers don't seem to be correctly waiting to confirm that you've successfully landing.

This tool worked beautifully for me- except for the F-14 and Viggen. The AB engages too early for me in both of those. I know the Viggen just had an extensive update- did something change with the internal detent positions there that would require an update for this? It's complicated by the fact I'm using a Virpil CM3 with an idle detent (which needs X-saturation of 87) and also an inverted axis. Screenshots included. With this set up, the afterburner kicks in at full power just shy of the real-life physical detent; maybe Heatblur is doing something internally that the rest of the modules aren't that doesn't play well with the X-saturation?

Thanks for the reply. I copy and pasted the livery folder to the saved games section and now it works. Definitely did not work before I did that. I am running the beta, but my file path is different and doesn't have .openbeta in the saved games path like yours does. Haven't had time to try mission 2 again regarding the stuck humvee, but just to I'm prepared for when I try it again: I land by the checkpoint, they say they're arranging a taxi for Wolf 1, the humvee drives off. Later it comes back. I'm told over the radio to follow it to the outpost? Did i miss anything important? When I tried it the first time the humvee drove down the road a short distance, took a left turn near some other vehicles, and then drove up to a tree and did not move again. Will report back if it happens again the next time I try it.

Did this make it in to the update? I see it in the changelog, but when I fly the missions there is just the default blank aircraft skin, no wolfpack markings or even german markings for that matter. Also in mission 2 the Humvee i'm supposed to be following gets stuck on some trees.

Hello- Mission 3, player skin is brown/green Soviet camo, appears correct. Wingmen 2-4 however are all in the Serbian grey livery. Also, in this mission, the SAM batteries started to engage the enemy fighters without any sort of communication beforehand as I was heading towards waypoint 2, had not rendezvoused with Su-24 yet. Just got "SA-6 launching!" and "SA-3 launching". A few minutes later a message telling me the enemy fighters had retreated and that I could return to base. Seems something is making the enemy prematurely stay into the SAM engagement area? Mission 4, same skin issue as above, all aircraft are in the Serbian livery.

So.... why does it take multiple rounds for the minigun to take out an infantry soldier? I'm trying to play the "No Time to Drink" mission in the campaign. Rebels are attacking the outpost and I need to take out two groups. The first I come in and obliterate, with the rockets, no problem. The second group, no rockets left, and I need to take out 3-4 infantry and a car. I just can't do it. I have the damage log up, when I fly, and each minigun bullet it is making infantry something like 9% damaged. It takes 7-8 direct hits to kill a single infantryman. With a 7.62mm minigun round. That, combined with the fact that it's all in a dark canyon with NVG's make this mission pretty much impossible. The darkness and night vision that completely blinds you whenever you shoot is a fun challenge. The puny, feeble "miniguns" strapped onto the sides of my chopper that do pretty much 0 damage is another, and extremely frustrating when even scoring a hit because of the mission conditions is difficult. I can't imagine this is working as intended. It is exceedingly difficult to destroy anything of substance with the miniguns, even unarmored infantry in the open.

I just tried the mission again with the latest open beta and the issue still seems to be there? The two russian ships are racing away from the ivanov well before I get there, they're like 20 km out?

I just hopped in the Mig to see if there were any FM changes with the open beta that came out today, and had this radar performance problem. In the A2A missile training mission and the "free flight" mission, FPS is steady locked at 60 fps with the radar in standby, when I turn it on it immediately tanks to 20 or so. I don't recall this happening before the patch that came out today, but I hadn't tested it in a few weeks.

Where is this trigger zone? I did successfully get the message to provide help, was told to make sure to use A/A mode. It told me to fly to VS-4 (at the top of the mountain), which I did, then nothing.

I've taken off, climbed to altitude, destroyed the first camp. Got the message that the camp had been satisfactorily destroyed. Proceeded to take out all the tanks, helicopter, APC, and truck at the second target, all apart from one tank. As I was working on the last tank, I got the radio message that the Mi-8's were being chased by hinds and to proceed to VS-4. I climb up, go there, and hover exactly on the VS-4 spot on the ABRIS- and nothing, the hinds/Mi-8 do not appear. I even turned on labels to look around, can't find them. What am I doing wrong?

Does this refer to the friction when landing on road bases? Or by crossroads do you mean something else?

I've noticed that the AI tends to fire off their RB-04 too early, so that the missiles run out of energy and hit the sea short of the targets. Is there any way to get them to close in a bit more before firing?

Mission 10, the one where you fly to Leningori, and while en route a separate flight of Mi-28 gets vectored to check out a fire in an abandoned village. One gets shot down by a SAM, and then I have to evac him while my Hinds provide top cover. Problem is, they don't engage the insurgent on the roof who fired the missile. After warning me to stay clear while they deal with the enemy, both of the Hinds, and the lone Mi-28, just endlessly orbit around the village at medium altitude, not employing any sort of weapons. As such, I don't get the message that it's safe to make the pickup, and can't progress in the mission.

Ohhhh..... I assumed all the buildings next to the helipads counted as the farmstead, as they were all on their own away from the town. Guess I'll look around a bit to the south then.

So you can confirm that it does work in 1.5? There's the river, then the farmstead/barn type of thing, then 2 x FARP/helipads, and then a road. I've tried landing on the helipad, and also between the river and the building, no luck. Triggers worked no problem for the previous landing at the Shpora(?) FARP.

I'm having a problem in 1.5 in the first campaign mission, when you do the familiarization flight and drop off mail and such to the different outposts. Approaching the "Vetka" FOB, the last one before you turn north, I get the triggered message that tells me to land at the farmstead out of town, and to avoid the river bank. However, after landing, I don't get the "unload the documents" message, the trigger doesn't work, and I can't progress with the mission.

I think I had something similar happen to me- I was doing the ARC tutorial flight. Soon after take-off, the signal was found and the radio pointer needle pointed straight for station 3, and I got the text there as I arrived. However, I never saw the pointer "swing around" to 180, before the text told me to select and fly to station 5. I hit the 5 button, the needle briefly swung to the right, before settling back to pointing straight ahead the way I had been going, taking me all the way down towards Sochi before I lost the signal. This was in the singleplayer tutorials.

I don't think a full profile is really necessary, there aren't many complicated HOTAS functions. All I did was go into the game menu, setup the curves as outlined in the manual, and then bound various switches to their closest representatives on the stick and throttle. For example, castle hat up/down for trim, thumb button for weapons release, red button a for lock, side button on stick for recovery mode, paddle for the brakes, etc.

What do you mean by accumulating errors? Anyways, the entirely realistic way to fly it would be to push the trim button many many times, repeatedly, as you move the stick to different positions. However this isn't really possible without FFB, so I think the way above is a good compromise that gets you controlled + trimmed flying, but it can still be tedious when doing something like a rocket run while one finger is occupied holding down the trimmer.

I don't know if it's already been mentioned, but here is what helped me really enjoy the Ka-50 a few years ago. First, check the central position trimmer mode option, so that you don't need to worry about recentering instantly. Next, instead of just moving the stick and then pressing trim, hold down the trimmer while maneuvering, and release when you're stable in the new desired attitude. When you hold down the trimmer, the AP channels stop fighting you allowing you to fly freely. When you're situated how you like, then just release the trimmer and smoothly return everything to center. This leads to smooth controls while maneuvering, and also makes it so that there is no post-trim "bump." It might not be entirely realistic based on how the helicopter is actually flown, but without a FFB stick it's the best option for me, and lets me fly very comfortably.

Is INU drift modeled? I was flying a long-ish mission online yesterday, and towards the end I noticed there was a slight discrepancy between the ABRIS and INU reported distances. The mission was not built with any reference points, so I didn't know how to perform an update. Is there a way to make your own reference points in the chopper, without using the mission editor. For example, if I land at an advanced FARP to rearm, can I note the GPS coordinates on the ABRIS to manually enter a new reference point on the PVI, and then perform a "fly-over" alignment? If so, how do I go about manually entering one? thanks

I've been trying the Mi-8 campaign missions, and the I'm getting ice detection warnings at higher altitudes in the mountains. The automatic system kicks in, the red "icing" light begins flashing together with a ticking noise, and a few seconds later I manually engage the left engine anti-ice, no problems. However, once I descend back to base and leave the icing conditions, the ice detection warning keeps playing, and doesn't reset. I don't see a reset button anywhere, and toggling the circuit breaker on/off doesn't help. Is this working as designed? Is it maybe DCS's "icing" system being a bit simplistic/buggy? Is there an OAT gauge anywhere in the Mi-8 that I can use to confirm that I am no longer in icing conditions? thanks

thanks a lot for the upload. Are the pdf mission briefings available anywhere?