TEOMOOSE

I dont see any issues with it, all the DED pages are shown. Make sure that your Data Entry Display brightness control knob is turned up (clockwise).

its a bug. When you press TMS up while FCR is the soi, it should slew the tgp to it. Work around is to cycle TMS right.

Currently unable to share SPI over network when using the targeting pod. Only steerpoints. Work around is to create markpoints which can be shared. TGP is set to point track mode to track target, HSD is the SOI, COMM-in long press. To my understanding reading the manual you should be able to that as described below. When the HSD is the SOI: - If a ground threat is boxed, the location of the boxed point is transmitted. - If no A-G threat is boxed, the location of the System Point of Interest (SPI) is transmitted if a sensor (FCR or TGP) is tracking the SPI; otherwise, the current steerpoint location is transmitted - When the HSD is not the SOI, the SPI location is transmitted if a sensor is tracking the SPI; otherwise, the current steerpoint location is transmitted

try this too

you can sort of see it from here how the bomb guide itself by going up and down in its midcourse flight

I hope this helps. What i have learned from that document: Guidance is provided by laser energy reflected from the target The weapon can be delivered in high/low altitude, level/dive/loft Four delivery options modes can be selected by setting the mode switch (on the side of the Guidance Control Unit (GCU)) prior to aircraft takeoff The bomb has three phases: Initialization, Midcourse, and Terminal Guidance. Initialization: During Initialization phase, there is an approximate two-second wait period to permit safe separation distance of the weapon from the aircraft. The control system is then activated. The GCU determines the mode selection and examines altitude data from the barometer within the GCU. From this available information, an optimum midcourse flight trajectory is determined. Midcourse: The midcourse flight selection is based upon the conditions measured during the Initialization phase. The midcourse flight profile and seeker scan functions are optimized to provide the best possible probability for acquiring the target, while maintaining the maximum energy for penetration. The midcourse phase is maintained until the target is acquired. Terminal Guidance: After the weapon acquires the target, it enters the Terminal Guidance phase of flight. During this phase the weapon trajectory is optimized to provide the best possible penetration of the target, based upon the target conditions determined by the GCU during the Initialization phase of flight.

Here is a pdf that goes in to some details, very informative. From page 9. https://www.globalsecurity.org/military/library/policy/navy/ntsp/gbu-24-a_2001.pdf

If, for any reason, fuel is not transferring or is transferring at less than normal rate, the receiver pilot will disconnect and monitor the aerial refueling status indicator. The bottom lamp (DISC) lights amber when a disconnect has been accomplished. The system will automatically reset to ready and the top lamp (RDY) relights blue after a 3-second delay. A second contact may then be accomplished. If this does not resolve the problem, the pilot may then disconnect, confirm disconnect with the boom operator, and recycle the system by closing and opening the slipway door using the AIR REFUEL switch. "T.O. GR1F-16CJ-1" ------------------------------- During normal after-start checks, check the air refueling system. Move the air refuel switch to the OPEN position and check the air refuel status lights for a blue RDY light on and the DISC light off. In a D-model, depress the NWS/AR DISC on the side stick and check that the amber DISC light is on. Three seconds later, the RDY light should come back on and the DISC light should go out. Move the air refuel switch to CLOSE and check that the RDY light extinguishes. The crew chief will confirm operation of the AR door and slipway lights. CAUTION: On the ground, depressing the AR/NWS button cycles the NWS. After closing the air refueling switch, check NWS light on prior to taxiing. "MULTI-COMMAND HANDBOOK 11-F16" "F-16 COMBAT AIRCRAFT FUNDAMENTALS"

It would be nice to be able change the laser codes on the bomb itself which does not require you to shut down, this is how its done in irl. Get the jet starup and ready, taxi to the rearming area "zone" set laser code and rearm.

The input values are determined by the amount of force acting on the stick, rather than the deflection angle and distance like on most other jets. Lowering saturation x, and adding negative curvature can simulate that, also this fssb-r3-lighting.

as the title suggest, the rws is not working properly. Cold aspect targets are completely invisible even at closer ranges, and its impossible to detect hot aspect targets outside of 30 NM. Even inside 30 NM, its very inconsistent and drops radar contacts on a Hot aspect aircraft. Sometimes have to get as close as 15 NM to get a lock. Im including a track file. The mission is running 4 aircraft(MIg29s, J-11A, Jf-17, Su-33) flying cold aspect, at various speeds and altitudes, and 4 aircraft flying hot aspect. (MIg29s, J-11A, Jf-17, Su-33) RWS and its sub modes should be the most powerful and reliable in Dcs F-16, and the second would be TWS which is using less energy and easy to notch it, but you can track and target multiple aircraft at once. fcr_rws_bad.trk

