RyanR

It's odd. I think this was happening before the ATP was released. You don't really notice this when using standoff weapons. Usually I notice this when coming into a landing pattern. Steerpoint for the airfield is still right in the middle of a runway. TGP looks right at the steerpoint, but HUD/HMCS can be off like 100 yards. -Ryan

Could this be why CCIP also seems "off"? Perhaps the HUD/HMCS is just "askew"? -Ryan

Interesting that you mention this. I have noticed this as well. HUD/HMCS symbology is offset from the TGP. That the TGP is spot on where it should be, this problem seems independent from INS. -Ryan

You may need to adjust your stick itself (if you can). The "pulse" coming out of the hardware may be longer than you think. The F-16 trim works really well for me with a VKB Gladiator. -Ryan

Thanks for checking! When I did a quick track, it wouldn't happen, so I tried a cold start. Things worked fine until they didn't. I don't know what triggered it. If you're not seeing it, that makes me wonder if it's a "system setting" on my end, or some sort of "cache" is getting full. Good to know I'm not alone! A track would be a big help. Thanks! Thanks guys! -Ryan

Is this really "correct as is"? Was the track watched? -Ryan

Here's a track. I got the problem to happen at the end. I described it a bit incorrectly above. It's like a "partial FOV zoom". Slew the pod, and it does a "full FOV zoom". If that makes sense. I circled the MFD with the mouse cursor when it happens. Could well be something I'm doing incorrectly. -Ryan ATP_FOV_issue.trk

No worries! I almost wrong "zoom"! -Ryan

XR has two FOV's in IR. Thx NineLine. Will do. -Ryan

This happens on occasion: ATP in XR mode. Track mode enabled in IR. When I hit the FOV button on HOTAS, sometimes the FOV does not change until I slew the the pod a smidge. Then it snaps into the correct FOV. In other words: -Pod is in XR mode area track, IR narrow FOV. -Press FOV button to get wide FOV -FOV does not change. -Slew the cursor -FOV pops into wide. My expectation is that the FOV should just change without the slew. Has anyone else experienced this? If not, I'll get a track. -Ryan

We usually circle back to the base and boresight on something at the airfield. On your way outbound, try to find something with the TGP. At 20-25 miles out, reverse and start trying to get the MAV's locked on to boresight as soon as the seeker will "grab" it. In the past, getting one missile per wing (so, two total) boresighted was all that it took to set up all 6 missiles. I haven't had a ton of experience with Mavericks since the latest patch fixed the issues that popped up with the ATP release. I still haven't had much luck with auto handoff, but I always use the TGP and a markpoint to get situated. -Ryan

Ground boresight is at least part of your problem. For months, I did exactly as you are: place a ground target and boresight before takeoff. When I started bore-sighting from altitude at 10 miles off, I was blown away by how the Maverick seeker looked almost exactly on target. Night and day. Another problem with auto-handoff is making sure the Maverick seeker is "zoomed" to the narrow FOV, with good contrast. That'll make it much easier for the Maverick to grab the centroid of the target. -Ryan

Other thought: the autopilot stays on with moderate stick input. Lots of new Viper people (myself included) instinctively start trimming when they're actually fighting the AP. Other than that, the F-16 just needs roll compensation for asymmetric load. -Ryan

One age old DCS question: Does the P5 beat the JULI? (We have the P5 for the F-1?.... I can't remember). -Ryan

Problem here is that the F-16 Litening pod isn't real. It was a placeholder. No actual pod can "see" that well, and ED says it's a mish-mash of technologies. On the other hand, the ATP is an attempt at reality. In other words, reality *is* the use case for the ATP. -Ryan

or! For the F4-U it's a total flip of the coin as to what way a switch/dial will flip. The F-16 is pretty good. -Ryan

Great idea! I did just this. I guess the question is if the "cage" button does the same thing for all Sidewinders. With the 9J, the seeker is uncaged only once you get a tone and only while the button is pressed. Release the button when the target is off bore, and you lose tone. This is just like the F-5.... which makes sense, since it's the same missile. Magic II seems to look at what the radar grabs. -Ryan

Cage and uncage has confused me for some time, as the manual and Chuck's guide don't go into it. What is the order of operations with the F-1. With the F-1, do you get tone and then uncage (as with the F-5)?.... or uncage first? Do different IR missiles work differently? Magic II seems to find things "automatically". -Ryan

Periodically it does say 20nm. Should be just 10nm.... or so I thought! -Ryan

The ATP does seem heavier (takes more to trim out the roll) and "draggier" than the old pod. The old pod is fantasy, though. -Ryan

There's a lot of neat features in the Hornet. Plus, you get carrier ops. And the Hornet can cheerfully fly much higher than the Viper with a loadout. As you say, they're both amazing modules. What you choose as your "favorite" really comes down to what fascinates you more. -Ryan

I take it back. Things are still hopeless. At best, other aircraft are translucent. -Ryan

I noticed this myself a while back! It helps a bunch! Put the flight path marker on the horizon once you get your "height" squared away. Tanker gives you speed in IAS but your HUD reads off in CAS. This is important. I remember wishing I had a radar gun to get the tanker's speed.... then realized that there's a very expensive radar gun on the front of fighter jets. Use this. The tanker is AI, it doesn't care it you lock it up (just don't blow it up!) in A-A or dogfight mode. The radar will then give you both the tanker's speed and closure rate (and distance!). Another trick that helped getting the mental picture was to turn head tracking off. This will let you use the edge of your monitor as you might use the canopy frame on another jet. Put a moderate ordnance load on the jet. A slick F-16 is really hard to refuel since it accelerates like crazy and then doesn't slow down. Rather than try to get your speed exactly right, it's OK to ping pong between the fore-aft position indicators with choppy throttle work. Practice is everything. And screaming into your headset. -Ryan

OK. I ran a repair on DCS, and made sure I didn't have any old nVidia DLL's swapping around or mods happening. Then, I got rid of forcing Preset K, and let everything run the "default". Spotting dots are back to 2pixels. Things are much improved. I think. As everyone said... there are now other artifacts happening. Thanks! -Ryan

Thanks for the help, All! Now I just need to remember all the places I force Preset K. There's the autoexec.... nVidia Profile Inspector.... and nVidia itself. I'll report back! -Ryan