primus_TR

I know this is an old post, but if you or anyone else is interested, I used winch grease, the kind that you use in winches on boats, to get rid of the friction. I applied plenty of it both underneath the circle base which supports the spring, and into the gimbals. Worked a charm. Any non-corrosive grease should work, I suppose.

In my case, keyboard controls stop working also, so it must be a different issue.

Due to the torque and fuel consumption issues with the latest engine modeling, I am using the old flight model: /FMOOptions.lua New_engine_model = false Unfortunately, I do not know what exactly caused the problem so it is not something I can reproduce at will; hence, I can only submit a track in which it occurred when it occurred, which was after about an hour into the mission. The reason you cannot reproduce is probably because the track was recorded using the old flight model. If it will be of any help, I can rerun the track on my end and record a video of it. It is bizarre: Cockpit instruments showing straight attitude. External view showing ~40 degrees bank, 20 degrees pitch up, heli flying straight without loss of altitude. It won't accept flight control inputs (neither keyboard nor hotas), but cockpit systems remain interactable. Anyhow, I believe this is a significant bug, that's why I took my time to report it for I want to see this module reach perfection. So, do as you wish with this information. Ciao, Calabrone. Il consumo di carburante e i problemi di coppia con la nuova modellazione del motore rendono spiacevole far volare l'Huey in questo momento. Ecco perché sto usando il vecchio modello di volo. Non intendo utilizzare il nuovo modello di volo finché non risolveranno i problemi. Ciao

Well, very refreshing to see a track-documented bug report being ignored.

I started having this very strange bug; it is not easy to describe but I'll try (track is attached): On Caucasus map, using MT version: 1. Heli becomes uncontrollable, as though I plugged off my HOTAS. The joystick controls are normal, though, as they work normal in the settings/axis controls page and keyboard flight controls also do not respond. 2. All buttons in the cockpit are clickable, radios work etc. 3. The heli is stuck in an impossible attitude (50 degrees bank, 20 degrees pitch up) yet maintains level flight. 4. Weapons fire, but after a couple of rounds, tracers disappear. Same with flares. I can hear the flares shooting, but no flares show. 5. ESC menu works, I can exit the mission. I can also exit the helo by ALT+J. Track is attached (a long flight, an hour+). The problem occurs close to the end of the track. Note: I'm using the old flight model. This happened twice when flying a Briefing Room-generated mission. Not sure if it is possible for a mission to break the aircraft dynamics like this, though. I have never before encountered this bug. It may be somehow related with the co-pilot autopilot. Both times, it happened when going back and forth from the autopilot. uh1_out_of_control_bug.trk

This, plus too much head wobble and too much left pedal needed when hovering and taking off.

Both methods (overflying and Shkval) work for me, except when using Shkval for INU alignment, it must be locked on to an object (TA must appear). You cannot just point it to an empty field, lase and use that location; there must be an object (a building, vehicle, etc.) that you can lock on and TA must show. The overfly method works perfectly. You might want to review your steps.

+1

It could be a heading alignment mishap. You're not inadvertently flipping the mh/gyro/man switch while hovering by any chance, are you?

If you (or anyone else) still need this information: Using the Magnetic Heading for alignment is more practical than using Manual alignment. For alignment by Magnetic Heading (you can use this both when landed or in the air): 1. Check the magnetic variation for your location in F10 map with the compass rose. 2. Dial in the magnetic variation (for example, for Minvody, it is 6.7). 3. Set the Man/Gyro/MH switch to MH 4. Wait for the HSI to align, and then switch it back to Gyro. That's it for MH. For Manual (you can use this only when landed): 1. Check the magnetic variation for your location in F10 map with the compass rose. 2. Note the compass indication. Your true heading will be compass heading plus magnetic variation. (e.g. if compass shows 210, than your true heading will be 216.7 if at Minvody). 3. Set the Man/Gyro/MH switch to Man. 4. Dial in the true heading. 5. Wait for the HSI to align, and then switch Man/Gyro/MH back to Gyro.

that right there seems to be the culprit.

At altitude, even full left rudder is sometimes not enough when taking off. This was the case in Elbrus rescue mission. I picked up the survivors from mountain top, and taking off, even full left rudder was not sufficient to keep her straight. Never set foot in a Huey, but this seems a bit off.

Don't forget to fully open the throttle and then close it back to idle stop position before cranking up.

Thanks. Very useful.

Well, guess what. The reason the course autopilot veers off course is because, well, it disengages by itself for no apparent reason (when flying straight and level). Adjusting the collective results in sudden and abrupt yawing, perhaps that's what's messing with it. Not sure, but anyhow, looks like I must keep an eye on the green light and heading indicator.

I can confirm that after the update 2.7.11.22041 (30.03.2022), this issue has been resolved; the comms are working normal. Thank you to all who have helped to fix this bug ~S~

I am not talking about the yaw ap channel issue; it doesn't bother me, as I got used to how it works from Black Shark. This issue is related with course following autopilot, not the ap channels per se. Since there is no official manual, I am not %100 percent positive it is not a mechanization error on my part, but it seems to be a persistent problem. After some time, the autopilot can no longer keep the course, and can deviate as much as 40 degrees from the set heading. I've ruled out rudder coordination, and wind (tried in a no wind scenario). I will try and record a track today, and maybe someone can point out if it is a step I'm missing.

What I said. After a while, the course following autopilot deviates from the set course. No wind, no crabbing, with yaw channel set to the same heading, it veers off course; can't hold course. I'll try to make a track tonight.

Besides problems with the pitch channel, the course autopilot cannot hold a steady course on the set heading. To refresh on other unresolved issues, you might want to check out the Bugs and Problems subforum for the Hind. Sorunları çözmek için yeterince çaba gösterilmediği konusunda yapıcı eleştiride bulunmak için "Amerikalı" olmak gerekmiyor.

Will check

I have been a big fan of ED since Flanker 2.0 times, and will likely remain so. But honestly, the big picture is that half-baked products appears to be the name of the game here. A couple of items in the update list, even minor ones, would have made many folks happy. And lack of it gives the impression that Hind development is shelved at this time. I understand that they need cashflow and AH64 is probably one of the top selling modules, so they're concentrating resources on it, but c'mon... not a single line for the Hind in the whole list? Slap in the face really. Knowing ED, I had postponed my purchase of Hind for a long time, and resisted the temptation, until the current SimFest discount. What can I say? Just keep waiting, I guess.

I was thinking about purchasing the AH64 also, but I think I'm gonna wait until the mi24 gets some much needed attention, the autopilot issues in particular. It was really disappointing that there was not even a single line for the Hind in the update list.

4 parts ethanol + 6 parts water = true vodka

Looks like I figured it out: the two files that need to be edited are: others.lua and combat helpers.lua. Now I can generate mig21 vs f5 missions

Hello, I've been messing around with the Mission Generator templates. I tried to add Mig21 flights, but Mig21 is not included in the groups dropdown menu. So, I tried to edit the others.lua and combattemplates.lua (or somesuch), and managed to have Mig21 flights listed in the groups menu to add to a template. But, when I push the 'generate' button, no units are generated. Can someone direct me to a source or information that explains how to add aircraft which are not listed in the groups dropdown menu to the Mission Generator? Any help would be greatly appreciated. ~S~