RyanR

The A-10 is a lot more complicated with nav points... because it's an attack plane first. The F-16 is a lot simpler if you remember a few rules: All sensors in the F-16 look at the same place. "SP" is "snowplow".... a fixed distance ahead of the plane. Otherwise, sensors look at a steerpoint/markpoint. I never use snowplow. The F-16 gets confusing when it comes to "CZ".... but it makes sense if you think of the F-16 being a "pre-GPS" fighter needing a way to update the INS. When you slew the sensors, all the steerpoints move. This is sort of baggage from those INS days where you'd use the sensors to get an INS fix to update all of the steerpoints. CZ simply zeroes everything out to erase the offset you put in slewing the sensors. In practice: Use CZ often. In addition to the TGP and FCR, the HAD/HTS and dive-toss bombing can introduce offsets. Once you find a ground target to blow up, make it a markpoint. Markpoints are saved as steerpoints #26-30. You only get 5 markpoints before they start overwriting themselves. Use CZ often. -Ryan

You can't really win. A smaller high res monitor wasn't helping me. A bigger monitor at the same res fixed that. I did learn that forcing DLSS with a 3080 wasn't the right thing to do. Now I have a 5080. Much better. As with all things with DCS, just throw money at the problem. -Ryan

Even for offline play, it'd be nice to have more control. It helps train your eyes where to expect to find a bandit during some BFM. -Ryan

Are spotting dots going to get "better" or more customizable at the user end? I have dots set to 2px, and at 1440px on a 27" monitor with a 3080, things are still a bit hopeless using DLAA or DLSS. If I use MSAA, it gets better, but it's still hit or miss. Often, I can see a dot for the lead bandit, but can't for his wing man. Yet, if I set the resolution down to 1080px, I can suddenly see dots at 40 miles. That seems to be in line with the wisdom on the internet: To see best, turn off all of the things that make DCS visually stunning. I have a new rig with a bigger (but same resolution) monitor coming, and I hope that fixes things. I don't mind taking a heater from a MiG-19. That's how you learn. But a MiG-19 with a cloaking device isn't really fun. Thanks! -Ryan

I noticed that you can interact with the "wrong" IFF panel! Bizzarre. For multiplayer, you basically need to uncheck all of the "simple-logic" options: Landing gear, IFF, Unfolding the triggers, etc. I can't throw any stones at Aerges, they generally do great with the F-1. It's still a ridiculously good module. -Ryan

Just about to complain about this. I've wasted hours with the F-1 since this patch. People who run MP servers aren't going to figure this out. That means the F-1 is going to be messed up for the people that own the module. -Ryan

Seems every user option is screwed up in the multiplayer. This roll-out was poorly thought out. In situations with Dynamic Spawns, the F-1 is all kinds of messed up. -Ryan

Plot thickens a bit... if I un-select the "Mode 4 IFF installed" in the special options for the F-1, the IFF panel in the EE is now clickable in multiplayer. The problem is this from the changelog: "Some options, such as: 'Simplified Gear Lever', 'Simplified Firing Safety', 'Mode 4 IFF installed', 'Delayed Oil warning light', 'Counters reset on rearm/refuel', are always read from the mission now. These options will be always in sync between seats in F1BE." I'm wondering if the problem is confusion between the client settings and the the server-side MIZ file. If I were Aerges, I'd just let the client settings rule the day. Most server folks aren't going to get all of the F-1 options correct. -Ryan

Yeah.... problem seems to be MP vs. offline. Offline OK. MP not OK. Affects both the -EE and -CE. Two different looking IFF panels. -Ryan

Same here! Even if I map the IFF functions, there's no animation. -Ryan

The only problem with the waypoint tool is that you can't change it without re-planing. Soooo.... it's kinda limited. For the time being, I'm still using the DCS DTC app/mod. for the F-16.... just to set up steerpoints, comms, and now CMDS. I think the "official" DTC has tons of potential, but for MP servers, it's still pretty clunky. -Ryan

Holy schmoly.... what's going on? -Ryan

The F-1 really likes to slip around on the runway when landing, especially in a crosswind. It feels like the wheels aren't "gripping" the runway. Is there a trick to keeping the plane going straight after the nosewheel touches down? I seem to find myself chasing yawing oscillations. Should I turn the nosewheel steering completely off via the guarded switch? For the most part I'm OK if I pop the chute the second the nose wheel comes touches down and use differential brakes instead of rudder input until the plane comes down. Just curious if I;m missing something. Aside from the F-16, the F-1E is my favorite DCS module by a long shot. The Phantom is like driving a big, gloomy school bus by comparison! Thanks! -Ryan

I was doing this in DCS last night. I dunno why I love the F-1 so much.

Since there's no canopy frame to reference, one thing I have found that helps when refueling the F-16 is to toggle head tracking off. Edge of your screen gives you some more reference to fore-aft position. With VR, you've at least got depth of field and natural head movements. Additionally, when forming up on the tanker, you can use your radar to get the tanker's speed in CAS. The F-16 does not have IAS, and 300knts IAS isn't 300 CAS. -Ryan

I thought this was fixed? Slick Mk-82/84 are falling short in CCIP. Drop in CCRP, and they're almost spot on. Is it just me? I know, I know.... no track file. -Ryan

RWS is noisier, but definitely get you a target on the scope before TWS does. If you have datalink, you know what to look for. -Ryan

Wow. This is really bad. The plane also feels very sluggish suddenly around the roll axis with gear up and at speed. Almost like CAT III gains in CAT I config. -Ryan

With a good plan, the F-16 is the winner for SEAD/DEAD. The F-18 guys are always jealous of our toys. MFD setup makes this all quite easy. Honestly, any SAM that a HARM can target should already be on the list of things to deal with. Setting up the HARM's to fire in POS mode becomes handy. -Ryan

Where's tech support for this? I put an image in "bug reports". -Ryan

This drove me crazy trying to figure it out. "Glad" I'm not alone. -Ryan

I know we've no support at this point, but has anyone noticed that "PCM" is in the upper left of radar display since the latest patch? I'm 90% sure that it wasn't there before... and there's nothing I can do to make it go away. It overlaps with "TAF" when you're have GCI going. Hmmm? Thanks! -Ryan

Thanks! This makes sense. I could have sworn I was in a track mode.... maybe not. I'll keep an eye on it. -Ryan

This seems to be new: I have the FCR in GM mode. Select a target (that I put there). I went to make a mark point. DED shows HUD instead of FCR, and the radar kicks out of GM mode and into AGM mode, which undoes all the work of finding the target. Nothing is in CCIP, so I'm confused. In the past, choosing to make a markpoint with the FCR as SOI, automatically chose the FCR.... not the HUD. FCR stayed in GM mode, and a TMS up made the MKPT. Track is attached. Thanks! -Ryan MKPT to AGM.trk

As long as you're in the envelope with a PGM2, you can fire a HARM over your shoulder. The system is *designed* to work this way in EOM. When you really need to wail on something, get a steerpoint on it and fire in POS/PB mode. -Ryan