jaylw314

To clarify, you need to HOLD the NWS button on the stick to get high gain steering

FWIW, if you have the WW Orion 2 throttle, you should have removable detents, since it doesn't make much sense for the A-10C. While not a game stopper, it makes formation flying annoying sometimes. A word of warning, the screw and nut that hold the detent in place REALLY want to fall into the slots in the base under the throttle arms. Almost impossible to get out unless you flip the throttle base upside down, and I think they're stainless steel so a magnetic pickup doesn't work well. You also need three hands to hold the nut in place while reinstalling the detent. Quick tip is to superglue the nut to the detent to make it MUCH easier to reinstall. Alternatively, you could reduce the X saturation so that full power comes at the afterburner detent, if you're okay with losing the throttle throw above it.

Cockpit flow is cool, even if non-official. I think it's one of those things NASA has been doing research on as an alternative to written checklists in civilian aviation, and given that you don't have a regulatory agency breathing down your neck in DCS, it makes total sense for most sim pilots

Could you just bind it to a ButtonX_OFF so that the Canopy Close command stays on?

My wild speculation is that some of the signal lights themselves might be powered by some of the buses in a way that an interconnect failure would show up with the main gens but not the APU gen, but after trying to figure that out my head exploded so I just left it alone

You posted multiple times, your browser is probably slow In the F-15E you have a bunch of options: You can use these as alternatives to the slider setting. If you set the IDLE and OFF bindings to buttons, it will prevent the slider from controlling the engine state, AFAIK. Note that depending on the joystick, you can set IDLE to buttonX and OFF to buttonX_OFF or vice versa

There isn't anything to learn. ILS are not used for guidance to the airport area since they are so narrow. You would either use a procedure that calls out nav beacons (like TACAN Or VOR) or GPS waypoints, or you'd be getting vectors from a radar controller onto the final approach path. FWIW, a typical ILS procedure at uncontrolled airports (which pretty much applies to DCS) is to fly to the airport (using some type of guidance), fly outbound on the ILS course, pick up the ILS guidance while outbound, and after 6-10 miles make a 45 deg procedure turn back onto the final approach course, aiming to establish around 2500' above the airport elevation until you hit the glideslope from below

The target designation is for the purpose of the pilot's guidance symbology (among other things)--the navigation cues and the AUTO cues. Where the TPOD and laser are pointing can be completely independent. If you designate a point A with the TPOD, and then slew it to point B and engage ATRK, the AUTO cues will guide you to A, even though the laser is pointing at B. Likewise, if you designate point A and then engage PTRK on a moving vehicle, the AUTO cues will guide you to A, even though the TPOD has followed the vehicle elsewhere. the CDES button is supposed to automatically designate after slewing, but it's bugged and doesn't work for PTRK right now In practice, this means for LGB's, you should probably have the target designation pretty close to your actual target, but it doesn't have to be perfect since it's going to guide on the laser. You just don't want it hundreds of meters away. For dumb bombs, the TPOD doesn't matter at all, just the target designation.

Arrrgh. You burst my bubble

It is in the install folder, not the Saved Games folder, DCS World OpenBeta\Mods\aircraft\F-15E\Doc, and the most recent version is there.

Nice! TIL that CPU is simply AOA + 10! I always thought it was some arbitrary and fancy conversion

It's also in your DCS\Mods\aircraft\F-15SE\Docs (I think) folder. Probably better since I'm not sure whether the one on the website is kept up to date

In Chapter 2 of the User Manual

If so, it's new. Before, the pitot would ice up after 40 minutes of flight with the pitot heat off, regardless of what weather you were in. Obviously, not the sort of thing I'm interested in testing out, but if icing happens in some clouds, that would be an interesting change.

LOL, your response made me think of that movie line: "What are the chance of a guy like me and a girl like you ending up together? ... One out of a hundred?" "I'd say more like one in a million" "So you're telling me there's a chance!"

I recall hearing on the RAZBAM discord that avoidance points only show up on the SID and not the TSD, so they are moot right now.

LOL, nice catch!

Don't forget the different canopies between the Charlie and Strike Eagle, too

I know people have talked about stores and the danger of the laser reflections, and I've not seen publicly available data on the litening pod. OTOH, the limitation for the laser is exactly the same as the limitation of the video tracking functions, so I suspect it's just a hard-coded DCS thing.

LOL, you took the red pill, didn't you?

IIRC, the waypoints over 50 are pre-programmed system waypoints from the navigation database, like airports, georefs and such, and weren't meant to be edited by the pilot

I believe they correspond to the SLEW parameter on the MAV and STAT->Throttle pages, if so that would mean higher values reduce axis saturation (less sensitive). I have not tested this out though.

What is this new layer in the control settings? null

It had been much worse, but I'm not seeing this anywhere near as much as it was 6-8 months ago, even in VR (where it had seemed to be the worse than flat screen). FWIW the incomplete IR textures on a lot of ground units (which was basically an IR cloaking device) has been gradually fixed, at this point I can't recall the last time I saw this (I'm sure there are still some on some rarely used support vehicles)

Both are known and have been reported previously: The TPOD Designate function is known to mess up tracking, if you bump the TDC it will track again.