zerO_crash

I at least have never needed to use the second discharge, the first one always worked with immediate effect. However, it makes me wonder. Would there really be any negative effects if the pilots got a fire warning (during combat) and happen to use the distinguisher without cutting off the fuel (red levers) and shutting down the fuel pump (switch)? I´m thinking a pilot error here or a stressful situation. The only one I can think of is the discharge not being able to put out fire, but would there be anything else?

The new battlefield between the superpowers is really economy and market dominance. Wars and conflicts have become unethical, unconstitutional and generally uncalled for in today´s society that screams "hugs, not bullets". Also, it costs money, which is the primary reason in this money-driven world. Although history repeats itself and thus we will have a major armed conflict at some point, right now we are in a phase where even superpowers avoid conflicts as it works against their PR and agenda (remember why US lost in Vietnam? it was due to lack of support from civilians back in US). Officially that is, as PMC´s (often backed up by the governments -> Blackwater) are on the increase and the only ones with the incentive to carry on armed conflicts, they got nothing to lose. As to training, well you cannot say that Helo vs. Helo never happens IRL. It has happened before, although there are few documented cases. As such, there have been units both in US army and Russian army that have had additional training on helicopter tactics in case of a clash. There are no conflicts as of today where such a situation would happen, but that´s not how military operates. They train and prepare for the worst, keeping at pace with whatever their arch-enemy has at hand. If they were to only focus on what´s going on today, there would be no need for all this advanced tech that superpowers currently wield. It´s the "what if"-scenarios that have driven the technology and tactics forward.

It has a radar screen, which shows much good info not related to radar as well. It´s not a MFD, and you´re not going to see a RED aircraft with one for some time I am afraid. Secrecy

The question is if one will be capable of dynamic flight-plan creation in session, or change it, so that the map inside the cockpit updates. Would be really neat. I suppose creating such a system should not be too problematic, given that such systems are already in-place in other modules.

You are correct. Page 250 in DCS manual just for reference. @Rudel_chw Aside from what sLYFa stated, I cannot spot any inconsistencies. Nice! )

What people don´t understand is the grand scheme of tactics in general. They run alone to AO with their precious aircraft and wonder why they got shot down. "If I died, it must mean that the enemy has a better radar, weapon, aircraft, etc.... I mean, it for sure cannot be that my tactics suck or my battle plan, control of my aircraft, knowledge of what my aircraft excels at and it´s limitations, etc...". IRL, who sees first, usually wins. But you have to add all the other to the formula. Since Ka50 doesn´t have RWR, it does mean that fighting in a SAM/radar-contested area is not it´s primary task. Logic would suggest staying behind the SAM/Fighter umbrella and sniping from 8-10km. That´s just an example of it´s application. One thing is for sure, with the modern SAM´s, manpads and AAA-systems such as Tunguska, you are pretty much dead meat in a helicopter, be a Ka52/Mi28/Apache/Cobra. Those missiles move so fast, that the early warning gives you time to pull ejection handle before it hits you. That´s how much your countermeasures are worth when going in dumb without any proper tactic. Forget any relevant avoidance manoeuvres, as these rockets eat distance like nothing. The prerogative in this thread is naive, when it talks about this phenomenon of "balance" and "equal units". That´s not real and neither something this sim attempts to replicate...

I´ve been AFK some time due to reasons. Anyways: In the sim, the actual forces acting on the pilot aren´t modelled. For example, the collective can be pulled just as fast with the collective brake engaged, as without it. This is nonsense as IRL, the pilot, without holding the the collective brake in (which he normally would never do), would have to fight an immense force holding the collective in place, but could still move it by sheer force of muscle. IRL, there are differences greater than in the sim. Also, the reaction time is faster when you don´t have heading-hold or altitude-hold engaged. There is a difference there as well. It´s 20% on cyclic and 25% on collective. Also, it works in a different way than you think. It does not remove 25% of your total scale, which the AP will always counter your movement with. Rather, when you win over the AP, it will standby and not fight you giving you 100% gain in the direction that you move the stick or collective. That´s why you don´t see bigger differences in reaction times. Small adjustments, falling within 25% is something it will correct. Kamov and Mil use the same type of trim. There really is no noticeable difference. We are talking about the way it works. Even western helicopters that have a click trimmer have it working this way. The reason click-trimming doesn´t work well with non-FFB sticks is because for every click you do, you would have to remember to center the stick, before clicking it again. Often you can hear the pilot holding the stick in a certain place, and clicking multiple times. That is for him to get the perfect centre for his current flight, as well as remove any type of errors in the trim (which always occur). If you tried to do the same, clicking multiple times without re-centering the stick for every click, then you are magnifying your trimmed input many times. It just isn´t natural, and doesn´t really work well. You need a FFB stick. I´ve flown the Ka50 since it was released. I know her very well If you wonder about something, shoot. Otherwise, I see there are some issues further down the thread below your last response to me, but it`s too much to correct. Again, much is misunderstood by many.

Gotcha, and I would agree with that. +1

You are jumping to conclusions too quick. You know that there are many reasons why a lobby can be ruined, and it often isn´t tied to how many people there are in that session, but rather who joins it. Often lack of planning from the pilots and badly made missions are responsible. This isn´t so much a question of price, because I´m sure that everyone wants to reward a good product with money, but rather execution. That´s what will decide how this affects DCS on a greater scale.

I believe that, and the team does great, I am impressed. Nevertheless, have a look here:

Absolutely agree on the AI improving, no doubt. But having read the russian side (that´s where I am on most), PilotMI8, Chizh and others have confirmed that even with the AI being improved, we are talking about an AI on a basic level that can spot, shoot, fly the helicopter in a straight line or circle for you, and not much more. Maybe in a couple of years we will get advanced algorithms that will allow us to make the AI do more advanced stuff, however that is still miles from what two human operators could do. And this last part that I mentioned is in "2 weeks TM". Look at F-14, AI does "ok" at A-A and that´s about it. For advanced A-A and A-G, you are alone. And I say that with respect to the devs, cause they achieved an incredible Jester considering the aircraft´s complexity.

There is a difference between not having a flyable module and still being able to join a server, versus not having an asset pack and not being able to join a server. Also, no one ever said that the majority of DCS community is online, quite contrary, according to what ED have stated. Most of us who are in clans fly singleplayer a lot. However just because it´s a rather small percentage online, doesn´t mean that it doesn´t exist. If it´s 2ooo people online right now, then creating servers with specific packs (that as opposed to not having modules, will not let you join a server) will bring that number to 20. That´s the issue. And if multiplayer is not important, then I wonder why ED used so much time with improving net-code, made it possible for dedicated servers and all the other multiplayer implementations. If that wasn´t enough, we are now moving into a time where new modules released finally feature multi-responsibility aircraft (F-14, L39, C-101, EB-339, Mi-24, AH-64D, F-4 and all the other upcoming multi-seat modules), thus making it optimal to feature multiple human pilots in one session. Flying in those with an AI is a cripple. This is definitely not something that should be neglected!

Although the idea is good, I am afraid that if "packs" with different units are introduced, it will split the community between those that have the packs and those that don´t, and of course those that have a mix of them. This makes sense for aircraft modules, but not so much ground units, which are the basic mission-making material. Another question is whether there is enough information about the different units such as SAMs or AAA-units to really make all of them. In the end, I would not expect to be making money out of this. For most of the people here, they care about shooting "something". Whether it is an Abrams A1 or A2 is not really that important, even more so when you start talking about buying the A1 when A2 is already in the simulator for free. If you decide to give this a try, make sure to not make a mistake of making too many separate "packs". In the end, it´s much better to have a single, more expensive pack, than 4 different for 5 USD each. Although the idea is good, I am afraid that if "packs" with different units are introduced, it will split the community between those that have the packs and those that don´t, and of course those that have a mix of them. This makes sense for aircraft modules, but not so much ground units, which are the basic mission-making material. Another question is whether there is enough information about the different units such as SAMs or AAA-units to really make all of them. In the end, I would not expect to be making money out of this. For most of the people here, they care about shooting "something". Whether it is an Abrams A1 or A2 is not really that important, even more so when you start talking about buying the A1 when A2 is already in the simulator for free. If you decide to give this a try, make sure to not make a mistake of making too many separate "packs". In the end, it´s much better to have a single, more expensive pack, than 4 different for 5 USD each.

I see "μA" there, meaning micro amperes. I am pretty sure that it´s equipment for measuring static electricity acting on the helicopter. The scale seems to show 300 and I guess 600 micro amps. Not sure why it goes both ways though, but if a rotor blade hits a particle in the air, it creates static electricity on the airframe. The more particles (dustier), the more static electricity. It looks like it´s test equipment though, not something I would expect to see on a production helicopter. Americans did a similar test: https://apps.dtic.mil/dtic/tr/fulltext/u2/282087.pdf

What´s really interesting, is that they are making the D-version. I would expect the Longbow radar to be quite classified still with regards to acquisition modes, ranges, efficiency and scan patterns. I am also surprised that they have sufficient info with regards to the glass cockpit and the different electronics. AH-64 has generally been kept on the secrecy-level of F-22/35 all those years. It´s going to be interesting to see how this helicopter performs against my russian babies

This is gold! Nice

For the sake of this thread, it´s interesting to see how long this pilot holds the trimmer while making adjustments. He does it most certainly to avoid fighting the cyclic-forces. He lands by holding the trimmer in. It´s a Mi-17 for reference, but applies to pretty much all russian helicopters. Check 03:56 and onwards for observing his thumb move when he trims (you can also hear the clicking):

I guess technically, if you wanted to, you could design a planetary gearbox (just as the real thing has), where you could have the engine run at maximum RPM and the cog within the planetary gearbox be used to "throw over" the excessive energy. That by giving the engine a different set of cogs to work with to maintain stable rotor RPM given the pitch of the blades and load. However, I´m also seeing only negative effects of such a configuration. Engine at max rpm would mean higher fuel consumption, even when not needed to, as well as reduced service life for the engines as they operate on the maximum all the time.

Then you are wrong, AP channels never "disengage" when you move the cyclic/collective outside of their 25% authority without trimming (The light on each AP-channel indicates their operation, and it never turns off when you hold the trim-button in.). This is both in the manual, my sources, as well as can be tested in flight. If you have all channels AP channels engaged (except FD), and trim the helicopter for say 200km/h (nose down), heading 090* and altitude 40m ASL, then fighting the AP and moving outside of it´s authority will give you nothing if you don´t hold the stick in the new position or trim for it. If you let go of the stick, the helicopter will return back to it´s trimmed parameters. This is also a bad technique of flying because you are "fighting" the helicopter, and as a real pilot, would probably be tired by the immense forces acting on the stick, after only a couple of minutes of flight (that´s why the exception here is an emergency). Not only that, but the helicopters reaction time when doing manoeuvres is severely impeded. When you hold the trimmer button in, you put AP Heading Hold into standby for the duration of you holding in the trimmer, it never turns off. As for AP pitch and bank dampeners, nothing happens to them, they are still operating, you never put them into standby with the trimmer. However, angular stabilisation gets suppressed until you release the trim-button. There is nothing to argue here, this is how it works. Also, it´s important to specify what AP channels you talk about, because they work different. Also, FD =/= holding down the trim button. FD is an AP mode, and holding the trimmer button down simulates FD, but it is not FD per se. The obvious difference here is that in FD mode, you would still trim the real aircraft because of the forces acting on the stick, whereas with trim button held down, you are simulating FD, but have severely reduced the forces acting on the stick for as long as you hold the trim-button in. That is a major difference between those and actual flying with them engaged (FD or Trim engaged/pressed in). The last part you write is correct, but you draw incorrect conclusions from it. The "small levels" you talk about are within 25% of the range of the trimmed point. Where did you get lost?

Thank you very much.

@BIGNEWY Any progress on this bug?

A) I don't preach, I'm pretty far from a priest last I checked. B) I haven't told anyone what they should do. For the past couple of posts you have provided no relevant argumentation, only posting personal crap that diverts the discussion off it's initial topic. You have already showed me of what calibre you are when you wish me or anyone else bad. You certainly have a lot of catching up to do with your manners. We'll end this here.

No one said it's ok, and it's not left for years, don't exaggerate. Funny you would compare a simulator to buying a house or car. Guess that nails your lack of perspective. In principle, although both purchases, you would never buy an apartment or car at such terms, and it's logical, cause it's a different good and price-point altogether. Again, what are complaining about? Why not complain about Windows, iOS or any other major software that has bugs? According to your, rather flawed, logic, there should be no bugs in those operating systems given how long they have been out.... Also, if you ever buy yourself a house or car, I suggest that you do proper reading, cause no lawyer will consider your "decency". Rather it will be a matter of what's worded and not in a given document or product description. If you settle for the first, then you are in for quite a treat. I am more than eagerly awaiting for this module finished, just as anyone else. I am not advocating for unfinished products sold at full price and left to die. However patience is a virtue, think about that. I will also add that wishing someone bad is not the noblest of things to do. Maybe you ought to apply some of that "decency" you talk about, to your rethoric, and start with yourself before demanding from others.

Hehe, we agreed pretty early on after MIG21Bis released that it is a fantasy-weapon IRL, you would need a single beam radar, like RP21 (not RP22 Saphir), to target the missile. Otherwise if KH66 Grom was simulated correctly, it would behave like Vikhr at the early stage of flight with RP-22 (dual beam radar) until spinning out of range of one of the radar beams. This is one of the few weapons in MIG´s arsenal that were added for fun, and because no other variants of MIG21 will be simulated in the upcoming future )

First of all, not changes are always posted in changelogs, many smaller fixes are not even mentioned while being applied. Again, who ever stated that the attention a module get´s is relative to the price? What you pay for is the complete product, and by that, the amount of work needed to complete the project, i.e. the magnitude of the project. That says nothing about how much work is going to be put in over a specific time. Consider UH-1H Huey, it was released in June 2013 (7,5 years ago!!!), and it is first now that we are getting multicrew (which was announced back then) with proper functionality and depth. As the team (Belsimtek and ED) themselves said, much of the core code had to be brought up to modern standards and rewritten. No one initially could guess how much needed to be done to finish this undertaking. Furthermore, given the nature of software, every new update can break other things. One good example is Ka50 where one of the updates broke laser guidance (for Vikhr) as well as HUD reticule and elevation of outer pylons. It was initially stated that Ka50 BS2 would not receive any updated until BS3, that it would be done in one go with the new release. Again, the new bugs made the helicopter unusable, forcing ED to re-allocate parts of its team to fixing the issue. For this, other projects suffered by extending deadlines. Another great example is MiG-21Bis. Ever since EDGE arrived, it has been a cat and mouse with LN trying to catch up on the ever changing lightning effects introduced practically on a patch to patch basis. This has been going on for a long time before it was finally looking like roughly like it should, but there was still much to be done, and the new upcoming patch has indeed most of the new fixes. For this, their other projects suffered. Point is, there are many standing issues, that date way back to the old engine, issues that are not counted in 1,5-2 years old, but rather 8 - 10 years old. Issues that were on purpose held back to await new engine being released in order to avoid having to work 4 times with updating the same element. Additionally, I want to stress out that this whole thread is a fest of expectations put by consumers on ED, something that ED never promised anywhere, for example your statement with how much a module costs vs. how much attention it "should" receive. Again, stick to facts and what you paid for, and not guesstimation and "I think it should be like X or Y...". Although I agree with the sentiment in this thread, and want the Yak52 to be finished and major bugs be solved, I kinda understand why it all has been taking time. It´s ok with constructive criticism, but this is going in circles now. And again, by people who are not patient and should never opt for a beta product. Stick to final releases, and it will do both you better, as well as show ED whether it´s a good idea to do pre-release business. Just to clarify, I don´t post toxic stuff. If my responses seem harsh at times, it´s because I respond in the same manner that I see a fellow virtual-aviator write in. Mutual respect is not always apparent here (I wish it was), but there are more propper ways to converse than what has been done in this thread. Initially me explaining the "why" for delays, and all of a sudden it get´s personal, nearly fanboism (really?). In that case, I spare no word for pointing out where a fellow aviator makes a mistake in his assumptions. Regardless of the tone in this discussion, I guess the point has come across to ED (considering BigNewy chimed in). Let´s wait and see what 2021 brings.