ramjet77

I think apart from the No Rad mode locking up issue and inability to cancel a lock without exiting DGFT as Tom says above I think the bore sight bug is indeed linked to HMCS. I too started having errors after using it for a while and switching it off again. I’m certain it is affecting Bore lock up in some way but cannot produce exact steps to say what it is. Definitely not working without a bug or two in there somewhere

BIGNEWY Here is the first issue I am experiencing. As soon as I move DGFT switch into what should be a No Rad mode I straight away am getting a radar lock. I cannot unlock the target only cancel DGFT mode and return to Nav. Until I can get passed this I cannot now even try Boresight sub mode as target is already locked up. Track file attached. No Rad lock.trk

I cannot figure out what is going on. I have run a repair and clean and am up to date with OB. I have just flown a mission I have been using for ages to practice the use of DGFT and ACM. Firstly as soon as I switched to DGFT the bandit infront locked up in what should be no Rad mode. Next I found he locked up in all sub modes without me doing anything. The last bandit I trailed would not lock up in Bore as described in this bug..... no amount of TMS forward or releasing would get him locked up. For some reason I am getting very inconsistent variations whilst using DGFT. During the same encounter even going back to nav by centering the switch would not clear the DGFT sub mode. I will try again tomorrow and see if I can post a track file.

Confusing at the moment, I’m finding the same thing. Sometimes I can get SP and a CCRP cue to coincide but other times CCRP cue remains fixed on CZ despite using SP......

DGFT ACM Bore sight not getting radar lock DGFT ACM Bore submode selected by pressing TMS up and placing Bore cross over bandit but no radar lock. Using HUD or Vertical scan sub modes on same target both give radar lock as supposed to.

Ok. According to the F16 guides I’m reading after selecting Bore the first target within 20 nm within the scan area cross below gun sight should automatically lock. This is not happening. Last time I used the feature it was working but that was a while ago possibly two updates back.

Definitely different behavior than previous versions so unless intended I think these features are bugged. Will continue to experiment.

DGFT ACM Bore submode selected by pressing TMS up and placing Bore cross over bandit but no radar lock. Using HUD or Vertical scan sub modes on same target both give radar lock as supposed to. Also could not get a radar lock using Bore with HMCS. Could someone verify and then I’ll know if it’s the sim or me please.

Great guide as always, thanks

I just hope they will fix up what’s already there before adding more broken or buggy features. Do not mind waiting for stuff as long as the implemented stuff works correctly ie steerpoints with TGP......

If you cold start make sure the IFF switch is set to Norm. It is located on the Aux Comm panel on the aft left console. Do you have any friendly flights such as an AWACS in your mission? They designate contacts for you to see. You said you have the MIDS on. Double check the MIDS switch on the Avionics Power panel aft right just in case?

Agree, TGP drag causes the aircraft to pull right on takeoff and the NWS sensitivity is very high usually resulting in over correction. With it off the rudder lacks any authority until higher airspeed so you continue to drift right. It’s all a fine balancing act, try using a rudder curve to limit the sensitivity for now.

Just to confirm is the drone the default DCS one and you have it lazing targets via the comms menu? Do you see pod indicator slewing once uncaged showing the LSS is active?

Habu_69 I think your post 2 above sums this whole issue with TGP and Mav Fs perfectly. If this is how the real system actually operates I’m surprised any pilot would want to use that combination at all. I tried and tried but have now given up so hopefully as you say it’s WIP.

Hey Hinkel, firstly I’m no expert, just enjoy the F16 and spent a lot of time in it recently. Just to clarify are you getting a picture on the TGP after a ground started mission or not? The cheek mount has to be powered where the TGP is and by default on a ground start the switch is off. Maybe you know this but I’ve got to start with the basics so I can figure out things you may/may not be doing?

Awesome, glad you got it working. Now experiment with different speeds and altitudes and see for yourself what’s possible.

I use Track IR to look around and use the small throttle slider for external zoom.

The RDR Cursor/Enable button moves D, U, L, R and has a push in (depress) function. So I use the Coolie hat to slew and the slew control next to it only as a depress control, not for any slewing. The TMS, DMS are on the Joystick as per real aircraft. I use the thumb HAT on the throttle as the uncage button by pressing it and also for ANT ELEV up/down. Not much else needed right now as the warthog stick is practically the same as the F16 and is bound as the real A/C. All I can suggest is you try again because it definitely works and I can hit the target every time and never have to set laser codes as they are already there by default. If you still cannot get it working maybe you could post a video showing us how you setup and drop the weapon.

Hi, I use the Coolie hat on the throttle front next to the slew control to slew as my slew control itself is a bit worn and sensitive nowadays. I use the slew control push though as my RDR Cursor/Enable depress. You are correct that the F16 does not need to designate the target, so slew cursor over target and then I usually TMS up to go point track but that is not a must, Area track is fine on non moving objects. Try bombing from 15-20,000 ft at 400 kts + and see if it makes a difference. Only laze about 10-12 seconds prior to impact ( you will have to best guess that until TTI comes) if you lase immediately after release the bomb may run out of energy on a shallow flight path. From 20,000 it’s about 40 seconds. Once the bomb comes off the rail after a few seconds start a shallow angle of bank turn to the right ( use autopilot alt hold helps) Then after about 10 seconds start holding the trigger ( Flashing L) and hopefully that will get you a direct hit. As you pass over the target if the cross hair has drifted slightly due to slant error from where you first set it then just gentle move it back to target. Codes are all set by default currently to 1688 so nothing needed there. Sounds like you might just have been too low and slow and the bomb might have been running out of energy. But I’m no expert so just a guess. Edit:Just to add I’m referencing the open beta build.

Thanks chaps, yes David OC my HOTAS is correctly bound and working correctly with Aim 9s so what Svend_Dellepude said makes sense that it is simply not implemented yet then. Yes I guess I could bind an OSB like you say, that would be a temp workaround. Thanks

Ok cool, did not know you had reported that, glad it’s known and fixable.

You can cycle Slave/Bore by pressing OSB on the MFD but not by the HOTAS switch which according to the manual you should be able to do. Still learning AA so wanting to know if it should /does work or whether I’m doing something wrong?

Could someone please clarify if the the Aim 120 Slave/Bore can be cycled on the HOTAS using the Cursor/Enable as written in the F16 EA guide, I find it works with the Aim 9 but not the Aim 120? From manual: Cursor/Enable (CURSOR/ENABLE) Control. This control is used for slewing of the fire control radar cursor or TGP/weapon video. Depressing the control changes the BORE/SLAVE option for the AIM-9 and AIM-120 I’m aware you need to press and hold in DGFT mode for Aim 9 and have tried both holding and single clicks in AA master for Aim 120 but no go. Thanks

hein22 ok thanks I will try that, the whole reason I mentioned Maverick Fs was because occasionally the seeker sits just to the side of the target or doesn’t lock and a slight slew of the missile head usually would generate a lock like if not using a TGP at all. But with TGP the missle just does not slew the same way. Sorry for somewhat changing your thread topic but I posted here as pressing undesignate bore sights the TGP which was the thread topic. The Mav F was an added complication I found which I thought holy depended on that undesignate to work. So I’ll fly later today and just try slewing TGP not Maverick at all. Thanks