LastRifleRound

This is completely broken now. Automatic handoffs don't work at all as far as I can tell

It definitely doesn't work right, because you can trick the system into functioning properly by TMS up, DMS down to get TGP as SOI again, then use TMS right for all other designations. Only problem is if you slew in point track over something you don't want and linger too long it'll hand off every time you stop slewing, when it should really wait for another TMS up or right. This will force you to DMS back to WPN and TMS down to break the lock. The way it most likely works in real life is TMS up once to point track and hand off. TMS up again will switch to WPN. Slewing in point track won't hand off until TMS right is used. Subsequent TMS up once in point track switch to WPN. That's how the other two modes work, how the real manual describes it, and makes the most sense. Preponderance of evidence is making this look alot like an FA18 ATFLIR offset cursor situation.

What is the practical affect of the INS changes for the F16 going to be? What will the player notice? Are there any behaviors they should change?

I gotcha, keeping up with the update pace can be tough, but some of the systems this stuff is based around have been around for over a decade, including the JTAC. I recommend looking up some of the A10 videos on youtube of people dealing with the JTAC. The code the guy gave you are coordinates in MGRS format. If you go on youtube and search "DCS Viper MGRS" you'll get a useful tutorial on that. However, if you watch some of the videos on how to work with the JTAC, you'll see DCS is assuming some knowledge from you on how to work with JTAC you probably just don't have yet, namely that if you did a few more radio calls, you'd tell them you were inbound, and they would then mark the target with smoke, and the mission triggers would likely work at that point and you'd be able to proceed. As far as sighting, I struggle with that, too. There is an option in labels to have, instead of labels which kill immersion, dots to be superimposed over all items. Visual acuity in DCS is MUCH WORSE than in real life, and ED knows it, but there just aren't many good options for it right now with the current tech, so this method is provided as a stop-gap until the engine is further refined. Don't be ashamed to use it, it's meant to be used and it's not cheating. There's plenty of coaching available, I had a brief time with an online squadron. I can't remember their name, but they were very cool guys and life commitments didn't get in the way I'd still fly with them. I didn't need so much training at the time, but they did offer it. That's not helpful save for the fact they're out there and I don't really know anyone who had a terrible experience with one. The general cattiness you see on these forums goes away once people start talking to one another one-on-one in a cooperative environment. Good luck.

Yup, we're on the same page here. You shouldn't have to make a mark point at the designation, then set the O/S on that. In your example, you should be able to apply the O/S to the waypoint, designate and refine on the JTAC, then hit O/S and be staring at the target with no other steps needed.

Yeah it's weird. When you give a waypoint an O/S it becomes an OAP, because you are supposed to be aiming at it. When you have the OAP designated, and then refine it, say with TPOD and designating with TPOD, hitting O/S should apply the offset to that new, designated position. Instead, designating the OAP, then refining the aim point, then hitting O/S makes the O/S overwritten with the designation, instead of applying the O/S to the designation.

That's part of what makes what I'm decribing necessary, but it is not itself what I am describing. Also offsets are DEFINITELY involved with INS drift. Please read Hornet tacman, see W-OF function in Harrier tacman, watch linked videos in A-7 forum, or reference dash manual for the Viper for OAP/VRP/VIP if you don't understand. Could also be a scenario where you have a great relative reference but poor absolute coordinate positioning.

Use FRZ mode to avoid the snap-back issue for now, works well

It's my understanding from the TACMAN that offsets in the Hornet should work like this: Let's say we set up a waypoint on a prominent feature, like a radio tower. Let's say our offset will be a target that is a known bearing and distance from that tower. Let's say by drift, the waypoint is displaced a bit. When I have the tower in sight, I designate the waypoint, then slew either the HUD or sensor over the tower. I hit offset, I should be looking at the target. Instead, any slewing or designating I do on the waypoint changes the offset to what I designated, and no offset is applied when hitting offset. Am I wrong here? The current implementation makes no sense. There was this comment in the November update, but it doesn't seem to work. Fixed: OAP designation is incorrect with CCRP - fixed calculating relative TD OAP position

There's a bug burried in an intentional (though possibly not correct) change. AUTO target handoffs are bugged. The handoff is only attempted the first time you TMS up on the TGP, whether successful or not. SOI then changes to WPN. If you undesignate (TMS aft), then DMS down to make TGP SOI again, any subsequent TMS ups will NOT engage the handoff, and will instead only change SOI. The only way to get it working again is to cycle the modes to VIS and BORE back to PRE EDIT: just read the post above about TMS right...maybe intentional then? Will check it out tonight.

Same here, can confirm order does not matter. If you set VRP to MSEL, THEN change bombs to CCRP the crash happens immediately upon clicking CCRP. Also was not online, was just a single player mission I made up in the ME.

No way the Hornet still has bombing issues? It's only been 4 years and it's early access so you deserve it. Oh, it's released? Well it's your fault because open beta. It happens in the stable version, too? Ummm....bombs aren't that accurate. Real pilots don't use auto or something. Need more tracks, thread closed because we can't reproduce and if we can it's supposed to do that anyway. You don't know it's a bug because you don't know the exact version, revision and favorite kool-aid flavor of everyone who worked on this Lot Hornet's software. Go TOO ripple 43 JDAMs or something. In all seriousness, try making sure the temperature in your mission is 20C, there is a glaring error in certain designations at lower temperatures that I'm not sure is throwing the aimpoint off (it's always short when using radar and waypoints). Probably not the issue as in the Viper you can correct the designation in the hud by slewing on target before release but it will at least prevent the two bugs from compounding on one another, as the temp bug is a universal DCS issue at the moment. I've posted 4 or 5 bug threads about this issue in its many forms throughout the years. I'll tool around tonight and see if I can't add more tracks for you, though at this point I'm not sure it will help. It's been years of the same issue.

Good stuff my dude

Did you have LGB's or Mavericks, too? Even though they're at 0 if you already used them, you can still see them on the SMS page. If LGB's, use DTOS, if Mavs, use VIS. TMS up long to make HMD SOI, look at target, TMS up short, DMS down to get the TGP to be SOI. It's not much different than the A10 except the part where you have to pick a delivery mode. If you think you'll need to save that point for reference, hit MARK, then SEQ right to TGP as source, TMS up. If you want your new MARK to be active Steerpoint, hit MSEL while still in the MARK page. I really don't think it's that hard and the debate on who made it and why I think is based on the entirely subjective suppositions on how "clunky" it is when doing DCS stuff. Even for DCS stuff, it's not any harder than the Hornet is, and the A10 was purpose made for DCS stuff so you can't expect other airframes to be as good at loitering and plinking. In fact, you could argue DCS itself was built around the KA50 and to a lesser extent the A10, so DCS was built around this kind of mission. Give it some more time and I'm confident you will all will get in the flow in now time. I never thought it would be, but the team on the Viper has done an excellent job in my opinion and it's probably my favorite at the moment.

The confirmed issue is that bearing entry isn't working and is always 0 no matter what you enter. Are offsets being moved as a result of designation also reported? I didn't see it.