Muchocracker

There is a known bug related to the location of the diamond. But the ASL itself can be offset from the target position by the mission computer for wing compensation. Check if you have wind in your miz

...same reason anyone calls anyone else "bro"?

Chief. I am not an ED employee. Completely irrelevant

It's been reported in the past but i guess it needs to get bumped. This behavior is correct for older OFP's for the hornet. But ours is suppose to be much later(17-19C i dont remember which one). Should always show BRA and A/A WYPT to the cursor regardless of an L&S existing.

it was not noted as being fixed.

Make reports in the respective module forums.

Again, it's going to depend. If you're trying to track that mig-29 over 50-60 miles the probability of detection is going to start to degrade enough that tracks will start dropping into memory. And gets worse with range. That's going to be a bulk of what people are going to see. But there are other issues surrounding that.

This doesn't really say anything in one direction or the other without added context. What is the range of the target, what PRF setting are you in, what is the scan volume setting, are you trying to get a track toward the edge of the gimble limit or not (there is an issue related to this which is known). There are things that are properly modelled that will effect your track quality and some issues that are causing it to be uneccesarily unstable with the current state of the hornet radar.

It's not really a matter of "opinion". It's a matter of how the real jet works. The SCS depress has many missing functions across the different systems and master modes but i don't know if there is here for this case. If you have material in public documentation that proves this then you should send that information to ED.

oh, just a typo. Fixed

It's suppose to be from 5m-25m burst heights selectable from sources but it isn't. Idk why ED did it that way.

M904E4 - mechanical nose fuse with safe separation arming delay and impact function delay settings. M905 - direction reflection of the 904 but is a tail fuse FMU-139 - electromechanical tail fuse with arming and function delay. Can be electronically armed in the jet as an instantanious detonation fuse, or use the function delay settings on the faceplate All 3 of theses are ground crew set and cannot be changed in cockpit minus the caveat with the 139 Mk-339 mod 1 - mechanical time clock dispenser fuse that functions the dispenser based on time from release of the weapon. PRI and OPT are 2 different set of function timings FMU-140 - Radar altimeter proximity dispener fuse that functions on AGL. Vt1 uses the rad-alt. Vt2 uses a backup time based function. Only accesible on the CBU-99 Both of these fuses are ground crew set. You can change with option to use in cockpit. But you cannot change the timings. FMU-143 - electromechanical hard target tail fuse. Used for bunker penetration with a higher 75G impact force activation and (should) have a fixed 60ms function delay. FMU-152 - Joint Programmable Fuse. This the only attachable fuse that is fully in cockpit programmable. But only with JDAM's. JPF page is accessd under JDAM DSPLY --> Mission --> JPF. Has arming and function delay settings. Will use the faceplate settings as default if unmodified. DSU-33 - AGL airburst nose fuse for the mk-80 series warheads. Fixed 20m burst height. This about as condensed of an explanation as i can make it. There are a ton of nuances and caveats but this will get you started

The carrier atc ai is basically irrelevant as it's the same lines that it's always used since the release of supercarrier. It has zero impact on the function of ACLS. There is no mode switching. It's all based on the ACLS, which acquires and locks on at 6 miles and will indicate "ACL RDY MODE 1 on the link 4 page. AFTER the lockon is when you engage coupled autopilot and it will go into P/R mode. If you're using the coupled heading mode on the approach before ACLS lockon you have to disengage CPL and rengage it for it switch to P/R. Reproduce it and post the track here in the thread. I cannot do much diagnosing otherwise.

Use the way's mod forum thread. This forum is for F-18 module bugs

the settings on the fusing can be different. The fuses themselves cannot be different

it's not only this thread. And yes, it is the performance of the seeker and missing processing techniques in relation to its MPRF waveform and tracking targets with low radial velocity in high clutter enviornments (which there are plenty of ways to mitigate this problem). it has nothing to do with the more kinematically efficient control gains.

Plenty. This topic has been covered many times

Does not address the core problem of the seeker modelling. This should be focus'd on rather tan trying to find ways to work around it.

Both the mk-20 and the cbu-99 have the mk339 mod 1 mechanical time fuse by default. If you want the radar altimeter fuse load the FMU-140 on your dispensers. This is correct as is.

This issue has already been fixed chief.

It's bombs of the same type. All gbu38's on the jet have to use the same fuses, all gbu31v2's have to use the same fuses. You cannot have 2 gbu12's with one having an m905 and another having an fmu139. The way that part of the question was phrased was you were looking for the JPF page to manually change fuse settings

You caused an MC-LOAD fault condition by having another of the exact same bomb on the jet with a different fuse type configuration. That is why the SMS fuse options were missing and the bombs were X'd out. You would have also seen a crossed out "LOAD" in the advisory section at the bottom of the left DDI. This is also not where you enter the JPF page anyway. That is done by going into JDAM DSPLY --> Mission --> JPF at the very bottom left.

No, it means in normal operation you shouldn't really have to touch the scan centering. Because if we had full MSI we can designate any ranked trackfile (from any source, including SURV tracks) as the L&S and then TWS Auto centers on whatever you selected.

Also not having automatic scan centering but more or less. Correct. We just don't have it yet.

you and me both