earnil

This issue is related to both MP and SP. Regardless of whether there are already any existing steerpoints or not, you can't add new steerpoints through DED. It will allow you to enter the coordinates for new steerpoint but it doesn't show new steerpoint on any display (HSI, HSD, HUD) Attached picture is from SP mission, steerpoint 1 has been added in mission editor, steerpoint 2 was added using DED.

Excellent that, along with running VA PRIOR to the DCS fixed it. Thanks again, it was driving me crazy:)

Hey guys, sorry if this is not an appropriate place to ask this question - if that's the case I'd really appreciate if you could direct me to right place. So I have a Voiceattack with VIACOM plugin and when Voiceattack is running it keeps popping on and off the Comms menu, every 5 seconds approximately. I tried multiple things to deal with it, like deleting the keybind for Comms '\', deleting and having VA recreating lua file in Saved Games\DCS\Scripts\VAICOMPRO\VAICOMPRO.export.lua It does this presumably for all the planes (tried F18, F14). I have discovered older thread dealing with somewhat similar issue here but no solution proposed in there works for me. Does anyone know how to solve this? Thanks in advance!

Same here - CTDs even when using the optional campaign file. For me the crash occurs almost always very after I splash first bandit whatever it is. And this was true for the anti-heli missions as well as the later ones.

I did not see it mentioned anywhere so another small tip would be - use rudder for small lateral adjustments when connecting with the basket instead of bank. Also, make your adjustments while moving forward. Lot of people have a tendency to get the basket into perfect position and then try to move forward to connect, but that's wrong (the movement forward = increased speed = you're out of trim = you must control pitch = your vertical control is harder) Counter-intuitively, but as shown in Maverick's video, you should be approaching the basket at constant forward speed. Accelerating and decelerating will cause your plane to pitch up/down. If you move at slow speed forward, you will stay trimmed making your vertical control much more easier. Try to push through the basket too, don't aim to 'stop' where the basket is.

Also, the IFF result is not shown on radar page but on SA page. So, set your MFCD (the middle display) to SA and there you see the result of IFF interrogation. Sent from my iPhone using Tapatalk

Because you're focusing on speeds. Forget about speeds, only thing you need to care about when you lower the gear and flaps is AoA. The fact that you deploy your flaps. Flaps change the shape of your wing and therefore relation between your airspeed, pitch angle and AoA. With flaps on AUTO, your AoA for level flight at 250kts will be about 4 units (depending on your weight). With flaps full down, your AoA for level flight at 250kts would be close to 0. FCS, when you deploy your gear and flaps aims to maintain constant AoA, which is 4 units. But your effective AoA now is 0 so the FCS will command pitch up movements to increase back to 4 units. That's your buck-up. Because when you use your trim with gear and flaps down you're not controlling directly pitch attitude (actually, you don't even with flaps on AUTO) but rather commanded AoA. What you effectively tell the FCS when you trim up is not "pitch up" but "more AoA". But what you're doing with your stick is pitching down which decreases your AoA (that's why it seems that it doesn't work). What you need to do is to wait for your airspeed to deteriorate further. As you fly slower, your required AoA for that particular attitude will increase and at some point it will match up with what you trimmed for.

That really depends on what you want to do. Do you want to fly mostly SP missions, or do you want to try multiplayer against other people? Do you want to do A2A or A2G mostly? Do you just want to have fun or do you want to learn the plane more thoroughly? Anyway, Matt Wagner from ED has quite extensive series on Hornet:

Since it's called KobyashiMaru, I couldn't resist just to try it. It's doable, but haaaaard. Couple of things: - your original loadout was bit too excessive on 120s. F18 handles like a brick if you put anything at all on those wing pylons. Take 2x 120 and 2x 9x, that's enough - and you can actually turn. - In the end I had to change CM loadout to 5 flares for terminal engagement and 115 chaff. With standard 60 / 30, ... I don't think it's possible to beat it. Tactics is pretty simple - stay in the notch, let them come to you and when they are close, about 10nm, after you beat that last 54, turn in and shoot them. You need to save your chaff for the close ranges so try to defeat the first two salvos with maneuver and once under 20nm always keep chaffing and notching until you see the missile pass, they tend to relock after you leave the notch or stop chaffing. Not sure what the AI does in 2v2 though and honestly I don't have that much experience in it, but you can try to split them and play it as 2 separate engagements and if they follow just one of you, the other one can flank them and shoot them. Tacview attached. Uf, good challenge though. Tacview-DCS-KobyashiMaru.zip

Hello everyone! I've been playing with different loadouts on Hornet and noticed that maximum speeds you can reach, are, for some of them, rather strange. Two results that stand out for me are that max speed with 6x 120B is barely M1.0 whereas with 8xGBU12 and fuel tank it's M1.5 at same altitude. On top of that, carrying only 4x 120B seems to increase max Mach to 1.5. I'm attaching a picture with test results with different loadouts as well as the track for the 8xGBU test (all other tests were exactly same conditions). Other details: - Altitude: 40900ft MSL - unlimited fuel - immediately after start, BALT autopilot engaged, full AB - AIM120B are always single rack Apologies if this is not bug. If not, I'd be really grateful for explanation why these speeds indeed make sense. Thanks! FA18 - 8GBU Speed test.trk

