metzger

There should be also a probe Heat monitor that illuminates the PROBE HEAT caution light in case the airflow decreases under certain value e.g. if blocked by ice. Apparently it doesn't work now. EDIT: Also multiple FLCS FAULTs should occur in case of blocked air data probes and sensors.

Not sure if it is related, I also reported in the Mi-8 forum but the issue might be caused by this one. In Mi-8 Campaign Spring tension Mission 11 there is a WP hold which should be stopped by a Stop condition. Hold is set on SP and should be stopped by a flag. The trigger which should turn on the flag is triggered but the units never start moving, seems like the stop condition for the hold doesn't work.

Kurshum do not advance in the village and mission stuck. I can see the trigger in ME where kurshum should enter a zone in the village and spawn some units, the voice over which tells them to advance is triggered but they dont move.

SRS is far superior for Coms and it will be for a long time ahead probably. I see no reason to put my VR and run DCS for preflight or debrief looking at tacview(for example) when TS is much more feasible, doesn't take 15 minutes to load and it is not 180GB. So is the reason I see the DCS Voice as completely useless feature in it's current state.

The artificial reflections are indeed very bad and they do that on all modules. I hope someone capable will quickly make a MOD to remove them. Why ED keep adding those is beyond me, may be they like it :megalol:

Overall I am happy with the update as well. Cockpit looks much better than before even tho it is not something impressive unfortunately doesn't even get close to the art work of heatblur. So, it is better than before and I hope they will try a bit harder with the BS3 visuals !

I believe DCS lacks campaigns which are aimed for training a.k.a L-39 Kursant or Maple flag ones. Speaking of which, I suggest you get one of the few training campaigns and fly trough it while simultaneously learn about airplane aerodynamics, a good source of information about basic flying: https://www.flightliteracy.com If you like the A-10C I suggest you start with the following: https://www.digitalcombatsimulator.com/en/shop/campaigns/a-10c_bft_campaign/ Another one is for L-39: https://www.digitalcombatsimulator.com/en/shop/campaigns/l-39_albatros_kursant/ Surely for those you will need the respective modules. Always carefully read aircraft manuals provided with DCS and learn them properly. And last but not least, If you want to learn and get more serious, I very strongly suggest you finish DCS Academy: https://forums.eagle.ru/showthread.php?t=255633 Very nice group of entusiasts running it just for people like you.

Thanks for the answer. Yes I remember reading that you are waiting to see how MC for the UH1 will go (or something in that sense) and so is why I have opened the thread. Fingers crossed Kiowa and hope ED will provide you access :thumbup:

I said "considering it was not meant to be released" so this is a state which we should not even see it. Taking this into consideration - yes it works very well a.k.a looks very promising. Of course there are issues.

" also reduces the mouse area when in VR." basically my issue is this. I can't use the whole area in VR. How do you adjust it with User32.dll ?

I noticed that you can't use 100% of the FOV for mouse movement, especially bad is the lower limit where even if certain switch is within field of view, you can't move the mouse over it unless you move your head down so it is almost in the center of the screen. This makes some switches really hard to reach with the mouse even tho they are easy to see. I believe it is tied to monitor resolution, aspect ration or both, tried to change the res in DCS settings or on my monitor display settings but this didn't help. Oculus rift S with 1920x1080 monitor. I will appreciate if ED or someone else can help to overcome this limitation via lua or other way possible.

