Py

I would think it's just due to the higher air density at lower altitude (more drag). Density is a simple function of temperature and altitude, it can easily be calculated directly. The motor only burns for a few seconds, after that it's all drag slowing the missile down, which is much higher in denser air. Nothing specific to the AIM-120 either, it's the same effect for all missiles.

It may have been fixed, I used to get this problem quite often but it hasn't happened at all for several months. You can't prove a negative though...

To see the scoreboard in game, press '

No that is incorrect, it should attempt to lock 1sec after slewing ceases. You can make it attempt to lock before the 1sec delay by pressing TDC down. The issue is that for some people it doesn't seem to do anything after a delay (it works for me).

The bug thread was closed because they haven't implemented the dynamic launch zone feature yet. The JSOW has only just been added to DCS, we have to be a bit patient to get all the features.

For now I think the only solution is either a close range release, or try to loft them slightly. Later on we will get the functionality to set an impact angle and/or direction which is the better solution.

After entering all coordinates, cycle through all stations selecting PP1 for each. Then launch the first 4 just by using weapon release 4 times, it will cycle through each station automatically (and all will be on PP1 since you set that first). After firing 4, you will be back on the first station again (usually 8) with PP1 selected. So for the second 4, you will need to select PP2 before each release.

The setting for PP1/PP2 is remembered for each station, so: 1. When entering coordinates for the second group of 4, did you select PP2 EACH TIME you stepped to a new station? 2. Then before launching, did you cycle through each station and set them all back to PP1? 3. When launching the second group, did you select PP2 before EACH pickle? It's kind of fiddly. I would guess your problem is one of those.

They also work best when dropped from a high altitude, what altitude were you dropping from? I would suggest at least 10,000ft, but up to about 20,000ft is better. That gets the bomb on a nice steep angle for better accuracy.

Actually this does work, I have had the same problem before. It must be a bug in the radar system modelling that gets reset when you change modes. I haven't been able to find a repeatable way to cause the bug to appear though.

How about making missions regularly (eg once a week), let a few build up in a stockpile, then start playing from the oldest first? Then you won't remember so clearly what is going to happen. I believe there are also ways to build some randomness into missions, if you use that in combination with making several missions, it should keep things interesting for a while. Hopefully the dynamic campaign will be out in not too long, but I doubt it will be this year.

I think DCS should have the default zoom set the same as the zero point on axes, but since they don't here is what I do: 1. Reset your zoom 2. Align the edge of your screen with some reference point by moving your head, eg the edge of the cockpit rail or some marking, then freeze your trackIR 3. Move your zoom slider then back to the neutral position, and note where the edge of your screen is in relation to your reference point 4. Go into the axis tune panel for your zoom and adjust the curve slightly (+ or -) 5. Check if your reference point got closer or further from the edge of your screen, adjust the curve in the opposite direction if it got worse 6. Fine tune the axis curve until your reference point lines up with the edge of your screen 7. Unpause trackIR and you're done

Well it's just my opinion, but I'd say #*%$ NO! I (and many people) have paid a lot of money for modules, if suddenly we can't use them without paying continuously there will be riots... A subscription model would also dissuade new players from trying it the way they can now.

What time zone?

I don't think you can. It appears that DCS doesn't actually simulate IR seekers locking onto contrast, it's more like "seeker is pointing at a unit, allow a lock". So you can only lock things that DCS counts as a valid unit (which includes lampposts for some reason...). You can do it with the maverick variants that have the "force correlate" function (-G? -H?), but the F/A-18C doesn't carry them.

All it needs is a DCS fan winning the lottery :)

That would be a really nice feature, especially with both a left and right kneeboard for quick reference to two different pages.

Seriously, you think this thread is being toxic?? Because some people have politely said something you disagree with? You are free to politely disagree with them too, it's a discussion. I think everyone is happy to have more of the less popular modules such as trainers in DCS if they are done by 3rd party developers. It's just that ED themselves already have the DCS engine and multiple unfinished early access modules to work on, so people are worried about new projects causing delays with these. Prioritising popular modules is not "hating" anything, companies just need to make a profit before they can work on modules that will have fewer sales. Hopefully they will eventually have a wider variety of aircraft so everyone has their favourite planes :) Yeah that would be an example of a toxic attitude...

I don't think people have been antagonistic or dismissive, they have just said that they don't feel that there is a strong need in DCS. Not like "some of us do actually partake in some level of socializing online". Anyway, screen sharing via twitch etc seems like a really good way to train to me, do you disagree? The instructor can see exactly what the student sees, not just a limited subset of instruments and controls. But do what you prefer, I'm merely making a suggestion. As for "Besides the more the merrier. IF you don't like trainers, no ones forcing you to buy them.", I agree perfectly with you and I don't see anyone else disagreeing. More planes is more fun! Pointing out that ED is more likely to make combat planes than trainers doesn't mean I don't want you to have fun, it's just pointing out a sad fact of commercial software development. If they do make more trainers then great, I hope you have a lot of fun with them.

That's due to real-life requirements of the instructor being able to teach (observe, give feedback, assist if necessary). In DCS, do we need any of that? We can try anything we want with no consequences, aircraft price doesn't matter, and we can get assistance from people by sharing our screen over twitch or similar. Even better for an instructor than sitting in the back. Sure some people may be interested in flying simple trainers, but I expect most people would prefer to just fly the "target" plane eg F-14/FA-18 and learn on that. With unlimited resources at ED then sure, why not, but for them it doesn't make business sense to develop modules that will likely have low sales.

The CCIP cross should move when the mode is switched between FF/RET, but it doesn't. Very clear track attached, it's easy to see that the cross doesn't move at all when the mode is changed. snakeye_ccip.trk

Nice work! I assume that is just a placeholder drag model until later in beta, but it's useful to see how things work at the moment. Did you try any comparison with other weapons, eg amraam vs maverick? Or rocket pods? That would be interesting to see!

It doesn't make sense that if you go into ACM mode while in SIL, eg in an emergency, the only way to get the radar active is to get out of ACM mode, press SIL, then go into ACM mode again. The fact that there is no SIL button even available in ACM mode pretty strongly implies that the radar should exit SIL mode automatically if ACM is selected.

This has been a problem for a while. The solution is to turn the radar altimeter dial down to zero then back up again.

That is...excessive :) It would take forever to release 9 MK-83s if you return to 40000 ft each time. My technique, which seems to work well, is as follows: 1. Ingress/reattack at ~350 kn at 8000-10000 ft 2. Dive at 15-30 degrees, set throttle based on speed and height eg if already above 400 kn, throttle idle if around 300-350 kn, throttle 50% if <300 kn, throttle mil power 3. Release at 2000-4000 ft, when the pipper is over the target will depend on angle and speed 4. Pull up to approx +30 degrees and throttle to mil power 5. Trade speed for altitude, you should end up ready to return to step 1 and turn around to reattack by the time you are at 8000-10000 ft again