RyanR

I assume I'm supposed to shoot Gator in the F-5.... but my cannon is dry. I have both air sources selected. I fenced in. Followed all the check lists. I'm just chasing an F-5 across Nevada with Jester yelling at me to shoot him. What gives? Also.... but less important... I can't hide the control stick. -Ryan

This is a different issue, it seems. No ordinance dropped.... didn't seem to be ordinance specific. Toggling NAV/A-G doesn't make it go away. It's pretty rare. I've only seen it one or two other times since my original post. -Ryan

Wow? Where can one get these paint kits? I've been having fun with just messing around with the ED templates. Thanks! -Ryan

Two different weapons systems, really. Just turn JDAM's "on".... they'll be happy when you need them. The sensors on the plane get the GPS coords, and then send that to the weapon. The bomb now knows where it is and where it needs to go. Mavericks care nothing about GPS coords. They technically don't even care about what any of the onboard sensors tell them. They're optical. They chase an optical target that you tell them. You absolutely have to boresight them to the targeting pod, which ultimately also aligns them to the HUD to make them easier to target when things get hectic. So, yes, turn on the weapons, and they will do what they need to do in the background. Just remember that Mavericks need boresighting when they come up. -Ryan

OK. I tried making a new simple mission in the Caucus map. Everything works perfectly. As advertised. Track attached. What could have caused trouble with the NTTR map? -Ryan Works in Caucus.trk

To reiterate, all of the following situations are fine: -It's broke. By definition, the Viper is a WIP, and that is totally understandable. I'll live. -It's how it's supposed to be. That these sensors work as well as they do boggles my mind. Technology is incredible and never perfect. -I'm doing something wrong. I will not debate that I am an idiot. In fact, I would debate if someone claimed I'm *not* an idiot. I'm just fishing for some sanity. Are others seeing what I'm seeing? -Ryan

Track attached.... maverick_TGP-offsett.trk F-16 uninstalled, all files deleted, then F-16 reinstalled for the above track. The yellow MFD mod was the only mod I ever used, and I deleted all traces of it. Same result, unfortunately. After this screen grab, I SOI'd the WPN page, slewed the crosshairs over, instantly locked up the target, and blew it up. The discrepency between the TGP and WPN pages is enough that auto-handoff never works. -Ryan

Agreed. I figured the yellow MFD mod would raise some eyebrows. I've had this issue long before trying the yellow MFD mod. If no one else is seeing what I'm seeing, then a reinstall/repair may be on my list. This isn't a bug report, but rather me asking if anyone else is seeing this "phenomenon". -Ryan

Is this as good as it gets? Is it a WIP? Or am I doing something wrong? All/any of these answers are fine. Here's a screen grab. Hot, in air, start. Toasty BTR80 as a targt. Mavericks should be "boresighted" automatically. This is what I'm seeing at 3nm after trying to auto-handoff continuously from 14nm out. Is this what you guys are seeing? As I close the distance, flying straight at it, the offset bewteen the WPN page and TGP gets worse. The reason I ask is that I'm seeing the same problem/offset every time I do the boresight process myself. It's easy enough the SOI the WPN page and nudge the crosshairs over and lock it up. I've noticed this as a problem ever since the INS work popped up. Thanks, -Ryan

Something has been "off" since the INS update a few months ago. A recent fix made it "better", but it can't be right. If this is "correct as is", then auto-handoff does not work at all on the real plane. The Maverick seeker is considerably "off" from the TGP at 7nm.... and the disparity degrades from there. Manual slewing the Maverick in the WPN page works fine, and the TGP gets you pretty close. Though, every time you fire a Maverick, you need to DMS-down to the TGP to get the missile on the opposite pylon to look where the TGT is looking (the SPI). This can't be correct either. In the end.... it's OK right now. I suspect we need to simply wait for the Sniper ATP to come to fruition. -Ryan

I got into DCS "late" (Early 2024), and quickly got sucked into the F-16. I've missed most of the Early Access. I really love the module. Yes there are niggles, but has there ever been a flight sim without niggles? I enjoy the endless learning that comes from the depth of the avionics and modern EW environment. I was just reading the road map, and the last thing on it for EA is the Sniper ATP. Exciting. The existing targeting pod and DMS logic seems to be one of the more frustrating things on the forum. -Ryan

Leave the HAD as SOI for as long as possible. With the TGP in the opposite MFD, it will get closer to the emitter as the HAD gets a better quality location. Not foolproof, though. Still a bit of a needle in a haystack, and you have to slew the TGP quite a bit to find it. I bet this works a LOT better with a donor over the datalink, so you can get down to PGM1 with plenty of distance. Once you find the emitter, marking it is standard stuff. -Ryan

Many thanks for the response! Perhaps I can use "Junctions" to send some other programs to another drive. I *think* I have a free NVMe slot in this machine. I dunno why I didn't take notes last time I had the case open. Definitely need to save some pennies for one. See how long I can push this out. I *really* want to upgrade my rudder pedals first. -Ryan

