Bearfoot

It should appear as a row in the control setup page.

Awesome! Thanks. I use a left-hand roller ball mouse, but I think a trackpad would work a lot better. My mouse just sits on my lap for now (I had it velcroed to the side of my throttle when I used to have the TMWH, but with the WinWing it's too far away LOL). I think with a track pad I might need to secure it more strongly.

With the latest patch, we see that the AIM-54 uses distance vs time to go active. Previously, when using ~16s TTI, we could see on the TID the countdown and have an idea of when the missile would go active, planning our maneuvers accordingly (i.e., when/if to crank etc.). (1) What can we use now? Is there a ballpark of time based on distances? E.g., large ~16s, medium ~10s, etc.? (2) Also, will the countdown timer still flash when the missile goes active or is there any other indication that the missile has gone active?

I've never had a single F-14 track ever work. Ever. :(

Could you share the setup? E.g., which trackpad? And how do you attach it to the strap?

Ok, this is cool. Very, very, very, very cool.

I would like a data cartridge just to not need to laboriously plug in coordinates in VR! For this and other GPS weapons (JDAM, JSOW) It would be nice to go from user mark points on the F10 map to a data cartridge like both the VIggen and the Harrier can do. So, what is the range increase between Paveway II and III? Wikipedia etc FWIW says from ~9-10 miles to ~11-12 miles. Of course, altitude and speed dependent. Which stills puts you inside the threat radius of SA-11's and -6's (and, of course, well inside the belly of the SA-10).

Hi, Please add me to the list. Do I PM you my email etc.?

SCS depress over track in the air-to-air radar page will IFF the track.

Hind vs Cobra in the Iran-Iraq war:

I too find JSOW A's extremely unreliable (OB). Sometimes they work, sometimes they don't. Not sure if it is my switchology/,echaniszation. This thread: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/7112978-need-track-replay-agm-154-jsow-always-off-target-or-simply-disappears/page2 suggests that it might be range issue. @Bunny Clark perhaps it would be worth seeing if you can consistently get failures when > 25nm and successes when less?

First of all, THANK YOU so much for this incredible engine. It takes DCS to another level! Would it be possible to have an option to add vehicles capable of resupply near SAM batteries? They need not be the same group, but need to be close. GAZ-66 KAMAZ-43101 GAZ-3308 KrAZ-6322 M818 Ural-375 Ural-4320 (either) This would allow SAM's to rearm. Otherwise it seems with lots of action the battery gets exhausted immediately and then is a sitting duck (which takes the fun away from both sides!).

Which is all fine and dandy in the spirit of speculative discussion, but does not really address as to whether or not this is a bug and if it should be fixed.

As someone noted, we keep going round and round in circles. Fact is: it works one way for some folks, another way for others. Consistently. And contra to documentation. And so, presumably, some of us are dealing with buggy behavior while the others of us are dealing with correct behavior. Parameters are ALL the same across trials, and set up for good launch -- uncaged, good designation, laser in FOV, within range, missile armed, yada yada yada yada yada .... It's great that folks continue to contribute their personal experiences on how they fire laser mavericks. Lots of lessons to be learned. But what would be extra helpful is if folks that think they have an insight into what's happening actually take the trouble to view the (MANY) tracks posted on this thread, and specifically apply their expertise to comment on those tracks to see how this follows what they think should be happening (or not). That way, we are actually talking to each other about the issue.

I have the same problem as described by the OP --- 154A (only; 154C works fine) many times seen overflying target and then veering off to crash behind the target. On some occasions, I've had hits. Never figured out why one but not the other. @williamzporto : your findings are very interesting, and may explain the inconsistency!

I have not tried the patch yet. However, there is this line: While everyone is referencing the stuff about E will not fire after F launched stuff, it seems that the above might be related to the bug discussed on this thread? Not sure why the description is limited to "a building" though ...

Finding things through the "fuzzy straw" is hard. But you can make things easier than what you are doing. You should ground stabilize first: TDC depress on some place near the tanks or at least near where you want to search. For e.g., on the road. Put the aircraft on AP (alt/att) and then sweep the road slowly for the tanks. Still should be tricky, but a LOT easier than you describe. Note that images only start rendering about 40-50 nm (? not sure of exact distance) out. Otherwise you just get a blank.

Same. Applies to F-14 wingman to human player. Or 2 x F14 AI as well.

Doesn't work for some folks some of the time, and doesn't work for other folks any of the time. Even with LTD/R flashing, and everything else within parameters (incl. seeker X in the right place) maverick will never see the laser. Need to assign TDC back to TPOD for maverick to see the laser, lock, and launch.

Sure, but it depends on what the weapon uses and expects -- AGL or ASL. Either would work. But if the weapon expects ASL and you give AGL it would be just as off as the other way around. With (consumer) GPS you can easily get ASL based on the WGS spheroid. AGL is more complicated and requires terrain data to be available. No idea what the weapon uses or, more to the point, what the DCS implementation of the weapon.

That might indeed be the issue. The F10 map shows elevation in ASL. I assumed the elevation in the missile programming / waypoint designation would be ASL as well. Is that not the case?

I agree with @Honey. I can easily put JSOW rounds on target (either A or C) by using either (a) TOO + TPOD designations or (b) TOO + TPOD markpoints + waypoint designations. But TOO + waypoints (LABORIOUSLY!) created off the F10 map and entered in the UFC, even in PRECISE mode (with elevation ASL in feet as well), send the round past the target doing nothing. Fuzing set in inst. So far only tried JSOW 154A. Probably should get its own thread. If @Honey does not open one with tracks, I will later when I experiment more and get some tracks.

For LGB's, you do not need to "manually" update the target designation. A simple point track (even without the offset cursor) works fine for the laser tracking, of course. But I guess you are referring to the Auto release cuies? I guess the Auto release cues may not update but with ground vehicle speeds not sure if that makes a difference in practice -- the difference is made up for by the guidance. At least, I find LGB plinking moving vehicles having so much less a fiddly switchology than either Mav F or E. (Of course, LMAV's have other issues where (for some people at least) you cannot launch till the TGP is SOI (or I guess "TDC assigned to TPOD format" in Hornet-speak. But that's another story.)

Yes, as I and others have stated on this thread -- all parameters are correct: laser armed and firing, MAV seeks is correctly the laser (X in the right place), etc., but simply will not lock till and only until TPOD is SOI. You cannot fire the Maverick while the Mav is SOI. Whether this is correct or not, I do not know. BUT: (1) This clearly was not the case a few patches ago, as many videos/tutorials written then do not mention or (in the case of video) show the SOI being TPOD when firing. This includes Wag's academic series as well as tutorials by third-parties (RedKite and others). (2) No documentation mentions needing to set SOI to TPOD for firing. More to the point: (3) On this thread and others, many, including yourself, say that this is not the case for them -- so there is inconsistency. (4) Some on this thread say that they sometimes find this is the case and sometimes not. (5) The tester (or somebody) has declared this as "CAN NOT REPRODUCE". So, IF it is correct behavior then it appears that lots of people, including yourself and the ED tester, have broken installations. Either way, the inconsistency itself seems to me an issue.

- TDC depress once to get the offset cross. - TDC depress again to designate the point (this will be the point the TGP will diamond will slew to when you do the next step). - SCS in direction of format (e.g., right if TGP is on the right DDI) to cycle out of point track. You should get a diamond at the place of the offset cross.