Py

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

Aim for 450-500 knots at the drop.

Do they have different effects in game?

No not yet

This would be very useful

We're going to need more information to help you, that's why a (short) track is useful. When you exit the mission in single player, it goes to the screen showing all the events that happened. There are buttons on the bottom, left is EXIT, right is FLY AGAIN, middle there is SAVE TRACK and PLAY TRACK (or something similar). Are you using the realistic mode for mavericks where the TDC button must be depressed to move the cursor? Or the new modified mode? In the "unrealistic" mode you need to slew to the target then press the TDC button, it is supposed to lock just when you stop slewing but it is bugged at the moment. You won't be able to lock things when they are far enough away that they are a tiny dot, they need to be close enough to have some size. What mode were you using for HARMS? SP or TOO? Were they missing because they fell short? There is no range information in SP or TOO modes so you need to make sure you are high and fast enough for the missile to be in range when you fire, but it won't tell you if you re in range or not. The higher and faster you are, the further the range is. It might take some experimentation to get a feel for how far you can launch from. Hope that helps.

It may be that after rearming each maverick is only beginning the cooldown (not warmup) when selected individually, instead of when any is selected. I typically cycle through all the mavericks after takeoff to set narrow FOV for each, and later when I fire them I don't need to wait 3min between each one. The countdown timer doesn't seem to be correct though and sometimes is not shown at all.

Watch Wags' video again carefully and it makes sense what you are seeing. To do manual IFF you need to put the cursor over them on the radar page and press sensor select depress, which you might not have bound yet so check it. The small diamonds mean hostile from a surveillance sensor and no information from your own sensors. So when you are tracking one target with STT in pic 2, your radar can't see the other 3 targets so they are shown from SURV data only. When not on your radar in pic 3 they are all from SURV data only.

Almost all missiles use a solid rocket motor, once you light it it will burn for a certain time then it's done. The missiles can't turn it on and off, they must rely on the energy from the initial burst of thrust.

I've had this issue too, but on the previous version of open beta (before retarded bombs became dud at low level). Initially I thought it was from wind (was set to 20kt), but the bombs miss completely when you use the CCIP cross when it has this skewed drop line. And light wind should have almost no effect when dropping at 500 knots from 500 ft.

Sure post a track or video. It sounds like you need to forget the landing part to start with and practice flying on-speed, using throttle to control the velocity vector NOT the stick. Once you have that down, landing is just the same except you place the velocity vector on the runway once you are at a reasonable glide slope. Don't try to trim until the flaps are down. I put gear and flaps down at the same time during the break then hold trim for ~3 seconds to get in the ballpark, fine tune when level to be centred in the E bracket. If you go straight in, put gear down at 250kt but wait a while for flaps. Maybe 180ish, then you won't get as much pitch up. Use brake if you need to speed up the deceleration, it will go down automatically when you put the flaps down.

Did you uncage it?