zerocoolant

In stable 1.5.7 (I'm not sure of earlier state) R863 controls "Dial / Memory" and "Squelch" do not respond to their keyboard shortcuts: LAlt+LWin+W and LAlt+LWin+T respectively. Other LAlt+LWin+* controls for the R863 work as intended (e.g. frequency knobs).

I was critical in an earlier post about some aspects of the Spring Tension campaign. I finished it tonight and wanted to give praise to its creators! The last mission was ... bravo! The holding pattern, how the mission evolved, all of it...super good. The campaign overall was awesome. I loved the ramp up and the variety of tasks. It was many hours of fun and I really appreciated its depth. A few small suggestions / observations (mostly systems under-utilization): - Radio management was not really a thing. That's cool, but rather different than for example the museum relic campaign. - Radio navigation was not really a thing. Certainly there are few NDBs in that area, but for example the flight to Mozdok / Nalchik for the replacement airframe it would have made sense to have used them as a reference. - Flares were not used, but could have been by other helos as an example after gun runs, etc. ...I'm sure you get the gist... - When flying with an AI lead, please consider having the lead announce the direction post-take off. "Flight, take off" is good, but sometimes the AI helos out-climb or are lost sight of. Having at least a bearing to search would be helpful. This was especially tricky during the 4 troop drops with two fakes mission where my flight plan got me to the A.O., but only the leader knew the L.Z. locations...would have been super nice to hear: "Flight, take off, initial heading 090." Huge kudos for the night illumination mission. The bomb-subsystem was interesting to learn about an operate. It also created a very surreal universe below. That mission was a real treat! Although the NS430 took a lot of adventure out of the navigation part. Anyways, thank you very much!

+1 to this issue. Having trouble using the VRInsight MSPanel that worked so well for the Mig-15's controls. NS430 knobs skip two to three clicks for every pulse.

+1 to this. It also happens when taking off from Shpora in 'spring tension', when you spawn at shopora and power on the NS430 it appears that you are on water with the water having a straight up and down edge.

I encountered this as well while flying night missions in "spring tension". For me the issue was only present when I turned on the overlay, the 430 itself did not affect NVG. It was also much worse in the engineer and navigator positions. I did not notice it at first as the pilot.

Go for it! It is big, well modeled, complex, and able to do many tasks. There are hundreds of hours of fun to be had with the Mi-8.

Thanks for the validation Holton :). I sort of understand ED and that not every object can be modeled to the extent the player's vehicle is. However, I'd think the campaign creators would do a few fly-throughs and realize that the campaign suffers from these issues and would be better off doing something different. For example if they flew just a little higher above the trees the maneuvers would not be so alien to a real helo. What kills me is that they tie it to mission success sometimes: "stay in formation" or "lost contact". The other bit I'd love to see is rather than just saying: "flight taking off" which is only a start, but at least give a direction: "taking off heading xyz". So when my overloaded and physics bound helo can't angle up to let me see the other helos I can at least be going in the same direction. So there are other things that could be done to offset this poor AI helo behavior...if only someone would bother to thoroughly test the missions.

I've just finished what I'd call a frustrating night of flying the Mi-8 in 1.5.7. Any time I have to fly formation with another Mi-8 as lead its a nightmare. On good missions (6, 7, etc.) they just abuse their lack of a physics model and speed up and slow down using maneuvers not available to the pilot. However, once you start going over ridges (like in "Encircled") its totally bananas. The mission has them fly right over the canopy, but then they pull up into 20% climbs, slow down, and then dive before crossing a ridge. The result? ridge crossings below ETL speeds. Keeping in formation with AI pilots is mostly a non-starter. They appear to be unaffected by gross weight, engine power or any other limiting characteristic. Are others experiencing similar issues when paired up with AI as the lead helo?

I'm also interested in how they came up with the grid numbering (10x10) in the top image. Does anyone recognize that system? AFAICT it is not MGRS or UTM, or even similar since the indexes change from square to square.

Cool. Thanks for the follow up!. Final data point. I went back to 1.5.7 latest release version and re-flew Spring Tension missions 6 and 7 without issues.

No, I haven't completed a mission in 1.5.8. I wasted a night on mission 6 trying to deterrmine the cause and eventually by-passing it via flightlog modification. Then when I had the same issue on the next mission I reported this as well as here: https://forums.eagle.ru/showthread.php?t=198250.

FYI, I just reverted to DCS/1.5.7.11762 and verified that the issue is not present in that version. I tested only the 'on land' timer and not a stop condition. I'll test the missions later tonight when I have time and report back.

Confirmed, this issue is not present in DCS/1.5.7.11762.

Yes, I'm on 1.5.8. Specifically: 00000.338 INFO DCS: DCS/1.5.8.12667 (x86_64; Windows NT 10.0.16299) 00000.338 INFO DCS: DCS revision: 132665 00000.338 INFO DCS: Renderer revision: 14969 00000.338 INFO DCS: Terrain revision: 14987 I'll read up on reverting to an earlier version and test it out. Also for context, this post is in reference to the "Spring Tension" campaign.

FYI, game version info: 00000.338 INFO DCS: DCS/1.5.8.12667 (x86_64; Windows NT 10.0.16299) 00000.338 INFO DCS: DCS revision: 132665 00000.338 INFO DCS: Renderer revision: 14969 00000.338 INFO DCS: Terrain revision: 14987 I don't know when this issue started. I'm assuming recently since it is affecting a campaign that must be reasonably well tested.

Do you want me to attach tracks from missions or a sample mission where it is easy to observe?

It appears that the land command available via advanced waypoint actions is now permanent. When the task completes the unit does not resume travel and continue on the next waypoint. The Ka-50 for example just ejects. An Mi-8 shuts down its engines and the crew leave after some point. This happens with the "on ground" option or together with a stop condition (e.g. time or flag). For me, this is screwing up the "Spring Tension" campaign. Are others similarly affected?

In missions 6 and 7 my flight members/leads simply land and don't take off. In mission 6, the evacuation of the first pilot stalls when the Mi-8 lands and turns off its engine. In the subsequent mission we all land at Shpora and announce readiness for take off, but my flight-mates again power down their engines and stall the missions. Was there a recent change to the land task and the "on ground" timing that allows them to spin down and not resume their flight plan?