RyanR

Thanks!!! -Ryan

Here's a track with the centerline eventually coming off at the very end. I had unlimited ammo set so that I could keep trying until the problem appeared. That said, this problem occurs after 15 minutes flying across Afghanistan with limited ammo in MP. Thanks, -Ryan Centerline problem.trk

Not sure if this is the same problem, but similar. If I put MK-83's on the wings, and four SAMP-400's on the centerline pylon, when I release in single mode (with wing and fuselage selected) after flying for 10-15 minutes, all four SAMP's and the centerline pylon come off at once. No exploding. I wonder if this is related somehow to the nav/gyros all going crazy and then CTD. Hard to get a track file right now. Thanks! -Ryan

I came here to bring up this exact bug. Glad that I'm not alone and that Aerges has a fix! So, next DCS patch? I can wait! Thanks, all! Thanks to Aerges for making such a wonderful module. The F1 is still my favorite not-an-F-16. -Ryan

That's what I meant. -Ryan

Either the pod is finding the emitters, or you're using the weapon itself as a sensor. Viper has a pod and the weapon (HAS). Hornet just has the weapon (TOO). -Ryan

Yup. Plus, if you SOI the HARM WPN page, you can step between the different emitters, there. Handy when running around on the deck. -Ryan

That's what I thought. The F-18 folks are able to find EWR's with "HAS", then slew the TGP to that point on the HUD, and then kill the EWR. The F-16 can't even see that. Based on what I've read, it seems that the F-16 implementation is correct, and the Hornet has a loophole. No biggie. Just jealous. I want the Viper to have a monopoly on the SEAD stuff. Thanks! I'm finding so many great HOTAS functions. Seemingly insignificant until I found out where they're useful! -Ryan

I've been re-reading the manual trying to pick up things I've missed the first few times around. The updated manual is excellent! With HAD as SOI, and an emitter designated, TMS-right should step to different targets. This is not working. What am I missing? Second question is of no importance: The F/A-18 in DCS can find and target Early Warning Radars with HARMs... the F-16 can't with either HAS or HAD. I suspect the F-16 implementation is more accurate. I'm just jealous. Thanks! -Ryan

Something I've learned: don't boresight Mavericks on the ground. Doing it while airborne is the difference between OK and perfect. -Ryan

In addition to AGR, the TGP should be involved as well. I recall this issue (bombs falling short) predating the ATP, so that is not likely a culprit. Incidentally, strafing works AOK. If Bignewy is willing to follow this thread, we should try to be systematic and get some tracks. I'm happy to get some tracks together. Would it make sense to build a quick "test mission" with some targets that we could all try to hit with some predefined parameters? -Ryan

CCIP has been dropping short for a while now. I'm not really sure why. Some of the guys find that more time for the INS drift to accumulate affects the amount of error. That seems odd, as CCIP should be independent of INS. -Ryan

ED seems to be quietly tweaking the ATP in updates. We've noticed some minor changes that aren't in the changelog. I'm really liking it. It would be nice to have an option to speed up the BIT for cold starts. -Ryan

You need to set the CMDS knob to semi- or auto- -Ryan

You don't have unlimited fuel enabled? The client planes aren't already with 100% fuel? I agree, post a TRK. I wonder if there is a gremlin in your .miz file. -Ryan

I think you are correct. I tried a few presets, including J and K, but wasn't super happy with any of them when it comes to spotting. I feel like DLSS just sees other aircraft as "noise". -Ryan

One thing that needs to be tweaked is when "the dot" turns into the plane model. Right now, the dot disappears when the model is still smaller than the dot. DLSS has its own problems, and it's a moving target as nVidia keeps kicking out new presets. -Ryan

I'm having much better luck with DLAA, but running not-VR at 1440px with a 5080 doesn't require DLSS. -Ryan

Thanks! It's not a big deal. -Ryan

THX @BIGNEWY! -Ryan

I feel like 50% of the time, AWACS isn't anywhere near as good as it is in that video. When you need it most, it's not there. -Ryan

OK. So it is supposed to be hidden? No way to unhide it other than to lase? -Ryan

I thought to grab a couple screenshots last night from saving the new head position after an FOV change. I think the only way to start over is to delete the the snapview.lua in Saved Games. the one in the DCS directory doesn't do anything. The lua in the Saved Games directory will persist after a module reinstall or repair, so you must delete it. Once you do that, start DCS without head tracking, hop into the Fulcrum, adjust the FOV, and then save the snap view. Good luck. -Ryan

Something more than the FOV got changed. You may need to delete your snapview.lua and start over. -Ryan

Here are the conditions to get the empty bracket. Uncheck the MiG-29 in the NS430 special options, but enable the NS430 for the Fulcrum in the ME. So if a server is running a mission with the NS430 enabled, you'll get the empty bracket, unless you disable the NS430 module. Could I simply be trying to disable the NS430 wrong? -Ryan NS430.trk