JSpidey

In DCS after you fire your last missile, BACK SCATTER inhibit message is displayed and the missile constraint box disappears which from my observations is incorrect. Image from 2009 Apache TADS as evidence and DCS TADS footage showing the bug.

That's correct. The circles stay concentric since a few updates ago. They all move together according to where your head is.

Looks good to me. When you're firing are you keeping the aircraft stable? Also what's the range to target? For instance if you're sighted in at 800m and your target is at 100m your rounds will impact behind it. Likewise if you're target is 1.5-2K's out your rounds will be impacting short. So it's okay to be a few meters off because chances are your target is not at 800m at each engagement. You could try switching to auto range and see if your accuracy improves?

If you're using one eye or the other, you need to put the HDU LOS reticle in the center of the BRU and make sure the circles and dot are also aligned. I've done this plenty of times in VR and never had a problem. If you're using both eyes then yes some issues can arise for obvious reasons. In your case just make sure the reticle is also centered with the boresight unit and you should be fine.

Are you also making sure the HDU's LOS reticle is centered inside the BRU?

I get the exact same behavior in VR when turning the TADS on or turning on the TADS repeater in the back seat.

How did you come to the conclusion that you have an upwards and right alignment error? Also did you center the IHADSS LOS reticle inside the BRU before accepting the boresight?

The IAT gates originate at the TADS LOS reticle and move out in the format to capture a selected object with FLIR or DTV imagery. In the sim they just appear around the target when the IAT switch is pressed. Also Pressing and holding the switch in the IAT position for longer than 0.6 seconds will initiate manual sizing control of the tracking gates as well as adjusting the aim point within the gates (which is modeled) however the gates originating at the TADS LOS and manual sizing is not.

Thank you for the help! I basically put down a shovel at each IED and made a trigger so when the shovel gets destroyed it will explode the IED. It works pretty good.

Thank you, also I'm not able to detonate the IED's with any of the munitions I've threw at it, is there a way I can have them detonate when hit with a missile, 30mm etc?

Hey guys, I have the Low Level Hell Counter Insurgency mod which comes with some IED static objects, I was wondering how I could set up a trigger to make the IED explode when someone runs over it or if it gets shot (30mm, hellfire etc). Any suggestions would be greatly appreciative, thanks.

@BIGNEWYI posted pictures for evidence. I know this would be very low on the list of bugs but I just wanted to make sure you were aware of it. Hopefully someone with true hands on experience can chime in and verify this as well...

I've added evidence, first picture was taken in 2009, second picture was 2003/2004.

Very small issue with "BACKSCATTER" inhibit message. It should be spaced and shown as "BACK SCATTER". I've included 2 screenshots of the evidence.

Can confirm it's still happening on my end as well.

I'm on Windows 10 which is up to date, RTX 3080 with up to date drivers, I experience massive amounts of stuttering as soon as I turn the TADS on either in the front seat or the back seat. The main concern I have with the stat page is Obj, Trg, and CPU count start "spazzing" out as you can see in the video which makes me think is the root cause of these stutters, it won't happen unless I turn the TADS or TADS repeater on. The stutters are so "micro" it's hard to pick up on the monitor unless you have the headset on so it's hard to record it which is when I turned to the stat page and noticed those 3 values spazzing out and acting strange.

Hey guys, I've posted this once before in the past, now that the framerate and stat counter has got updated to a more readable state I figured I'd show you what's going on with my system when the TADS is turned on, this happens in the front and back seat, in the video I was showing what happens when you turn on the TADS from the VID page from the back. I hope someone who's knowledgeable in the stats section of the frame rate counter could take a look and see why this is happening. Take note of the Obj, Trg and also FrameTime and CPU usage. When the TADS is off, the Obj and Trg will remain at a constant number, when I turn the TADS on it will start flickering wildly which I'm guessing is not a good thing. Also notice the FrameTime jumps from 11/12 to 22/23 and CPU count will hold a constant 1.xxxxxx but as soon as I turn the TADS on it will then start jumping from 0.xxxxxx to 1.xxxxxx to 2.xxxxxx. I'm no expert but to me this is a sign of the issue I'm having with framerates dropping from 90 fps to 45 fps, it happens in succession each time I turn the TADS on/off and I've also experienced this with the Hornet's TGP as well.. hopefully someone can shed some light on this. Thank you

What's the distance of the target and what's your manual range set to. Some people have problems boresighting with IHADSS set to both eyes so that could also be causing an offset with boresighting.

Make sure when you're boresighting you're putting the LOS reticle inside the BRU as well as making the yellow circles concentric like so. Also remember that you don't have the benefits of the target state estimator in the pilot seat and you can't get a laser range to the target so you'll need to make sure your manual range is set appropriately

Not sure if other people experience the same issue, but when showing the George interface, TrackIR goes from zoom axis to forward/back axis when zoom axis is set. You can replicate it by removing the forward/back axis for TrackIR and setting the zoom view axis for TrackIR's Z axis, then engaging the George interface and moving your head forward and back.

I know it's been discussed before but I don't think it has been shown like this. In VR when turning the TADS on or the VID page in the back you get very annoying stuttering. When bringing up the performance tab in DCS, you can see how it goes wild when the TADS is on, then stabilizes when turning the TADS back off. I'm no expert but I don't think it should be doing this? I'm guessing this is why I get those constant stutters when enabling TADS or TADS on the VID page. (Not only does the FPS drop around 20 frames, but take a look at the Obj and Trg values on the second line compared to when it's off.) Thanks

You're welcome glad I could help!

I don't even need to do that for the PLT seat, for CPG only thing I need to do is move my head to the left a little, hit the VR recenter and I'm more centered in the seat, then boresight as per usual and I'm good.

Make sure you're binding them to the seat you're using (Pilot/CPG), check the category on the top left. Right now even if you're in the CPG seat, when you click on controls it defaults to pilot seat which can be confusing. First trigger detent means if you have a weapon inhibit message it will prevent you from firing. Second detent bypasses inhibits.

You can also save the view with a keybind I can't remember which one though. I'm sure it's on this thread somewhere, then you won't have to keep changing your view every time.