maxTRX

I don't know... I have the SatNav checked in the game settings now and the INS switch is always on IFA when starting hot or in the air. Now, things got even stranger on my last hop. No more discrepancy between HUD/JHMCS and the FLIR when the target is designated... at least not my last mission. I flew over the same map as before (Syria), in different area though. However I noticed something else: When I had my sensor priority on HUD or HMD, then designated the waypoint as target (WPTDSG) on HSI, The target diamond popped up in the air in the random spot. Repeated the process and the designation jumped to another random spot in the air. The WPT elevation was set correctly. I switched priority to FLIR and redesignated. The target diamond was in correct position. So... I put SOI back to HUD and redesignated the same waypoint again. This time no error. Switching to a different waypoint and running through this drill recreated the bug. I think the code is alive and all these bots that I decimated are hitting back at me, lol.

I'd better start looking at my logs and see what the heck is going on occasions. I only use ST DCS.exe, single play, loaded with 64g DDR5 (fixed page file set to 9216, never even bothered above that). I haven't had any crashes in years, even before my recent rig upgrades, until this MT thing showed up. I gave up on it for now. Memory was probably not the only thing leaking there, hehe. Currently ST is holding up OK for me, even in fairly long missions but... once in a while my Reverb G2 goes 'grey'. Nothing will fix it until the OS reboot. The game is still running on the pancake screen and the head tracking still works. There is some other strange behavior after quitting the game or rebooting my rig but I have to investigate more, could be just VR related.

I think the search start point in R/BL is measured from launch point. In BOL from the turn point if used. I flew the similar mission to the one OP posted with the turn point on the grid he provided. The target ship was another 20 nm from the turn point (90 deg turn) I launched Harpoons over Khasab with the search set to 53. Worked fine.

Slight correction: It was 'RAID' button I was pressing not Uncage. Somehow I had my older controls config file loaded instead of the new one, my bad. The issue in question still stands...

Sure thing, within radar's gimbal limits not just outside of HUD. In my vid you can see the solid box when I peeked over my shoulder. I think it's just another bug but if someone has some feed back from the devs or SME's... anyone?

I ran another quick test, this time w/o AWACS and Link16/Tacan powered down. It does look like some sort of extrapolation and it lasts a few seconds. This also happens in other A/A radar modes. From what I understand, the track should be dropped past radar gimbal limits but what do I know . Extrapolation in a turning fight can actually be counterproductive. If you get transfixed on the TD box instead of gluing your eyes to the bandit, especially when the bandit is blending with terrain, after few seconds the TD box WILL be way off then... good luck getting a tally again.

Nah... I don't think so. The jump around 1:40 was caused by me pressing 'cage/uncage' again. Actually, 'cage' button has a different function when the radar is in GACQ mode. Something to do with the funnel or sim mode... I think.

I stumbled on this by accident when testing the gun director mode. The first few seconds of the vid show the final part of that test.

