maxTRX

Meanwhile... in our DCS world: The Litening pod will maintain PTRK track once the radar is off (SIL), same when PTRK track is established without slaving to radar. ATFLIR will not. After establishing the AUTO track (slaved to radar), the pod will drop it as soon as the radar breaks lock or goes 'SIL'. If the pod's AUTO track is made without the radar lock first or with the radar off, the ATFLIR will maintain the track quite well. Short test run: https://youtu.be/9zBsaVHwwm0

It is implemented for... silencing TACAN DME. The radar and the radios are still happily radiating. I forgot to check the rad. altimeter. As far as ATFLIR 's A/A mode... will test it shortly. BTW, once EMCON is fully implemented, it might be a good idea to have some sort of persisting indication showing EMCON is on. Currently, nothing on HUD or anywhere else. Well, it shows on UFCP for some seconds then disappears.

I tested Exp3 again and basically it is useless... It takes too long to sharpen the image. Even if you wait that long, there's no way to tell what sort of object you might be looking at. I tried to focus on TU160 image and all I could see was a blob. Buildings or runways yea, I can see the features. In one of my tests, I was patient enough to let the radar do a full EXP3 scan, while carefully maintaining the proper offset from the target. The image was OK, the problem was... by that time I was 5 nm from the target. Now, the FRZ function doesn't freeze anything. Basically, once frozen it should be an image centered around the target (cross), rotating smoothly to show correct orientation from the jet. The MC knows the coordinates of the cross. How hard would it be for the MC to extrapolate any other point on the frozen image if a different target within the image is designated. Same as on SA display. In this clip (starting at 1:00) the target is designated in EXP3 and the 'cross' jumps over to a different location when I turned away slightly.

The only info I can give you is that this dampening issue has been going on since the release of OB. I think it's not as bad now as it was early on. I remember in some instances the oscillations would not stop (at very light weight, around 400kts). I have no idea when the FM update is coming.

I don't think the Hornet drivers in RW would put up with this blanking insanity we have here. Not only blanking but also radar coverage gap around the HUD frame when in HACQ/LACQ modes. It most likely works the same as in the Viper or the weapons symbology jumps to HMD when priority is on HMD. The HUD would retain the flight and nav data (repeated on HMD). When HMD moves over the HUD, the HMD's flight data is blanked out but the weapons symbology is only on the HMD and doesn't need to be blanked. It moves around with no gaps or duplicates superimposed on each other and jittering like hell.

Here's my 'detailed' description of A/G radar integration... It sucks. Well, I can work with GMT or SEA modes, the modeling is lacking or in some cases too optimistic but it does the job for my needs. After reading this thread I decided to try EXP3 scan on a big structure around Damascus. I had the WPDSG right on top of it and the ground radar was sharpening the picture in EXP3. I was actually impressed with the quality of the final scan before freezing it. I had the ATFLIR on LDDI so I could see the target clearly. I turned away slightly and the radar image snapped to a different orientation with TGT cross still in correct location. The FLIR stayed glued to the target. The problem started when I tried slewing the radar cross to various, clearly visible objects on the radar image. Whether I should or shouldn't be able to do this... I don't know, I suspect I should. The cross would snap back to original designation every time I moved it (could be an issue with my WH TDC) but the FLIR went bonkers. With every press of the TDC on the radar map, the FLIR would jump to a different part of the city, never the same location. I couldn't figure out any pattern. So, if the ground radar is not capable of re-designating on a frozen image, it shouldn't cause the FLIR to go stupid.

That's how I found it. Hey, I was planning on a trip back in a day... in the good ol' days (insert your own time frame ) but, got delayed. One day...

I was able to knock out the SA2's FanSong2 radar in PB mode. It was visible on RWR but not on HARM's TOO page. I marked the clip to start at 3:10 (PB shot at FS radar)

36SYC4483463035 On a hill east of Jounieh

I believe it's just north of Beirut, will verify later and post grid if you need it.

Hornet's radar and Amraams performed well in this 'gamy' type of scenario. The radar doesn't seem to like extreme banking maneuvers but... wasn't really a problem. Gun rounds were totally ineffective against Kh65's, talking strictly about damage model. As far as tactic of shooting a cruise missile right in front of your jet... not very sound, hehe.

