Maverick Su-35S

These are from DCS, right? The real F-18C isn't impressive at constant turn rates when flying at FULL AB above 10 AoA, even when clean. Perhaps you didn't know that ever since it appeared in DCS, the F-18C lot 20 has an exaggerated drag versus AoA function, so it decelerates much faster than in reality at IDLE thrust, and because it couldn't reach 1.8 Mach as Wikipedia wrongly states anyway as it's top seed, I suppose the devs have increased the engines thrust enough to have it reach some Mach 1.82 in ISA conditions at some 36k feet. Not to mention that even at 100% MIL, the beloved DCS F-18C reaches Mach 1.48 in clean config (SUPERCRUISE) like it tries to catch the F-22 and it also suprecruises at some Mach 1.27 with 2x AIM-120s and 2x AIm-9x. Anyone can test this! The real F-18C pilots know that it can reach only reach close to Mach 1 at 100% MIL, as well as maximum Mach 1.7 as top speed in clean config, when flying leveled at high altitude and may reach 1.8 only on a shallow dive for a some while. So, it's drag was and still is too high all around the AoA tables, and in order to compensate, the engines thrust is also over-exaggerated. That's why the F-18 in DCS turns with at least 2..3 degrees per second faster at maximum constant turn rate than it proves IRL for the same conditions and that makes a big difference in simulated dogfights. For instance, during personal tests I've found that it out accelerates and out climbs all other fighter jets in DCS when put into the vertical from the same initial speed and climbing G-load, shortly followed by RAZBAM's M-2000 (another jet with the same exaggerated engine thrust issue). The only fighter jet which has the highest constant turn rate, almost 2 degrees per second above the already high rate of the F-18C, is the JF-17 and it too isn't realistically made in terms of performances, either aerodynamic (lift-drag vs AoA) or engine performance! The F-16 is one of the most accurately performing and aerodynamically simulated fighter jets in DCS so far, only together with a few other jet fighters! So don't you wonder why real US fighter pilots who flew the F-16, F-15 and F-18 know for sure that the F-16 out turns the F-18 and F-15 at constant turns, while the F-15 only slightly out turns the F-18, thus the F-18 being in the thirst place, while in DCS it's on the first place. Something has to be fishy somewhere and I've already given some clues, for who cares about them!

Nope! I don't even have a button assigned for disconnection as I never plan to disconnect before fully refueled and I didn't even set may inputs as I've only started trying the F-4 with some play around in mind, starting with air refueling which has this apparent bug, which all other jets that I do air refuels on don't do! You have the track, you can check it. Like some 6 minutes after starting you can find what I'm talking about. And that didn't happen once by chance, I've intentionally then tried to see if it does it again (like a tester I like to be) and yes, it does it every now and then with no logic. Sometimes you sit there with the most forward green lights on, telling that I'm a bit lower and too forward (so the boom isn't that compressed if I'm also low and not just forward), and all of a sudden it disconnects, sometimes it stays for a while and won't do that. I think that it's triggered by the motion of the plane, cause let's be honest, you can't remain stuck in a position, so as the whole plane wobbles a bit, but still maintaining that general position with those 2 green lights, wammm...it disconnects! Regards.

Some times he says things the opposite way, so, personal choice, I erase Jester! I mean there's nothing more upside down than ignoring the lights and waiting for Jester who is also late in response to tell you what to do=)). Personal choice, I like to fix things, not ignore them!

Hi, Although I truly enjoy this product's quality, especially when it comes to the flight model realism of the aircraft, aerodynamic forces and moments versus AoA and Beta (sideslip angle), as well as engine performances, for which as an AE I can tell that for me HEATBLUR has won the prize for truly the best team in making the aircraft in flight behavior be simulated very correctly and I don't even want to talk about other third parties who never managed even 50% of what HEATBLUR proved. Every correct/fair definition comes relative to something, so I had to say it! Now, for the subject that I'm here with, whenever I do air refuels with the F-4, very often when I'm just one dot below and one dot (green light) ahead of the ideal center position, although I'm not making any abrupt maneuvers or anything, the boom disconnects! In order to catch this suspected bug, I've reconnected plenty of times and re-done the scenario and yes, for a good couple of times when I'm with both green lights from the belly of the tanker ahead of the ideal center position, meaning when I'm one green light towards UP and AFT indications, the boom unlocks for whatever reason and I must go for a re-connection! The track file has 65MBs, so I've shared it on this link: https://drive.google.com/file/d/1cmkhmOfZEDHRm6SmuNKk5DgAZiMFS3jx/view?usp=sharing Kind regards!

Hi, Whenever you use DTOS launching mode for a weapon and designate a point on the ground by using the HUD, then correcting the position on the ground through TGP, then switching back to CCRP launching mode, the steerpoints no longer work and all the SOIs remain stuck in a random plane on the ground which is not any kind of steerpoint. Another bug is that the BRST function now makes the MAVs FOV run haywire, not listening to the slave mode anymore, nor in VIS or PRE, once you press BRST after locking a target on the ground. From that moment on, you can just dump the MAVs as they become useless and probably only after repairing the plane, that would fix the problem (just a guess) or simply respawn the plane. No matter how many times you try locking a target again (if you easily manage to) and pressing the BRST again just hoping to have it work normally again, it won't and remains with the selected MAV's seeker oriented sideways by default. Steerpoints not working anymore when using DTOS and when pressing BRST on MAVs, their seeker goes haywire.trk Regards!

I see you are full of imagination for trying to invent incoherent pretexts, but sorry, it won't work that way! 1. The LG of the Su-25 is more robust than you seem to imagine and for a bit of thinking exercise, if not even the tire doesn't blow up from lateral force, how can the steering system fail that easily? And speaking of thinking, is there any other aircraft for which the steering gets stuck like that from a simple tarmac touch or smallest little non-uniformity in the grass? Show me one cause I'm genuinely curious. Only the Su-25s steering system needs a little attention to be logically at least as resistant as the one on the Su-27 and also the main landing gear needs the same attention to be somewhat more resistant to lateral forces only, as every time I steer the Su-25 on tarmac at some 50-80km/h and it's heavily armed and the wheel from the interior of the turn lifts off the ground a bit and then retouches after I reduce the steering, that landing gear fails. Very non-logically, not the one on which the weight of the whole plane is fails, but fails the one which re-touches the ground=). 2. I can use the rudder with the heels on the ceiling and still won't brake the steering systems or gear on ANY other airplanes, not just FC3, so avoiding the grass only has to do with it's coding..., which can be changed if people are kind. Btw, only the FC3 aircraft remain stuck in the grass. DCS level aircraft never do. I'm curious about your new explanation for that? 3. Wet grass? Mud? Sinks? =))). You are brilliant! Now I just wonder how would your proposed tests would look like! Perhaps you never heard of a Boeing 737 that landed on a grass strip, while it's main tires had quite a very good ground tire pressure (if you know what that is) on a fully rained, soaked mud as you like to bring in and not only that the landing gear withstood the forces without breaking apart nor even bending, but days after that mishap, it also took off from that same strip. Yes, it was relatively lighter, but the soil didn't just dry out that fast and still took off. Not to even mention the plentiful of videos showing soviet fighters taking off from exactly that..., wet mud terrains! And you want to come and explain how FC3 airplanes like F-15 or MIG-29 remain stuck on dry grass at full AB. Instead of accepting the truth and reality, you play the same game like many others I've seen doing so, by trying to invent all sorts of nonsense. You've found the wrong guy;). I simply wish I could help ED correct things in DCS. I wish I could know how to fix the damn thing myself if I'd be allowed to. Me and others who want to correct it, are at the mercy of ED's developers for their time and effort (and I understand them as they are overwhelmed with important bugs) in trying to look into these things as well when they get the chance.

It's funny when you have to restart the engine/s and reorient the plane so that the wind won't keep any of them at 1% non-stop, so you can find an orientation to have them finally reach 0% and be able to repair. some normal 7% or at least minimum 5% shouldn't be a big deal to be more decent.

Ohhh. Many thanks. But how could anyone know when and what they change and you have to relearn everything like from scratch sometimes. Thanks. The guy before you explained it clearly. I didn't guess that at the rearm menu there's a little triangle added at some update which does that. I thought that had other purposes. Cheers

