TheFreshPrince

Thank you guys for your time so far! To me it looks like it comes off the rail as stupid, it doesn't even track from the beginning. I posted 3 encounters, which should prove that it doesn't happen very rarely, but somewhat frequently. Although it is hard to replicate. I certainly could post many more screenshots or try to create more track files. But I think the problem is clear. Now, while one can argue here if it is realistic that it randomly fails or loses track, it is my question if this is how it's programmed in DCS. Because I don't know how it is intended to work. From my experience, it seems very random if it hits or if it doesn't. Which makes it hardly usable, except as you said against notching or cold targets, but then you still need to get rather close. But heads on, sometimes it can track at very long ranges and then again it doesn't track at all. Maybe it should be more a question of why it even has such a long range if it's not usable anyway and if it should even give you a launch authorization if it doesn't track afterwards. Or if it just has a random failure programmed into it, it would be interesting to know how often it is intended to fail.

Hi, der Knackpunkt bei dir scheint die Auflösung zu sein. Erstens ist das Format super weird, selbst Google gibt für diese Werte kein sinnvolles Ergebnis raus. Ist keine 4K Auflösung, sondern irgendwas stimmt da nicht. Soweit ich das im Forum gelesen habe, gibt es aber auch für 4K aktuell selbst mit absolutem high end Zeug (also mehrere tausend Euro PC) keine wirklich tollen FPS. Mit deinem PC solltest du aber alles mindestens auf high stellen können. Ich habe z.B. ein schlechteres/älteres Setup und spiele DCS auf High Settings mit noch paar extra Settings aktiviert und habe selten unter 30 FPS (auf dem Boden manchmal wenn viel los ist). Dafür nutze ich halt "nur" eine 1440p Auflösung, die aber imo völlig ausreicht. 32GB zu 16GB hat bei mir übrigens einen großen Unterschied gemacht bezüglich Ladezeiten und FPS am Boden und ist gebraucht nicht teuer. Gruß

no override, just automatic LA

Finally managed to get it on track ;/ very difficult to reproduce against AI because I rarely get launch authorization heads if I'm not very close (very often the R27ET has the exact same range as the R73)... I don't know if that's intended. You need to fast forward to the 3rd encounter against the F15 as I didn't get to shoot the R27ET against the first two targets (as I said, the range usually is very small if heads on against AI). Also against AI it seems to track better. In multiplayer I get to shoot it from further distances more often. So it happens more often there, but the track files are so big that I can't upload them. On tacview it's frequently observable though. But I don't get why it happens. There is no reason for the missile to go stupid. It is as if the missile fails randomly (unfortunately not very seldom). Tacview-20221116-170020-DCS-Test.zip.acmi R27ET#1.trk

You mean Mig29S? FC3 comes with its own training sessions, small campaigns and missions which are great to learn the basics. If you wish to learn more about A2A combat in the SU27 and MIG29 I can recommend Sukhoi Gaming Channel. Also the DCS flight manuals explain a lot and are great to learn from. To compare them, it's best to fly them and find out which feels best. PS: On topic, I like the GR tutorials. They are very basic, but they teach you enough to get started. Also they make it fun to watch and enjoy the learning process.

Same Tacview file, just shortly afterwards: Again launch authorization from the R27ET, but doesn't even bother to track against this F16:

I'm having problems with long range shots against hot or notching targets with the R27ET. Even though I get a launch authorization, the missile doesn't track at all afterwards. It just flies in a straight line at it's altitude, no reaction to anything. This happened on multiple occasions on multiplayer servers. Since the bandit doesn't get a warning from IR missiles, there is no real change in course from the bandit, no flares, etc. Is this normal with long range shots and the missile is just not good? Why does it give LA then? Some kind of ECM by the bandit? Or is it a bug? I'm adding one example from tacview. Since this is from the GS server, the file is too big to attach. But you can get it from their server, the file is called "Tacview-20221112-175935-DCS-Server_1_Operation_Urban_Thunder_V7.1.5.zip" and you can see the timeline below.