Well, technically shooting within NEZ is a higher PK shot as the target can't outrun the missile he has to maneuver, notch, chaff whatever else but just turn cold and outrun it wont work(unless he can accelarate but NEZ doesn't know that). So in your opinion what is the difference in PK 300 feet outside NEZ vs 300 feet inside NEZ or why exactly that is the distance where NEZ is calculated ? - I can tell you as I have already tested it :) This is exactly the distance where if I am cold the missile will or will not catch me as long as I keep the same speed for the attacker and defender. The time for the 180 turn doesn't matter really, it just tells you that during he is turning you are still closing in and he will be or not be inside nez depending when he started the turn. And you don't have to trade energy to turn - it is called energy sustaining turn, but I understand what you mean. This really doesn't matter for NEZ calculation as every aircraft will have different energy on the same altitude/speed - different aerodynamic performance, different engines, weight etc.. EDIT: E.g. bf109 at 1000feet with 250 knots has less potential energy than F-16 at the same alt/speed but NEZ is the same as your aircraft systems doesn't know that. So if you shoot on the edge of nez against bf109 you will probably kill it, while the f-16 will accell and outrun the missile. But NEZ will be the same for both at the moment of fox3

If you STT a target at 0 TA (completely cold), you will see that Max and nez are the same. Of course you can make 180 without loosing speed. You can see also that during the target is maneuvering, the max range changes based on aspect, while NEZ remains fairly similar in case the target or you remain with constant speed. So is why I believe NEZ is a function of speed and distance to calculate the max distance where the target can turn cold and outrun the missile. NEZ can't take into consideration maneuvering or energy state per se, as it has no idea what the locked aircraft capabilities are, how hard it can maneuver and so on.

gas turbine is still a jet engine, so it makes jet sound :)

I believe NEZ doesn't literally mean you can't survive the shot. It just means that if the target is cold and keeps the current parameters, the missile will catch him. As soon as target changes parameters(speed, altitude, manuever etc.) or start pulling G, this is no longer valid.

By lowering the collective I meant during the approach and while the decent rate is still under control, trying to compensate the steep approach by slowing down fast, pitching up and dropping the collective to avoid climbing, then transitinal lift is lost and you enter VRS before you know it. At least this is my observation in the sim from watching other players. I have no issues with landing any of the hellos personally.

There are 86997 registered forum users. I highly doubt DCS player base is 900 players and the rest are just here to chat...

The biggest factors for why it "feels" more difficult in DCS imho are below: 1. Cyclic works very different irl from what the majority has for sims and this makes big difference 2. Collective - IRL the collective is much longer lever which gives it much more precision from our throttles. 3. Last but not least for sure, bud feel. IRL you can "sense" the rate of descent/climb/speed and general attitude and therefore react to it much faster and intuitively then in sim, especially 2d monitor. VR helps a lot for helos, still no bud feel tho. Most of the time we simmers trigger VRS because we lower the collective too much, as we don't have precise enough hardware control. At the same time we don't have our eyes on vvi 100% of the time as we have to cross check everywhere with our single pair of eyes. While in real live your but feel is sensing non stop, so you will feel the descent rate while your eyes are focused outside and intuitively check the vvi and adjust collective if needed. We can get used to do it well enough in the sim with enough practice of course but it is just a little more challenging I believe. I am no pilot irl, but I have many hours in CAR/Motorcycle racing sim games and IRL and it suffers from absolutely the same issues because of the lack of real hardware and feel of the motion and environment.

+1

It seems the 29A are active from the start with full armament :) EDIT: with R-27 and R-60

I can confirm, brightness works by clicking it multiple times, I was trying to hold it instead. However decreasing brightness fixes it partially, 13WELT_JankeS expressed it better "The font got thicker and fits together making reading difficult" weirdly it is only noticeable when it's dark. Never tried night flying in the viper prior to 2.5.6 so it actually might be from before like that. EDIT: KA-50 Abris has the same thick font during night and I can confim it was not like this before.

As we have UH1 multicrew working very nice, considering it was not meant to be released yet, can we expect to see MC for the Kiowa ? This is really the buy/no buy difference for me personally. Thanks.

Yeah, tried it but it doesn't seem like its working :)

The old MFDs were much better. Now they are waaay too bright and the letters too thick much more difficult to read. LG lights and JFS Light are waay too bright. All lights looks exaggerated from close distance. EDIT: During the day it is ok. In the dark, MFDs too bright and font too thick.

F-14 especially A is cold war too.