it dosen`t.

Becasue the TGP and the harm dosent communicate with each other. Thats the HTS - HArm Targeting Sensor pod job to communicate with the harm missile and that is why its able hand off target to it.

Looking at your video again, confirms what i have just said. The harm need a SAVED coordinate to fly to, without it, no spi, and no TD Box - target designator box.

Hows the AG radar relevant in this conversation, i used that as an example to your question, saying, if you would use other ammunitions like bombs than you would see the crosshair because you are in A, CCRP, B, DTOS, either way you have the target Designator Box on the HUD which correlates to the tgp, and that gives the targeting solutions. When you using the HARm with the HTS pod, and you did not hand off a target to your harm to target, than it has no sensor point of interest to give a targeting solutions which you would see on the hud, like min and mx lofting cues etc.

When you use the HTS and you do not have a sam designated or handed off to the harm, means it dosent have a SPI, sensor point of interest.

Because your sensor point of interest is steerpoint 01, and the HTS is defaults to EOM, which needs a steerpoint to navigate to. Therefore, you may target sams, relying the HTS only, or use HTS, and fine tune it with the tgp. When you hav tgp over the target, create a TGP markpoint, from that point forward you no longer need to use the HTS because now you the markpoint as the SPI.

It does. - Search, - track, - system, and - bug. Now we have to understand a few things here. In RWS we have two ways of targeting, #1: Situational Awareness Mode (SAM) and, #2: Single Target Track (STT). SAM mode allows you to BUG and track one or two aircraft simultaneously while maintaining a RWS scan, this is called Two Target SAM mode, or TTS. STT is obviously is a Single Target Track, which you could do if you want to sort a single target, or wanna increase your PK, but you will loose sa on the FCR. RWS and its sub modes should be the most powerful and reliable in Dcs F-16, and 2nd TWS which is using less energy and easy to notch, but you can track and target multiple aircraft at once.

Because your sensor point of interest is steerpoint 01, and HTS defaults to EOM, which is using a predefined location in other words your selected, steerpoint. But when you designated a sam on the HAD page, it will make that your SPI, and it will slew the tgp to that point where it think it is. Than the crosshair should move as well on the HSD. TGP markpoints gonna be your best friend here. When you the see sam site, thru tgp, go point track, icp7, tms up etc etc. Make that your spi, handoff sam to harm and magnum. - if you would have some other types, like bombs selected it will work as you have described it, including the ag radar.

it sure does create track files, and 4 of them actually. Same as TWS. Try using the fcr with the D/L filtered out, or have no awacs on the mission, you will see that the symbologies are the same.

I recall F16s defaults to zulu, which you can convert to local times.

Positioning the PITCH switch to ALT HOLD enables the FLCS to use CADC information to generate commands to the horizontal tails which result in the aircraft maintaining a constant altitude. The FLCS limits the pitch command to +0.5g to +2g. Engagement of altitude hold at rates of climb or dive less than 2000 fpm selects an altitude within the pitch command g limits. Engagement above rates of 2000 fpm causes no unsafe maneuvers; however, the engaged altitude may not be captured. Control accuracy of +-100 feet is provided to 40,000 feet pressure altitude for normal cruise conditions. The altitude reference may be changed by depressing the paddle switch, changing altitude, and releasing the paddle switch. ALT HOLD in the transonic region may be erratic. T.O. GR1F-16CJ-1

Another overhead landing, the right way d:-)

I dont know where to start, so i made a few test. The mission is simple: A single bandit flying high ~50,000 ft @ Mach 1.0 in a J-11 set to ACE difficulty. The parameters for the AI were: - use radar for attacking only, - use ECM always, - missile attack range random between max and no escape zone. Fully loaded with ET`s and ER`s, ecm pods. On the other hand me, in a single F-16 with 6 amraams only, no pods, no fuel tanks. Starting at low ~ 6000 ft. Made two flights to test the radar in TWS to see what kind of behavior i get out of the radar. The aircrafts were set 50nmi apart from each other, mind you the altitude difference. Fly straight, in a fast climb and play with the radar elevation. Had no problem picking up the jamming contact, even was able ""bug it"" but not bug it. Dont know how to explain it, where it just tracking it but waiting more data ?? - Anyways, i see that the FCR is showing contact that is jamming and has no ranging, and no ??altitude information?? but the in the HSD it shows the range exactly at 50 nmi. Between each test, the radar was able burn thru the jamming signal and was able to fire ranging somewhere between 29-25 nmi. I didnt maneuver by the book after the fox3, because this is just testing. I didnt go on full details, so you might see more things that arent working as advertised, so feel free to make comments on that to keep this rolling forward to help the devs out. Cheers! Im including 2 video links with the corresponding trackfiles, including tacview. PS: I forgot to save the Dcs track files. I hope this is enough data. LO_HI_ECM_TWS_2.zip.acmi LO_HI_ECM_TWS.txt.acmi

it supposed to slew the tgp, when you designate anything on the ag radar, but currently it doesnt, but if you cycle thru tgt> oa1>oa2 and back to tgt by pressing tms right short, it will put the tgp to that target point.