maxTRX

I've only used S3 tankers for about a year and I always have them flying in an orbit around the boat. Daytime, fairly routine (I've been doing this since... forever). At night, the tanker's position lights become visible at 0.1 nm and it's been like this... forever. I'm going to post my 're-occurring' request in the wish list, again.

@pixie I've seen this once or twice in the last 2 weeks. I couldn't figure out what caused it. Gear and flaps were down, VV started dropping, slowing past 150 kts, I touched the trim and the nose pulled 'cobra'. I've never seen this before June updates.

If your hardware and curves are OK and you have the wind from the right, initially at slow speed the jet will weathervane into the wind. Many people here on these forums claim the effect is a bit exaggerated (perhaps not the wind but the jet's interaction with the runway surface). As the speed builds up and the airflow effect is significant, the jet gradually becomes part of the airmass moving to the left and will start drifting to the left. Check your curves and deadzones first, as mentioned already.

Before I put this to rest, here's a sample of one of my desparate attempts to achieve clarity around the HUD by turning it of. The clarity was great but some vital missile info was missing w/o HUD so I won't be doing this too often. Well, it was fun. I was lucky the fight stayed BVR and I didn't need guns. Oh, the pitch ladder and VV were on LDDI.

Yep, from fairly close distance it is creeping all over the place. Every few seconds it regenerates and creeps away between 50 to 100 feet. I marked the vid to show this. From a distance, it worked well. If you watch the whole vid it shows contacts anywhere from 3 to 80nm and the DL is spot on. https://youtu.be/LJzovhEmwYA?t=162

No worries, simple is always the best... for pilots. Engineers can stare at their equations and try to make it simple for the pilots. I'm not new to concept of trimming, AOA and other things related to aviation and aviating... just thought Hornets were a bit 'special', . Well, back to simming, have to find me some more bugs...

Nice explanation. Just to confirm... is there any FCS pitchup capture (hands off the stick) that happens right after launch. Of course that could always be effected by pilot input which, if done too early might cause FCS to mitigate that input? I'm talking immediately after launch before good rate of climb established and gear/flaps go up. Also, after bolters, if say the pilot kept the stick in neutral, would the FCS initially kept the nose at the similar pitch? Or, with the jet lifting, does the FCS immediately goes to capturing and maintaining PA AOA? I think you already answered this, just trying to sort out 'stories' I've heard.

Well, in that case... I'm revising my tactical manuals immediately, lol. edit: I mean my own manuals

I think it's also worth mentioning that the radar is not working alone tackling all these problems. RWR, ECM, MC and DL (big one for friendly missiles) Same as with power distribution between radar emitter and SP jammer... I would think the real system is probably more 'user friendly'.

That's above my pay grade, I think it's a good start with what you said.

I know one thing... an engineering team that would program the radar (in RW), especially TWS to display A/A missiles like any other airborne contact and include them into 'pinky toggle' sequence, would have to answer to someone... Especially your own missiles.

I think I know what might have been causing the DL 'black outs' that lasted for more then 30 seconds sometimes, since this was my main concern. The E2 was orbiting at 26.5K feet (I couldn't find an option to setup a racetrack pattern). S3 was also orbiting, at a lot lower altitude though, 7k feet and laterally they were between 10 ~ 20 nm apart. I have to verify this but there is a chance the tanker flew into the blind zone on occasion. I'm not really sure if this was related to the OP's problem... it looked like it at first so I piled up on it, hehe.

Ok, I made a simple track and a vid to show where I was looking with my HMD (in case someone watches the track in VR) At the start of the vid I was approaching an E2 and the Link 16 update rate was sluggish but fairly 'accurate'. Next, I approached an S3 and things got really sluggish. It looks like the update process gets stuck occasionally. I wouldn't think E2 was the cause... I don't know. The vid starts at 3:44 (on S3) https://youtu.be/NXwyb0TUZf8?t=224 DL lag.trk

I was just watching both missiles from external view. Aim120's behavior looked solid. R77... not so solid:

Yes sir, that pilot sh!z is always there. When launching from the boat in DCS, the excessive pitch-up might not be that noticeable due to relatively heavy weight. As a matter of fact I always catch myself trying to nudge the stick up a smidgen before I see VV creeping up. I know, flying off the boat in a Hornet is 'hands off the stick' for a second or two, in RW. Boltering in DCS requires the aforementioned sh!z, at a much lighter weight. From what I understand, in RW the pitch CAS controls the initial the pitch-up to 12deg.(?) then preset AOA. (?) Also after a bolter, when any 2 wheels hit the deck, the pitch CAS resets to a similar pitch-up logic then AOA (?) I'd appreciate if you could shed some light on this.

@Harker Another quick question if I may. Currently, is there any way to filter out types of emitters on RWR? Switching between NORM, SEA, LAND or AIR. This little knob on EW panel doesn't seem to do anything. It changes the letter in the center of RWR and the filter type on EW display though. Am I missing something?

Wouldn't that be nice, not just for t&g's

For those who also fly Vipers and Tomcats: Does RWR update so painfully slow? Shouldn't the threat spikes rotate immediately and smoothly? If there's processing time required to show the threat position correctly, why not rotate first, then process and adjust the spike position. It would help with notching incoming missiles and other emitters quickly. Currently in the Hornet, when turning rapidly away from the threat say 90 deg. when leveling on a new heading, the spike is still on my nose for a second. I know that even in the older RWRs, things worked a bit faster.

I also ran into this. Started in the air, INS on IFA. Single player.

I've seen quite a few pics from various systems (except Hornet's) and don't remember seeing a mess as we currently have with this blanking scheme. Never seen a shimmering double TD box either. Well, it's not up to me. All I can do is run my mouth once in a while.

That's not an issue in a missile fight. The problem shows with the guns. You have no gun director or the funnel. So, we have to turn the HUD on. Another thing I noticed (well, actually I mentioned it before in another thread) was the transition from HACQ to bore as the HMD moves into HUD area. It just jumps and was causing a problem with acquiring a target in that area. If the HUD is off, there is no transition problem then again, there is no gun pipper... Oh well, I tried.

Just did a very quick test... unboxed 'BLKN' in HMD setup, turned the HUD off and HMD on... I am freaken good to go! Well, let me do a full test first, hehe.

You know what... I just thought about copying Fat Amy and turning the HUD off when HMD is on,

Now this would help a lot.

I'll take whatever ED throws at me and try to find some use for it . btw, I noticed Litening has TDC OBS... in case someone absolutely needed to switch TDC priority to the pod when in some of the ACM modes. Not at dogfight range but something like LACQ.