This mod looks really great, thank you! I couldn't use it in multiplayer though, it didn't pass the integrity check. (2.8 open beta)

I like to fly guns only dogfights against AI at ace level for training and I find it more challenging than before. I also found that they now like to crash into the ground more often (even at fights above the sea). I can still kill them although I'm not very good, except the F-16. The F-16 at ace level seems unbeatable to me, it's just flying perfectly around you at high speeds until you make 1 little mistake.

Good job! I meant to wait a bit for your wingmen, but to take off before them and engage first. Exactly as you did. Otherwise the F16 come too close and you can't get the altitude and speed advantage anymore. I guess the mission setup is not ideal. If you're not within the MAR (minimum abort range), you can theoretically defend any missile. The rocket motor will only last a few seconds and after that it will lose it's energy. By diving down, cranking, turning cold or notching it, you can defeat it. The MIG29 luckily has enormous thrust to outrun the missile. In PVE you will get the launch warning, because the AI single target locks you. But if you're in PVP, you will likely not get the launch warning, because the enemy will fire in TWS mode. The missile warning will then appear when the AIM120 goes pitbull (turns on it's own radar) at close range, which is too late. Therefore it's better to develop a "feeling" (or to know) at which ranges the AIM120 can be fired, is dangerous and then to pre-emptively defend the missile even without a RWR warning. I think missions and PVE campaigns like this are really good to practice those things.

Hi, I've tried this mission a few times now. There are many ways to do this. Here's what I've found: -Your wingmen are taxiing too slow so you'll need to start on your own until they are ready -Ideally engage bandits between Gudauta and Sochi, by then your wingmen should be at least taking off -Start as high and fast as possible to increase missile range (if possible you can shoot an R27ET. It has more range than R77, but bandit needs to be in afterburner) -Don't worry about the first AIM120, it can't kill you if you defend properly, (ECM always on, chaff while turning and flares against 9X when you're close) -Engange flight lead with R77 or R27ET and ideally another bandit as well to put them defensive. You can use TWS mode to track them before engaging to increase your situational awareness. Fly towards them in a slight notch and only turn into them when in firing range. Use nnc (High pulse repetition) mode for hot bandits and change your radar settings accordingly to where the bandits are. -Defend AIM120 aggressively, use the mountains to the left to do this. General tutorial is here: -Watch your RWR: If missile doesn't come closer anymore, it is defeated and you can slowly recommit (even if it's still tracking you) -Repeat until merged (some of the F16 will surpass you to get to your buddies, watch for the contrails as they are flying high) -You should kill at least 2 F16 before the merge Good luck! PS: Watch your flight on Tacview to see what's going on and then adapt.

Okay so, I wrote this post, added the pictures and then all of my text got lost and I can't edit any text into my post. So I will just write it again... I was on a multiplayer server yesterday and suddenly everyone at the base exploded. I watched the track replay and found out that after landing I parked in a spot where then someone spawned (pic 1). The collision set off this chain reaction that first we would explode, then all of the neighbours, then their neighbours, etc. Even after respawning (pic 2), planes were still going off and this went on for a while until I and several others got kicked for teamkills (if you explode and your neighbour explodes as well, it's counted as a teamkill). Even after reconnecting, planes were still exploding (pic 3). Meanwhile we captured another base and could spawn over there to stop it. Now, you probably shouldn't park in someones spot. But this isn't ideal either. IRL there are no spawning planes How about a) different damage model or b) not being able to spawn into a parking plane by 1) not being able to select a jet whichs parking spot is blocked or 2) automatically being spawned in a free spot rather than a fixed spot

Until Saturday I could use Shift+M (FC3 user) to silence the AWACS. But when I returned to the game yesterday, AWACS kept spamming no matter what I did. Even if I deactivated the subtitles, I would still get the voice communications. Also, the communications menu was bugged with ATC commands. The didn't switch to the next option even when acknowledged by the ATC (like Request Startup -> Request Taxi -> Request Take off), but would stay at the first option (Request startup or Inbound when landing).