You need to keep notching the missile. 54C has a lot more energy then any other missile we're used to, so, if you exit the notch too early, it will reacquire you and still has enough energy to get you. Get to notch, pop chaff, and stay there until you're sure missile has passed you. Use this to close the distance to some 7nm and as soon as you defeat last missile at this range, turn in, use ACM to lock him and shoot. No point trading shots at long distances, he'll most probably defeat them anyway. Shooting from shorter ranges has many advantages - you can acquire him with ACM modes rather then looking for him, your missile goes active immediately so you can defend right away if he get's off another shot and it's much harder to defeat at this range. Also, some people make a mistake of trying to notch the Tomcat's radar, you need to notch the missile's radar.

Re-lock is already implemented. If you lose lock, then reacquire it and the illuminated target is still within missile's gimbal limits, it will start to track it again.

There's definitely an issue with Mav G warmup. Normally, what works for me is to go to A/G mode, with master arm on, select the Mav G and then go back to Nav. In most cases the warmup runs normally. But there are instances where it doesn't work. From my observation it's not only if you select AIM 9, but also if you select any other weapon, like GBU. It seems that the warmup process is canceled. I usually manage to get it going again by selecting NAV, then AG again and selecting MAV. Then it takes 3 minutes as per usual.

Yes, we can! I have TDC axis bound to TDC on warthog throttle and it works like a charm. The PCA logic is kind of buggy still so make sure that you have A/A weapon selected when trying to lock on target. For example, if you drop a drop tank, PCA keeps it selected even though the yellow light is not lit anymore which prevents you from locking any targets I don't remember the Mission 4 exactly, but the target also may be jamming - check if you have 'BR' in top left corner - then you can't lock the target until your radar burns through

Just to clarify, the computer should recognize opposite runway or even different runway on the airport (if the reference code was used) automatically so no need to change numbers in BANA. NAV SYST pops up if the heading during takeoff doesn't match the expected one or if the initial alignment couldn't happen (for example if you're taking off with B1 already selected - you need to have LS selected for alignment to happen) or maybe (I'm not sure about this one) if you switch to NAV mode too early (you really should just before the takeoff). Overall there should be no need to use the reference button or change the BANA / GRANS setting if you're taking from known airbase. I think TERNAV beats the visual/RADAR fix, so if you have stat 5 with 0 error and you press RENSA, the fixes get deleted but you won't see any change because your navigation is already fully up to date due to TERNAV. The TILS transmiter is always of the side. It will lead you in but you need to fly last meters visually, it doesn't guide you all the way down.

Sorry, I just realized that I misunderstood the part about different antennas. Yes, indeed, that can be the case, not just directly opposite. Sent from my iPhone using Tapatalk

Yes, I know, things can get chaotic, but this is almost certainly from single source (the lock starts and ends at exactly the same moment for multiple contacts) Also, another piece of the puzzle is that people call buddyspike on me even though my radar is 100% in search mode - not locking anything. There’s definitely something going on that’s worth investigating. Sent from my iPhone using Tapatalk

I think I’m experiencing same thing. It’s usually when there’s another RWR contact directly opposite to the one locking you. So for example, if there’s an enemy on your 3 o’clock and friendly on 9 o’clock and the enemy locks you, RWR will show both the enemy AND friendly locking you. I’ll be back home on Monday so I’ll try to produce a track but it’s indeed kind of hard to pinpoint. Sent from my iPhone using Tapatalk

Great, thanks a lot for detailed information everyone (this is why I love DCS community!). So, if I understand it correctly then. I reality PID mode in fact does SAM, meaning that it just doesn't sweep the sky but also periodically 'pings' the bugged target to get more accurate info. But, because of how the RWR is modeled in DCS, it will only differentiate between scanned / tracked / missile guidance states and any form of TWS/SAM is shown as simple scan. Is that fair statement?

That's perfect. And is it steerable or just forward facing? For example, if the radar emissions are coming from 5 o'clock, will the pod jam it?

Hey guys! As the title says - I was actually wondering how this is modeled exactly. I'd assume that if I lock the enemy plane in TWS (first 'lock') his RWR would not give any warning but would simply show radar in search mode. At least this is my understanding of how TWS works (radar is actually still in search mode, it just keeps local track file of the know targets and matches them / calculates the additional info) But is that really so? Unfortunately I have no way how to test it myself so was hoping that more knowledgeable people here can explain if I'm missing something.

This, plus, AI plane always 'knows' where you are whereas keeping the enemy in sight is I think one of the hardest things in dogfight for real player. I lost too many of them because I simply lost sight of the enemy and he didn't.

A question - in manual it says that the pod is not omnidirectional, but rather emits in a cone. Is this modeled? And if that's the case, is the cone itself steerable or fixed (i.e. can the pod jam only directly forward or also off boresight?) Or is it just ECM ON => reduce lock range and that's it?

Unfortunately no.

Thanks man, you're my hero now. This was driving me crazy!