maxTRX

My burble work-ups: and, finally mustered enough courage for Mode1 + ATC. It actually followed the ball (for the most part) Of course, the 'wake turb. was disabled:

UncleReiben's tip works. Disabling wake turb. is definitely an effective temporary fix for the silly nose wobble. The downdraft is fairly easy to deal with now. The upward bump might be a bit tricky but after some practice flying the ball all the way down is becoming a routine.

Finally today I'll have a chance to burble around again and experiment. On my last attempt (right after posting my above vid.) I was able to fly the ball actually and hit the 4 wire and it seems I can do it consistently. 3 wire... sure but it doesn't look right. I have to either overpower, cut and go to MIL way early to hit 3 wire, with the wrong AOA or... jockey the stick a little as described by couple of people here already. Forcing the stick forward at the ramp should be a big nono. I haven't disabled the 'turbulence' yet and will definitely try it tonight. I wonder if anyone (including RW boat experienced folks) managed to fly a perfect ball through the burble w/o doing 'silly' stuff. On a different note: I added one extra item to my pre-landing checklist. 'Home' waypoint on FPAS page goes to #58 (blank)

This bug has been around for a while: https://forum.dcs.world/topic/297695-ag-gun-after-using-jdam-issue-update/?do=findComment&comment=4936693 The thread above was not the first report on this bug. It's related to using A/G gun after any GPS weapons have been powered up.

It's a start. After a while and bunch of YT vids, you might decide to get deeper and finesse the 'stuff'. Lots of good reading material around the forums.

Son of a... , just had my first exposure to the burble. I'm late to the carrier ops after the latest OB update. I flew 2 case 1 patterns and it seems like I have some work to do, to re-learn flying 'burbled' ball. Unless... ED beets me to it and make it more manageable. There seems to be a downdraft in-close and I could probably learn how to power through it but this nose-up over the ramp (it seems more like a pivot along lateral axis) followed by a nose down wobble, which brings the hook up and makes alpha lower made me bolter twice in a row. The ball needs to be centered or tiddly bit up almost all the way to the wires. Well, I'll try... Thanks for the 'wake turb.' tip UncleReiben. Lets see if that works. Here's how I got burbled on my first case1:

It seems like a few players are still reporting them. This thread (locked): https://forum.dcs.world/topic/280503-fa-18c-hornet-tws-messed-up-by-ghost-target/?do=getNewComment As far as 'phantom' radar tracks and empty TD boxes associated with them or not associated with them, I haven't seen any so far, in the latest OB. My understanding is that this type 'ghosts' have been fixed... hopefully. Now, the radar tracks of your own and other missiles, that can be designated and 'stepped' / prioritized with NWS button can certainly contribute to confusion. This PROBLEM is still there and it seems like some folks are also referring to it as ghosts. Perhaps the various 'gates' and things will fix this issue in the future, who knows. Anyone?

No, not 'schooling' anyone, just spontaneously chiming in.

Oh, I don't know... the big picture dictates the tactics. In my sim-gaming experience (few years online, then AI hordes), it almost always comes down to what happens after that first shot. Do you just want to simply defeat this first shot and reposition/reattack or... ride the 'edge' till the next shot(s) comes off the rail. That's where the fun was and is for me. Now... current Amraams don't annoy me as much as the crippled Hornet's radar. (That's the only jet I fly until ED fixes it, then... I'll purchase everything else ) The most annoying is the 'stepping' logic between the L&S and other tracks to include your own missiles. Inability to overcome the sidelobe noise at fairly low altitude, say 3, 2k ft. agl. and couple of other things. I need to play with current Amraams a bit more... so far I couldn't spot anything radically worse or even different from previous versions. PS. humans or bots... there's fun fighting either, although 'bots' have a long way to go... come on 'noah, klaus and bill'

Tested BOL and R/BL after the patch... seems to be working.

Lookup performance is also the same as before the patch. Side lobes noise is 'jamming' the radar very effectively.

didn't realize it was that easy... that's all

Hey...

I just need to correct my assumption that MSI is not implemented at all. (Bug forum thread, yesterday) Some of it definitely is. FLIR and radar work fine together. Perhaps not as automated as I'd like to see it but there is a good chance that it worked like this in LOT20 and others. I just have to be patient (and sober ) to get in range for PTRK lock on FLIR. That will make other options available.

Time for an edit... I was wrong about MSI between FLIR and radar. It actually does work. What threw me off was inability to lock the target in point track mode on FLIR. I guess I assumed that once the target was visible to my eyes, it should have enough contrast for PTRK lock. That's why the 'slave' and 'sil' options on FLIR were not visible at that time and my quick conclusion was... OK, it's not working yet. I flew the mission again and waited till closer range to use PTRK and voila... This a bit OT for this thread. I just needed to correct my previous statement. https://youtu.be/GSg32f6WcqQ

