maxTRX

Before this thing slips into oblivion... Does anyone know how to prevent blanking of D/L contacts donors/AWACS when they creep over the HUD?

LACQ, HACQ... these are HMD modes. When I put sensor priority to HMD I want it to stay there. It's not just about a visual distance. There's is a lot more to it especially in D/L environment. Now... I have no idea what got implemented in what year, etc. One thing I know 'I would want' is smooth and fluid cueing... No gaps or jumpy transitions. If I wanted to go back to HUD, there's 'undesignate' and if wanted to designate something again on HMD ... I'd press SCS, long, short. To sum it up: I would want smoothest , quickest way to acquire, lock and kill with minimal clutter/gaps. It's just me, so I'll put it to rest.

Actually, I think we have a bigger issue then just visual mess here. I tested the LACQ mode again and basically this mode is inactive not just outside of the HUD frame but also over entire HUD area (except a small band at the top of the HUD). This is a very useful mode and should work within the radar gimbal limits, including HUD area. When I glanced a radar page I could see the scan line frozen when moving my HMD cross anywhere over the HUD. This shouldn't be the case. It makes no sense. I'll make a bug report when I have a chance.

and last but not least, the zone around the HUD that prevents LACQ (and possibly other ACM modes) to see and acquire anything. The radar certainly doesn't have any 'gaps' in this area.

As expected I was on the wrong track . First, it was happening to missile #1, not 4. Initially I was suspecting VR effecting memory, after multiple flights w/o restarting DCS. Finally, I noticed that this was happening when I engaged A/P BARO hold and on top of that, FP hold (or whatever it's called) by pressing A/P 'ON' button. I wanted to stabilize the flight path before releasing the missiles in a slow sequence. If I didn't engage A/P and countered the asymmetric load effects with the stick... all missiles released and flew correct altitude profiles. I wouldn't bet 100% on this theory but it sort of looks like there's something to it. Here's a track:Harpoon test4.trk and a vid:

I've come across some weird behavior of the last Harpoon in a 4 missile launch sequence. There are no issues if I start the mission after the fresh start of DCS (actually I did the reboot also). When I try to fly the same mission again, without restarting DCS (and possibly rebooting), I always see missile #4 flying up to over 40k feet, leveling off then diving on the target... after overflying it and hitting it dead on. All 4 missiles were set to BOL with HTPT, LOW flight profile and SKIM terminal phase. In all cases, all missiles followed the programmed route. Weird. Anyone else seen this? Edit: I'll post the tracks and vids tomorrow.

I use the WH and this mini track ball is pure crap. I use it also for TDC depress, so... the dead zone has to be enormous. Currently I have it set to 17 . The 'realistic' setting is unchecked. Holding this tiny track ball and slewing is next to impossible. I would probably have to use some toggle switch to flip it to 'depress' and then use a track ball to slew. Yes, there is someone out there making replacement TDC's... maybe I can put my name on a waiting list. Heck, I'm not even sure if the guy is still cranking them up. The rest of the settings. Both axes: Saturation X - 100, Sat. Y - 50, Curv. -15 (joy_Y inverted) You know how this works. You get in a situation where these settings are too sluggish and... here we go again. For now I'll keep it. It's not very fast on ATTK page but it's sufficient for me.

I tested SLAM-ER in the previous OB build. I got the same results when launching directly at targets. When I used turn points, the missiles flew at 5k in low profile, 15k at medium until their last turn point before target then they descended at a very shallow angle to 200 ft. I haven't tried high profile.

Same here. I can switch between AUTO and CCIP without loosing a designation.

I hate to be positive but the HUD and HMD designations seem to work very well, at least in my test. I reconfigured my WH TDC mini track ball... dumbed it down quite a bit and it's really manageable on the HUD and HMD. I think it is still acceptable on ATTK page. I was surprised to see the IMAV snapping to HUD designations accurately every time. Well, it was all within fairly short range. On top of that... everything looks better at sunset

I can't replicate it on my rig (latest OB). Starting my mission in the air. In NAV mode, I could not designate any point on the ground using HUD or HMD. I could definitely designate a point with WPDSG, radar or FLIR. Regardless whether I try it before or after A/G master mode.

Another method that would be very intuitive and 'clear' is to blank the HUD from displaying weapons envelopes and TD box(s) as soon as the priority goes to HMD. This would give you a smooth and solid display of important data on HMD regardless of where you're pointing your head. When pressing undesignate or switching priority to anything else the HUD would take it back.

I see only 1 TD box... anyways, what do you think about the 'dead zone' I described in my vid?