If you didn't understand the bug here, I'll explain to you again. I wasn't talking about resolution! How did you get there? Whenever you use NORM, you can change the scan angle. Whenever you are in EXP, only the 1,3,6 appears when pressing the OSB for changing the angle, but the simulated scan angles remain untouched at 60 degrees. Whenever you are in DBS1/2, now the button for changing angles doesn't change anything anymore, while the angle remains stuck at 60 degrees or at least it remains stuck with the scanning time for a 60 degrees scan angle! Was this good enough? Anyway, you have the track which explains everything about these AG radar bugs.

Yeah..., they really did...! Of course I'm being sarcastic. At some moment they've let you pre-edit the code from within the mission editor at the aircraft additional properties section, just to get a "better" idea with the latest updates to eliminate it from there and put it nowhere to be found anymore. Where is the option to have the laser code set up from the mission editor now or is there a whole new "feature" to do it? Thank you!

Hi! Did anyone talk about the angle coverage (10, 30, 60 degrees) when in any other mode than NORM, such as EXP, DBS1/2? Whenever I change to those modes, the number of scanned degrees remains at a fixed value (dunno which one), although only in EXP when you press the angles button, the numbers change from 1 to 3 to 6, but nothing actually changes about the scan itself. Only the horizontal antenna sweep indicator moves in according to the three scan angles limits, but the visual picture remains stuck on the same angle and the scan rate also remains intact and these things happening to me are totally different from that video from Wags. Track: F-16 AG radar doesn't change scanning angles and scan times in EXP, DBS1&2.trk I may be doing something wrong, yet I don't guess what. I cannot change the scan rate or scan angles in DBS modes. Bug or what? Many thanks!

Hi, Whenever you are at 1% or above for any engine rpm, the ground crew won't ever repair your aircraft, including if the weather plays it's role as well by having the wind blowing fast enough to keep your engines at or above 1% rpm! Can you please correct the code and let them start repairing even when the rpm is as high as 7% ? It is frustrating and can even become annoying to wait for starting a repair on some aircraft which take a lot to have their engines rpm go down to 0% and you probably already know it too! You can be pretty sure that even at 7..8% rpm on the low spool (which gives the highest airflow rate) no jet engine will ever pose the danger of sucking a human. I say this even from my own experiences as working on Boeing 737NGs (which have big engines compared to fighters) for 8 years, when for a good amount of times I had the chance to do some dry engine motoring runs which gets up to some 28-30%rpm on the high spool and some 8% on the low spool and during those runs I would put my hand in front of the inlet to see how much force would pull it when held directly flat/perpendicular to the airflow (90AoA) and to my surprise I would guess it was around less than 3..2lbf which would drag it into the inlet, so..., there is no risk in getting sucked in at all at such low rpm. So, can you please re-code the aircraft repair to start repairing whenever you are below at least 7% or 5% rpm? The amount of time (3 mins) of repairing isn't realistic at all anyway, as well as the rearming, so at least make the low limit engines rpm a little higher for starting repairs! Many thanks!

Hi, Just happened to come across this video and after seeing how the plane was slammed onto the ground at that visible rate. From experience in DCS, the landing gear on our lighter Su-27 bends quite much for this kind visually memorized vertical rate. I totally agree that I could be wrong, but I'll do some tests as soon as I get the time to see how things compare. This is all for the good of DCS, not for the bad of it. Regards.

Hi, Only after the latest updates which include a an otherwise very useful setting of controlling the AB detents as a % of throttles position, I've noticed that if you put an AB detent % summed with the deadzone % which would give a result of over 100, the engines will forever remain in FULL AB while the exhaust nozzles will correctly listen to the IAS-MACH-THROTTLE function and can go fully closed with the afterburners blasting at max gas flow rate, definitely proving an engine model fault, only due to this reaction of the nozzles which don't listen to engine regimes conditions, but only to throttle inputs and IAS/MACH function, not caring if the afterburners are in full demand! To cut any useless replies from the start, you never possibly can have a full afterburner condition with the nozzle fully closed without having the engine either get into a violent surge or eventually blowing off altogether. Regards. F-14 FULL afterburners continuously ON with nozzles fully closed.trk

Nobody simulated that, take that out of your mind!