I'm better if I just keep it off...

I tried switching back to radar track again from either pod. Regardless of the FLIR mode, lock or no lock on target, after putting SOI on the radar all we have to do is press TDC once anywhere on the radar display then move the bracket on target and bump SCS. Works every time. I don't think this is correct mech but... works for now.

It is actually possible to get back to radar track but it's very erratic. It took me 4 or 6 attempts, bumping the SCS and trying to line up the TDC bracket on the brick.

It is visible once the LST is tracking, simply because the FLIR video comes back on with LST aiming cross and the LST boxed. Yes, LTD/R code is also visible along with the rest of the display controls. I'm not sure if either pod should display the LST code during the search scan. I usually turn the scan on after calling the JTAC to lase and before I do, I double check the code.

I can't d/l your track now but... in my fairly recent GBU10 deliveries I didn't see any issues (one of the very few areas w/o problems) I used Litening pod. The tanker ship was locked in SEA mode from a long distance. Once at around 15nm, I switched priority to the pod (CCD image). Before I even attempted to get PTRK, I depressed TDC on the center of the ship (INR). When this was done, the radar was no longer driving my pod. I could see the brick and the cross roughly collocated. The pod was stabilized on the ship in INR. I bumped the SCS toward the pod twice and the PTRK was active. The center of the lock was more or less where it's supposed to be. I was approaching the ship head on, perhaps if the ship was crossing my course at an angle the centroid would have been off, I don't know. Turning away might not matter that much in this case but pointing the nose down slightly to allow the Pod hang in there for a few more seconds did. I was lasing manually. The drop was from 26k feet. When I turned back toward the ship again, the pod was dead on the target, still tracking in PTRK, in the center. Slightly OT: I was disappointed with meager explosion of the the tanker. 4x GBU10. No secondary... empty tanker, damn it!

As far as laser guided bombs go, I wouldn't fly directly toward the target after release. Turn away slightly to give the FLIR and LTD/R some room.

Hmm, I have to check this out for myself (the left/right DDI thing) As far as TGP loosing lock along with radar... was TGP in point track/auto before the radar hit gimbals?

I understand that perfectly. I was just trying to get some idea on the specifics of closed beta testing. Is it done at random? The testers get the build and test whatever they want or do they have narrow areas of testing that needs to be done by each group before the build is thrown at the rest? To me it looks like the devs bypass the closed group altogether sometimes. I've been around this stuff for while and got used to flexible time constraints and reoccurring bugs, etc. It's just... once in a while things get a little out of hand.

Try unboxing the sequence. Markpoints are not part of pre-set sequences. Edit: just noticed it is one of the steps in your OP.

I don't care if it's called early access or medium access... they need to straighten up their QA process so even if it takes longer to throw out updates, this one step forward, 2 steps back is getting old... and so am I, unless the main goal is simply non-stop 'updating'.

It even happens when I can see the jammer pods on the bandit and pointing my radar bore directly on him. No time to play around with director mode. Funnel on and... a head shot. ED's AI looses again

No, the last route waypoint for the SLAMER doesn't have to be collocated with the target so if your WPT2 was designated as a target, you only need to input ALT and WPT1 into the route. From WPT1 the missile should maintain WPT1 altitude until terminal phase. I don't think terminal parameters can be set yet and the default pop starts relatively far from the the target. If the target area has air defenses and your attack package doesn't include SEAD the chances of success are slim. The pop might be necessary for DL13 guidance though if needed. I haven't dl'd the last 2 updates so I'm not sure if anything changed. Nothing in the notes.

Yep, Hornet's radar and FLIR are at the top of my list. I understand that crashes and cloud jitters were important for lots of folks and I'm glad ED fixed them (I think) but... since I recently fly CAVU without a single cloud in the sky and had no crashes whatsoever, I skipped the last 2 updates and continue pummeling AI with the help of my broken radar and FLIR, hehe. I can only imagine my skillz level when these 2 systems are fixed. But wait... I keep forgetting about 'give and take' rule. The balance has to be maintained.

I don't think so but as you know, currently everything is 'drifting' in and around the Hornet