To me it would appear that it's a motion blur of TD box moving across the HUD FOV. There is no duplicate data displayed anywhere. There are various ways of making HMD data interface with HUD in different jets... All of the one I've seen make sense. Our current implementation doesn't.

If I could add one more little quirk to this... When I locked a moving target with radar and switched to FLIR display everything looked good with radar in the driver seat until I switched priority to FLIR with SCS. The FLIR immediately let go of the radar track and I had to slew it manually following the targets. But, on the HUD I could still see the RDR as a tracking sensor. When I switched back to radar display... the radar wasn't tracking the targets either.

I know, there's always a band aid... I'm going to try again to get my point across: It is not correct as is. There are 2 major issues that I can see right off the bat: 1. HUD blanking acts as an ON/OFF switch triggered by HMD's center cross approaching the HUD frame, side to side. From the top, it blanks when the cross hits 3 deg. above the combiner glass. It should be a smooth blanking starting when the HMD's FOV edge hits the HUD frame. Issue #2: Dead zone for ACM modes acquisition around the HUD frame. I tested this using LACQ mode. LACQ circle doesn't show up until the HMD cross is about 8 deg. (?) from the HUD's frame. That's about where the HMD's FOV edge is... what the heck? This video shows these 2 problems.

+1

I put the HMD through the wringer today and it seems like it's working a lot better now compared to a few months ago. It could be number of things that you might be having an issue with. Give some more info or post a vid. Here's some testing I did with tgt. acquisition via HMD. https://youtu.be/F2q_RxVAlc4

This also happens with A/G designation. As I was lining up on the target marked with solid diamond on the HUD, the HMD dashed diamond was hovering not far above. It is very distracting.

First, is AGR power supposed to be routed via main radar power knob? It seems like the AGR mode is powered up non-stop, regardless of the position of radar power switch. Turning EMCON on or placing the radar on SIL has no effect on AGR either. Another Q: what is the purpose of forcing AGR (SCS up)? Currently, AGR is active automatically as soon as the nose dips to 7 deg. below horizon no matter what... even with the radar knob set to OFF. I imagine this is still incomplete? Well, the EMCON part also needs work.

TBH, I'm not quite sure what changed since then but currently I'm able to whack the target in AUTO or CCIP regardless of target altitude, as long as I'm in a dive (I only tried between 15 and 20 deg. dive at M .8 ) Level deliveries in auto are off, mostly short and left (3 out of 4) I used 1 MK83 on station 5 (center) with ATFLIR on a cheek. I'm gonna do some more tests today with HMD target acquisition and FLIR. So far I tried to set up a target at 10k feet and lock on it with HMD and refine with FLIR. It looked good for a while but then I started seeing discrepancies in altitude after only 10 min of flying ( lots of turning and high G though) The mission was set for 1985. I haven't been very successful with INS updates. I'll play with it some more but form what IvanK and others are saying... it won't work too well. Here's a short vid from the dive deliveries. (1985 mission - before alignment degraded). No wind. https://youtu.be/3GQBeAKabt4

OK, thanks. Now that I thought about it... It creates no problems either way, since no displays are changed when PBLK condition kicks in and A/A mode is not effected in any way.

Well, Coriolis shouldn't be a factor from low alt... then again. Nah, ED doesn't even simulate the earth curvature or rotation

I tested the Litening pod today on the latest OB, at night using both MavF and MavE, on static and moving targets. The FLIR was rock steady. The MavF was a different story but... there is a method to every madness. I used JTACs for lasing static targets (2 tanks) and LTD/R for movers using MavE. I also used JTACs with MavF on statics, punching in 6 digit grid given to me. I also had 10 digit grid on the same location pre-programmed as one of my waypoints, just to verify how much the JTAC's directions varied. The altitude given by JTAC was 120 feet higher and the grid within 50 feet. Close enough to get the FLIR on it and refine. The only time I've seen the FLIR drifting (in the last few months) when I designated the target via HMD reticle, watching the FLIR on RDDI slowly drifting away from the designated target. This was an acknowledged bug and I think still is. Post a vid if you can. Here are my tests if you feel like watching... kinda boring but it shows Litening pod performing very well. https://youtu.be/nJm4SFx7i34 https://youtu.be/jbUsw0-IvlQ

Only TWS and L&S has to be designated. I tried to see if there was any difference in the way the contacts were separated when using EXP versus SCAN RAID... didn't see that much as far as spacing between the contacts. BTW, just watched Wags' vid on new RAID modes. Looks like couple of things will change.