It seemed strange to me. When I pressed cage/uncage button, the locked target snapped to the center of DDI and it stayed there during my turn with the bar scan moving toward and past the gimbals. The lock was never broken and I was able to make a 360 turn, coming back on target... COOL, lol. The JHCMS showed the arrow throughout the turn. I'll do some more testing later just to make sure it wasn't a one time glitch. The track was incorrect but I made a vid, might post it later. Anyone seen this? ST DCS.exe Edit: It was RAID/FLIR FOV button not Uncage (my old controls config file was active not the most recent :()

Well, I've just wrapped up a quick test and I have to say that the gun reticle is usable now. When I was outside of the gun range or the locked bandit flew past the radar's gimbals, I might have a question or 2 for SME's or other folks 'in the know' related to reticle position, etc. With the target in sight and approaching the gun's range, the reticle behavior did not cause any issues. It looked good from that point till the kill. I didn't notice any excessive jumping around. It seemed like it followed the same path the funnel would draw, + range. This test was done in ST DCS.exe and I have no Idea how the gun director behaves in MT currently. Now, I did notice something strange though related to pressing cage/uncage button with the target locked in HACQ mode and possibly other ACM modes. (excluding WACQ). I have to make a separate thread in Hornet's general forum. Perhaps someone might have an explanation for me.

Well, no changes there, more scissors. Cool. Someone needs to bring out some gung-ho, air combat trained GPT bots and let'm loose.

It's weird the way it works here. You can power up the Mav by boxing it on SMS and it slaves to the pod with no problem but if you want to cage/uncage again using HOTAS... no, you have to have master arm on...

You mean 1 bottle? lol 8 would probably be enough, if you gobbled up lots of water gradually throughout the the night but who does that. Coffee dehydrates as hell too. Now back to the sim... I only fly Hornet and never have issues with high G, before I know it the energy is gone and I'm just wallowing, spiraling down and... still kill the bots.

Or... may be, just may be DCS is simulating a warmup in the O'club a night before and a big pot of coffee in the morning?

Not that I know of. Programming WPT + ALT seems a bit awkward but it works. Foka jogged my memory. Now, I actually remember plugging the WPT first then ALT by repeatedly boxing and unboxing the 'STP' button in the past. Long time ago, enough to forget. Using WPTs for STPs is obviously the easiest way to program and accessing the data is no problem. The ALT is easy to remember. In my test today, I put 200ft for every STP hoping it was AGL and it worked out fine. I was actually impressed with the missile's autopilot. The missile didn't follow every bump or dip in the terrain and in case there was a big hill in front of it, it started climbing early enough to clear the hill. The climb/dive angle is fairly shallow so planning the last STP is pretty important.

Only ST DCS.exe

HT is off. With 13900k I didn't have to make that many changes in bios, just HT, mem to XMP and couple of other minor things. So... it looks like nobody else is seeing this. Is anyone still running ST DCS? How about MT? I stay away from MT for now until most glitches are fixed although performance wise it kicks butt on my rig, no stutter whatsoever. EDIT: I think you meant hyperthreading?

Like I said, the quality was showing .5 OK... still, the switch was in NAV with the GPS available (at least that's what I thought). This was something new so I had to investigate. Here's a vid (shot in VR) showing discrepancy between the HUD/HMD and the FLIR. The alignment should not be an issue here. FLIR was spot on every time. HUD and HMD were both off so I can't blame it on HMD alignment. Starting a mission in the air should have all 'alignments' done anyway. The vid was made yesterday before I changed the game setting to unrestricted SatNav. It doesn't make any difference, one way or the other.

I meant 3k ft ,of course. It flew above the trees just fine, not too many structures in its way though... except power lines. It went right through them.

Blue. Anyways, I set unrestrictive SatNav in game setup and now, when starting in the air, the INS switch is set to IFA. Before the SatNav setup change, I tried to do an IFA alignment using radar and following NATOPS... well, I gave up quick, lol. Besides, the quality was already showing .5 as soon as INS switch was moved from NAV to IFA, so... Now, back to the thread title. Even with perfect alignment, the designation drift still occurs, WPTDSG or HMD. Also, discrepancy between HUD/HMD and FLIR can be pretty significant on occasions.

Yea, I just looked it up. First, by starting the mission in the air I should be past all this stuff and ready to fight the bandits not INS (j/k) Now, if the devs want us to flip the INS switch to IFA in the air (GPS available, mission set in 2016) then it's going to be a pain. Speaking of the different IFA alignment options... I did notice the radar lookdown optimization angles LAND and SEA. CONT PVA for velocity updates was there too. I don't think this whole thing is complete yet but before I run my mouth any further, I need to jump in the sim and run the procedure by the book. Sometime tonight.

Another thing I noticed... When starting the missions in the air or hot on the ground, the INS switch is on NAV. When I flip it to IFA, a new item pops up on HSI: 'ALIN RDR' and alignment status numbers (.5 OK and the time below). I haven't referenced any manuals yet but I don't think it belongs there during normal flight or when GPS updates. Anyone? EDIT: I'm on Syrian map, using ST DCS

I see

This is actually worse then I thought. The old bugs are 'rotating' back from few months ago, like the one making the designated point on the ground drift off, not only in grid but also in altitude. In one situation the designation moved from ground level (1788ft) to 8500ft. (roughly my altitude) and few miles west. I could see it changing on FLIR, with WPTDSG still boxed. When I designate using JHMCS, the FLIR is usually a bit off, which is fine. I put priority on FLIR and correct and see my HMD diamond move 50 ~ 100m off (looking directly at it) FLIR is dead on. Seems like there is also a slight disconnect between HMD/HUD and FLIR. Now, I started these missions in the air, assuming the NAV alignment and GPS page are OK. The only check I do is NAV switch on IFA. I'll do some more tests with cold start later on.

GPS was good, my own mission, set for 2016. I only saw it once, will need to tinker with different setups before submitting a bug report. I was curious if anyone else has seen it.