NightMan

After destroying some vehicle it blows up and starts smoking. However, neither the smoke nor the flames appear on the Shkval TMV.

Gentlemen; I am trying to put up a mission with a few drones with AFAC as task. Either if I tell them to Orbit over an area or to "AFAC - Assigned Group", I always tell them to stay at 22000 ft, even in the Orbit Task. The problem is that after a while they decide to start descending down to around 14000 ft and they get shot down by SAMs. Why are they deciding to descend? Teste de exequibilidade.miz

+1

+1

+1

IT WORKS! And it's extremely simple to setup! Great work! A guy was insisting with me that it didn't work, but it does. I just spent an hour helping people set it up and experimenting with it.

Still happening. Demonstration Track - 008.trk

On this one I managed to recover, but the brakes didn't work, so I overshoot the runway. Demonstration Track - 007.trk

And here is yet another one. These are all maneuvers I'm used to do. The new performance may well be closer to reality (doubt), but that means all these years we have been using a wrong model. Demonstration Track - 005.trk

Here is another one. I have been able to pull out of a few of these situations and land safely. It was a bit like this: The tracks are at the [4YA] server somewhere in TrackView format. Today I'm not having such luck though. Demonstration Track - 004.trk

Here are a few tracks. I've been having this problem very often in the last few days. It doesn't even get the pilot to black out. Just rips appart. Demonstration Track - 003.trk Demonstration Track - 002.trk Demonstration Track - 001.trk

I seldom say this, but the programmers at Eagle Dynamics did a remarkable job with these two last updates (two if you are in Open Beta and one if you are in Alpha). Most of the bugs which were plaguing the game for a very, very long time were finally addressed and corrected (apparently). This is was one of those annoying bugs. Congratulations! Very good work. Thank You very much! For some reason though, it didn’t make into the Change Log list. But that is of lesser importance. One thing they list in the Change Log, concerning Flaming Cliffs by Eagle Dynamics, more precisely the Su-25T, was what they called the “Green blot”. I really don’t know how the HUD appears in real life Su-25Ts, but that “Green blot” to me added some realism. It didn’t cause that much problems, at least to me, perhaps because I used to dim the HUD when in low light conditions, until the “Green blot” disappeared. It worked perfectly and seemed very real. Nevertheless; good work!

Thank you Sir! Ufffff. Relief!

Yes, this problem is related with the chat function. And, of course, it doesn't happen in single player!!! It causes problems not only to the RADAR but to everything that depends on modifiers. You talk about other posts; could you provide the links, please?! Negative.

Yes, yes, yes. It just needs some TLC. Just like the Su-25T got.

This problem is still happening in version 2.7.5.10869. And it is really annoying because sometimes you can't see a thing behind.

Well; undetermined then?

And another update was released and this bug is still pesking our flights.

As to the track; I've noticed that the upload limit is ONLY 5 MB. Any Multiplayer track has easily more than that. What shoud I do then? A track file is just a Zip file with a different extension, so there is no point in compressing it.

I am so sorry. I usually clean temporaries at the end of each week. Next time I will put the track aside and upload it.

So it will work well with DCS for sure. They will both be buggy.

Sometimes the vehicles burn and cast smoke in a strange way.

I just tried it again, this time without even leaving the ground. I started the left engine and the right one spooled. Then I tried moving the antenna up and down and it didn't work. This control is tied to LCtrl and Hat Switch. I did it only to upload the log file and the track file you suggested. I doubt it will show up in there, but I don't have anything to lose. However, I couldn't upload the track file as it is WELLL OVER 5 MB, and there is no point in zipping because it is already a zip file with a diferent extension (TRK). dcs.log

I tinkered with the chat window until the bug manifested itself, making sure to note all the keystrokes I inputed. I managed to land. When on the ground I tried to redo what I had been doing before, and, to my surprise, after a few experiments, the effect was undone. I am now able to reproduce the bug. You open the chat window - <TAB> - (UI Layer: Multiplayer chat - mode Allies); Then you select ALL - <CTRL+TAB> - (UI Layer: Multiplayer chat read/write all); After that you hide the chat - <CTRL+SHIFT+TAB> - (UI Layer: Chat show/hide); The bug happens. The controls on the stick which depend on a keyboard Modifier stop working. To undo the bug you proceed unhiding the chat window, opening it and finally closing it. For that you unhide the chat - <CTRL+SHIFT+TAB> - (UI Layer: Chat show/hide); Open the chat window - <TAB> - (UI Layer: Multiplayer chat - mode Allies); Close the chat window - <TAB> - (UI Layer: Multiplayer chat - mode Allies); I did all the steps using just the keyboard. The controls depend on each one's configuration. For me they are: TAB CTRL+TAB CTRL+SHIFT+TAB Then CTRL+SHIFT+TAB TAB TAB Could someone please warn EDiots about this and ask them to solve it? Thank you very much.

.