DCS is *huge*.... and is just going to get bigger. I downloaded the Kola map to support the project, as well as a few others, and a was surprised to only have a few GB's left on my 1TB SSD boot drive. Not surprising since I have all my Autodesk/Adobe/work software on this machine. I cleaned house quite a bit, and got an extra hundred GB's back. With the last update, I still didn't have enough space to install it. Soooo.... I uninstalled some terrains/modules that I'm not using. Job done. Of course, when I want to reinstall those modules, you have to download them from ED.... which takes a long time. Two hours. Lot of data! Is there a way to "save" module installers on another drive, so that I can just pull them back in? Or is this just impractical with updates making potential "saved" versions obsolete? Can you spread a DCS install across multiple drives? What do you guys do? I've a 2TB data drive.... but it's full of.... data. It's also a spinner, so slower than an SSD. I can't remember if I've another hard drive bay in this box. I guess I could do a DCS specific drive. First world problems. Damn you ED and third party developers for your super cool sim, planes, and places to fly them! Thanks! -Ryan

Pretty cheap for the amount of work that goes into this stuff for a niche product. Hardware is what's expensive.... -Ryan

Wags has a vid on YouTube. My next port of call is to get a screen grab of what each bomb can have and start researching them individually. -Ryan

Actually the thread you linked was the one I was referencing: Sounds like the Lightening/LANTIRN mish-mash will become LANTIRN (I'm guessing the AN/AAQ-14 targeting pod) after the Sniper ATP? Just clearing my head is the trick these days..... The other question was simply how much "precision" should there be between any of these targeting pods and a Maverick seeker in the best case? We do a lot of complaining on the forum about this, under the assumption that perfection is reality, and deviation from perfection must a bug..... however reality often is imperfect. Thanks, -Ryan I said "over my head", not NineLine. It's all good. -Ryan

I'm still a newbie here when it comes to avionics after 1945. There's another thread on this that's a bit over my head. It's all fine, as the F-16C module is still super cool, and an endless source of learning and fun. Could we have a quick, not-too-emphatic thread about what we have on our Blk50? We have a mix of Litening and LANTRIN in our TGP? Not Sniper. The pod we have will eventually be modeled as LANTRIN? The other hard-to-answer question I have (if we're working with a hodge-podge of pods) is, how much precision *should* there be between the TGP and a AGM-65 seeker? "Video game" logic would dictate that once you boresight a Maverick, there would be laser-like precision between the two sensors. However, since DCS simulates the avionics this some level of imprecision might be expected. Yes the INS development may be impacting things negatively, but I dunno what we should expect. The INS work is super cool, by the way. To start this thread on a positive note, I've been captivated by the F-16 since Falcon was initially released in 1988 on the Atari ST and Amiga. I read the manual probably a thousand times. Read everything I could on the F-16 back then. I got into WWII sims at some point, and stayed in that era for ages. The DCS F-16 brings me back to being a kid again. It's been endless fun, and endless learning. Thanks, -Ryan

Thanks for the update! Info from you guys really keeps the experience enjoyable. -Ryan

It is a bit creepy to look down at the ECM switches.... -Ryan

Here's a sloppy run through the same setup with an air start. Boresighting should be automatically set up. I still had to slew the Maverick seeker in every case. BTR-80's are nice, hot targets. Still, auto-handoff is hopeless. Is this how "reality" is? I would not be surprised, given the zillions of variables. I'm still dumbfounded that all of these sensors can work in concert in real life to the level they do in-game. Thanks! -Ryan maverick_hot_start.trk

OK. This makes sense. Fix this problem, and the need to MFD back and forth "issue" goes away. Thanks! -Ryan

Had a chance to play around with Maverick boresighting. Seems better, but not fixed. First, the MFD behavior/logic has changed..... again. Tremendously so. It's like learning DCS all over again. If the WPN is SOI, when you cycle between the two wing stations in PRE mode, the missiles just point straight ahead. Regardless of where the TGP is pointed. In the past, they always slaved to where the TGP was. Now, you have to go back to the TGP MFD to get the Mavericks to slave to the TGP... and then back to the WPN MFD to lock the missile up. Sooooo.... even with a good boresight, you're constantly going back and forth between the two MFD's with DMS-down. Sometimes TMS up jumps to WPN.... mostly not. To fire multiple Mavericks you're jumping back and forth between the two MFD's. Second, the missles boresight much, much better.... but not good enough. They're off a bit.... so much so that there's almost no point in using the TGP. The Auto-handoff is hopeless. I boresighted at least three times in the track attached. Once on the ground, and twice in the air. -Ryan mavericks.trk

Yeah. I thought the pilot model would be kinda lame.... but the kneeboard function is super cool. That HARM code page is quite neat, too! -Ryan

I just saw the other thread about the change in the changelog. I'm getting old, but I didn't think I was that old. -Ryan