Well, I did find out... same bug without AWACS. It manifests itself differently: in RWS, the ghost might show as AACQ cross. It cannot be locked though. HMD will not show anything. In TWS, it might look like part of HAFU, HMD might show a TD box somewhere else, etc. Now, the target 'age' thing... If a target is flying straight and level and is designated as an L&S, age set to 32, I can complete a full circle and still have it designated, with AWACS support or without. I also tried to see if FLIR 'sort of' works as MSI. It actually did maintain a lock and 'think' I saw the L&S pegged on the edge of the radar page. (would have to check the video). Especially when using Litening pod, I was able to turn away quite a bit. On SA page the target showed at my 4 o'clock. The FLIR lock was extremely shaky and easy to loose.

In all A/A missions I recently flew, AWACS was always a doner. I wonder if this 'ghost' bug only shows up when contacts are received via D/L... time to find out, will hop in shortly. As far as target 'age' is concerned, when designated as an L&S and it's set to say 32 secs., it will be extrapolated for entire 32 secs. outside of gimbals or not. I made a complete circle and the L&S was still there, pointing at the wrong part of the sky when I turned into the bandit again. After 32 secs... blank. AWACS didn't help. Yea, I know, it's hasn't been implemented. STT lock will always get dropped past the gimbal limits, of course.

It is a mess in every sense here. First... press 'emcon' and run to safe area then re-evaluate everything (including HMD/HUD setup) OK, that one was OT. This is definitely not right. Perhaps related to the ghost radar tracks bug. I've seen worse, the radar showing L&S in one direction and TD box on HMD in a different spot. In some of the old OB versions, if you set your 'age' to 16 or 32 secs., it was possible to make a complete circle with the radar maintaining 'extrapolated' position and of course... lining up on an empty TD box. That bug has been fixed a while back. The radar shouldn't extrapolate past the gimbals now, the last time I checked. Then, playing online probably adds more stuff to consider.

Cool, I'll definitely get into complex mission building soon... These crazy ideas bouncing around in my head need to come out

This thing goes on for a while

Go on... . If I only had more time to play around with all this stuff.

Yep, 'J' was there. For some weird reason, the first press of the 'SIL' button simply drops the track. The second press silences the radar.

Is everyone here running on different builds? Perhaps MP makes a difference. Here's what my radar does (latest OB, tested in SP only): WonW puts the radar on stby. Maltese cross is showing, scan stops. I had a ST lock on a friendly when approaching a runway on short final. Stayed in A/A and maintained the lock till touchdown. About 4secs after WonW, the lock disappeared, radar went to stby and the contact changed into D/L fed symbol. Same radar behavior before T/O. All my tests were from hot starts though, if that makes any difference. I also pressed NWS button numerous times with WonW, same. Next, I tried jamming bandit. Going head on against a Flanker with jamming pods. He turned them on fairly close and his ST jumped into a AOT dugout. I pressed SIL and the radar behaved similar to previous tests. All contacts turned D/L only, AOT disappeared. I remember providing a track a while back showing the issue with radar on the ground creating a track when NSW button was pressed. Not anymore though.

Sounds like a good crutch to follow for land based ops, not only in good weather. Hey, I use FPAS on every hop... selecting the last blank wpt as a home plate.

Well, it does seem like some sort of side lobes noise is simulated. What is probably not entirely simulated how Hornet's radar deals with it. I wish I knew... I did some testing and it looks like in the current OB, we can see a gradual decrease in detection range, starting at around 5000 ft. above ground (my tests were done over water). I also tested at 4k, 3k, 2k, and 1k ft., intercepting the same target (F15E), hot aspect, flying at different altitudes. Using HPRF or 4bar/60deg INTL PRFs made no difference for these aspects. With target at 33k ft. hot, I could detect him at 43nm, from ownship altitude of 10k, 6k, and down to 5k ft., looking up. From 4k ft. looking up at the same target at 33k, I could pick him up at 35nm. From 3k ft. ~ at 29nm. From 2k ft. - at 22nm. From 1k ft. ~ at 15nm. Surprisingly, when coaltitude, hot at 200 ft. , I could see him at 18nm. Look down detection ranges at altitudes within the side lobes noise (5k ft. and down) were not surprising. Similarly from high altitudes. Just one example: From 33k ft. looking down at same target, hot at 200 ft. ~ detected at 31nm. Coaltitude, hot at 33k ft. ~ at 46 nm.