

Recluse
Members-
Posts
1134 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Recluse
-
So, when you have an FTT TRK, you can switch to FLIR and watch the target being tracked, but the symbology is only the DIAMOND track not the POINT TRACK. When you move to the MAV-F page, you can see RDR in the HUD indicating that is what the MAV-F is slaved to. Despite the fact that the TPOD is also tracking the Designated Target, the MAV handoff is via RADAR in this case. True we do not have GMT or SEA mode which will break out the MOVERS, for targetting, but we can get the FTT track if a MOVER gets selected with SCS RIGHT on the radar. I have only managed to do this with ships or boats as I have not been able to break out small moving targets with the RADAR in MAP or EXP modes. As posted in the similar BUG thread, I could get a good handoff from FTT on a boat to MAV, but the MAV-F had a great deal of trouble actually locking, but it did track once off the rails.
-
cannot reproduce [NO BUG]TGP + AGM65F - Impossible to lock MOVING TARGET
Recluse replied to jed40's topic in Bugs and Problems
Hi Gripes, See my track above MAV-F_APC_Mover. Maybe it won't show what you want as the MAV-F was not "Slaving around" but did lock to the target when uncaged. FYI, I recorded the TRK in the latest Open Beta. When I replayed it in the STABLE version, the MAV-F NEVER LOCKED or fired. Replayed in OB, and everything worked as I remembered it. -
cannot reproduce [NO BUG]TGP + AGM65F - Impossible to lock MOVING TARGET
Recluse replied to jed40's topic in Bugs and Problems
In your track, you never waited till the MAVERICK was IN RANGE. Also, you need to hit TDC DEPRESS after the POINT TRACK. You will see the Offset Cursor Cross in the box. If you don't do this, it won't track and the MAV will aim at the original spot. Sometimes you have to get even closer before it LOCKS. I had this problem as well last night (STABLE VERSION) against a Tarantul Corvette. Has worked in the past against both ships and vehicles. Meant to test with a Vehicle to see if it was just a ship/contrast issue, but I was able to use the MAV seeker itself to get a lock on the ship. Just tried it in OB. Slightly different approach. I got an FTT track on an ARMED speedboat with Radar. Handed it off to MAV-F. Had to CAGE/UNCAGE a couple of times before I got the flickering LOCK/UNLOCK like used to happen with all targets. Got the Mav off the rails by pickling during a LOCK flicker. Then tried against moving APC'S using VVSLV FLIR Point Track. Took me awhile to get the Point Track in the attached TRK, and in this case the MAV locked fine even before TTMR countdown was done. Seem to have constant issues with Boats and Ships, though.. MAV-F_Boat_Flicker.trk MAV-F_APC_Mover..trk -
I will have to go back and try again, but the last time I tried, I could not get the CSEL line to work with a Mark Point. In my case, I was landing on an airfield with no TACAN, and created a MARK POINT on the end of the runway, then tried to make a CSEL line to follow in to land. I couldn't get the CSEL line to appear. Should it work for Mark Points? I used TPOD to make a TARGET POINT, and I didn't think CSEL would work on that, hence creating the Mark Point.
-
I think the ability of SA-10's to take out JSOW and other AG ordnance was something that has come and gone and returned, so, probably when that mission was first made, the SA-10's couldn't target the JSOW, but they now can (again).
-
YES.. FORWARD/AFT is the direction of the hat, "UP, DOWN" SSS DOWN (ACTION) is like SSS ACTION (PRESS) in the F/A-18 that is used for IFF interrogation.
-
There is a handy table in the POCKET GUIDE pp104-105 that summarized the SSS actions. I admit I didn't really understand this table until I actually saw the functions used in the aircraft, then it made "SENS(or)" :) I believe that this table was not really accurate in terms of the TPOD until the recent update to the GEN4, especially the double click of SS Down.
-
I have to say the same thing happens to me periodically. I chalk it up to TRACKIR being weird. Sometimes it returns to "normal" after quitting and restarting the mission or the game. Happens more often to me in the Harrier than the Hornet, but it happens there too and looks just like the OP's screenshots
-
After you achieve POINT TRACK with the FLIR, you need to TDC DEPRESS to designate the target (again). You will see the little OFFSET MARKER cross in the center of the point track box. It works for me with both F and E. For E, I have to move the TDC away from the MAV DDI to allow it to lock on the laser, but otherwise, POINT TRACK>TDC DEPRESS verify the FLIR is following target, Uncage MAV... works for me Here is a pretty good video..showing the MAV-F along with the pitfalls of its use in environments with other high contrast items. Similar video with GBU against Movers... same idea with POINT TRACK..
-
OOPS! Sorry! I grabbed the wrong link....Sorry about that!!
-
You have to make sure the DESG button on the EHSD is selected. Here's a recent Video
-
Did you hear the Ground Crew message "REARMING COMPLETE?" If so, it should be automatic. If NOT, you might have landed on a NEUTRAL or ENEMY base. You will GET the Rearm Radio item, and hear your "REQUEST REARMING" but if you are not at a base owned by your COALITION, it will not occur.
-
If you are using the Open Beta, AUTO (CCRP) bombing has changed drastically. You need to use the DESG function on the EHSD. Here's a video of what it looks like currently in the Open Beta. I don't think the STABLE version has changed yet. ..and here's a thread.... https://forums.eagle.ru/forum/english/licensed-third-party-projects/razbam/av-8b-n-a/resolved-bugs/7141808-as-intended-ehsd-desg-shouldn-t-be-prerequisite-for-all-auto-deliveries
-
I'm going to try once more: In the current 18-Nov-2020 patch notes, it said: Since the PREVIOUS patch made the sweeping changes to make you use DESG to get to AUTO MODE, WHAT part of that behavior did the current patch FIX????
- 1 reply
-
- 1
-
-
Good luck! We've been asking about this FOR A LONG TIME... https://forums.eagle.ru/forum/englis...gm-65e-and-tgp In MY particular case (which is different from others) I can get it to work with MAV-E SOI for stationary targets, but for MOVING targets (Boats, vehicles) I MUST make another Sensor SOI. Noticed it when using AG Radar to do a FTT track. Since the FLIR seems to be AUTO-CUED in the background I could lock and fire when acquiring a static target with Radar, and leaving the AG Radar up, but with a MOVER in FTT, I had to move the TDC to the RADAR to get a lock and fire. Haven't tried a MOVER since today's update.
-
Saw this for the AV-8B NA. Anyone know what this means? Seemed like the last patch totally redid the AUTO mode.. did it get switched BACK? Or fix something else?
-
Yeah, supposedly. I don't think the SHIP option PB does anything at the moment, though. I think they should work. I got them to work against a Tarantul Corvette moving at about the same speed, but, of course it was a much bigger target.
-
So, since the latest OB which gave us the FTT radar track, it is easier to find and prosecute them with AGM. Look at your radar for faint-ish horizontal lines. Might take some doing to break out the Boghammers from other surface targets, but it is better than pure VID. Mea Culpa to using LABELS so I can try for a VVSLV lock with the FLIR, but you still need to convert it to a POINT TRACK which is a pain. Once you can get the FTT radar track, it will automatically slave the MAV/FLIR onto it and you can prosecute with AGM as usual. Found that -E's work a little better than -F's due to contrast issues as described above, but you need to watch the RANGE. If they are moving away at 29 knots, you need to wait some time after the initial IN RANGE cue to make sure the MAVERICK can follow them. NOTE: I've only done this in missions I setup for practice, Never did that campaign. In the MAV F track attached, I never got a CLEAN lock, but as it flickered between lock and Unlock I managed to get it off the rail
-
Thanks for that! :thumbup: At one time I think I actually knew that. :smilewink:
-
Very nice. Question, similar to the one I asked above: No longer any need to use the Laser Rangefinding to fine tune the target? TPOD is good enough? Also.. just about all the drops were showing a very low probability of hit but they ALL shacked pretty small targets! Not necessary to obsess of pickle near 100%?
-
Yeah, thanks! I meant to mention that distinction around "multiple". On another note, as I was re-reading the Razbam notes above I was wondering about Step 8 and 9. Shouldn't you have to repeat Step 4 for the Laser Ranging after moving to a new target to update that for the new positions, esp. if it is far from the original?
-
Wondering if it is expected behavior that Mark Points disappear upon landing. Noticed this the other night when landing to re-arm and refuel and my Mark Points were gone. Tried it again and noticed that as soon as I touched down, (no rearm/refuel) the Mark Points similarly disappeared. (Created 2 Mark Points, so the HSI PB showed "MK3". After landing, it went back to "MK1" and the previous Mark Points 1 and 2 were no longer selectable.
-
https://forums.eagle.ru/forum/english/licensed-third-party-projects/razbam/7121409-razbam-2020-q4-update JDAM relative targeting JDAM relative targeting, also known as TOO mode, has become more practical. Initially you had to designate a target with the TPOD, lase it, and then LONG WINC to pass the target coordinates to the bomb and then release it. If you wanted to drop another bomb to a different target in the same area, you had to LONG WINC to release the previous coordinates and then redo the entire procedure for the new target. That is NOT how it works on the real aircraft. The procedure to do a JDAM relative targeting is as follows: