desertowl

Hello, When HAD is SOI and HARM is the selected weapon, each time a threat is selected (TMS UP) in the HAD, the TGP jitters significantly, even if the same threat is selected and its position has not changed. Choosing a different weapon, such as GBU38 does not create this behavior - The TGP jumps to the HAD position and if the threat is re-selected, the TGP does not move. Please find attached track file that reproduces this issue. Best, Mk TGP Jump HARM HAD.trk

I reported it too, see last post in this thread:

Thank you very much for introducing this feature into the product! However, I did find a weird bug: in NAV mode, press MARK Select HMCS as SOI TMS up once to space stabilize the cue TMS Down to reset the cue to HMCS boresight Pressing TMS up again when looking at the rear hemisphere of the aircraft will not space stabilize the cue, it stays on the bore Pressing TMS up in the front hemisphere works as intended. Please see attached TRK that reproduces this behavior. Best, MK NAV Mark past front hemisphere bug.trk

A known issue,see here: Mk

When in "ACM Bore" and the FCR is slaved to the HMCS, upon approaching gimbal limits of the FCR, the Ellipse should start moving towards the edge of the HMCS display. upon reaching the edge of the display, an X should be displayed on the ellipse marking that it is outside gimbal boundaries. Is it intended to be incorporated into the sim? Best, Mk

I consulted an F16D pilot today regarding the issue, and he too acknowledged that HMCS mark points are available in both A-G and NAV through the HMCS. There are many reports here to support this behavior (some of which first hand), which at least warrants a second look. Being in transit with no weapons at all or in A-A role makes no sense to switch over to A-G in order to create a mark point, let alone the weird, half baked behavior we currently have. Best, MK

They allow you to shape the trajectory of the JSOW, so you can determine the azimuth and altitude from which it will approach the target. You can assign different parameters for each munition, creating simultaneous attack from several directions.

Since I was the one opening this thread, I was referring to creating markpoints in NAV mode with the HMCS. I was under the impression it should be working. In the sim right now the feature is almost fully implemented and it looks like there is a bug in which the markpoint cue moves to the HMCS and the markpoint is created, only the cue itself is invisible in the process. @Frederf, to my understanding supports this claim. Whether this feature will be fully implemented, completely disabled or left as-is, is up to the developers. Best, Mk

Hello, Don't know if it is a bug or not, but turning barrage mode on and then switching to SPJ modes 1/2, ECM keeps transmitting in barrage mode. see attached TRK for reference. Best, MK ECM Barrage SPJ.trk

When in Maverick VIS mode in the HMCS, after firing all mavericks, seeker symbology stays on the HMCS even after all mavericks were fired and switching to other weapon. See attached picture and TRK. Best, MK MAV_cue_ bug.trk

The issue is that even with an aircraft that does not have the pod, the stanby and active lights turns on. You won't be able to reach transmit though, without the pod.

"You could hold TMS up long in NAV mode to give commands to hmcs and it does what you saying but again that would be an incorrect way of using it". This is not how system design and human factors engineering works. Again, I would like the staff or someone with knowledge of how it works in the actual aircraft to comment on that weird behavior.

Teomoose, I've seen all the videos and read all threads, but it is irrelevant to my post. I am not asking about how to do it in A-G mode. I am pointing out a weird behavior of mark point creation in NAV Mode. As it is now, it seems that after TMS long the HMCS Mark cue leaves the FPM but is invisible in the HMCS - I would expect that either it would stay on the FPM or be seen in the HMCS. I wanted to inform the staff of this behavior and for them to acknowledge whether it is a bug or not. Best, Mk

I opened a post with the same issue in the bugs section (along with a.trk file). Best, Mk

Hello, The Standby and Active annotations lights up, even if ECM pod is not equipped onboard the A/C. If it is as IRL it is obviously not a bug, however, it sound weird that a system should report "Standby" and "Active" when not equipped. Best, MK

Hello, While in NAV mode, pressing MARK on the ICP and selecting HUD as SOI. Long TMS up moves the SPI to the HMCS, and when looking at a certain location and pressing TMS Up short twice, a mark point is created. However, in the entire process, the SPI reticle is not displayed outside the HUD boundaries, therefore ground stabilization and slew adjustments are impossible. please find attached a short TRK depicting the issue. Best, MK NAV_Mark_bug.trk

Hello, In the JSOW MFD page, the ATK AZ, EGEA and ROB parameters are still non functional - is there a due date to complete this functionality? In the systems and payloads thread it is marked as complete. Best, Mk

Hello, please find attached a track file showing 2 Mavs shot in ripple fire against 2 different tanks. The missiles appears to be tracking correctly, each on its own target, however, when the first missile hits, the second disappears. This was reproduced several times in the same scenario. Best, MK Ripple_MAV_bug.trk

Following Frederf report, please find attached a track file showing erroneous markpoint DED behavior. 1. Left MFD set as TGP, Right MFD as HAD 2. "Markpoint" screen selected 3. DMS pressed down, TGP is selected as SOI 4. DMS pressed down again, HAD "blinks" as SOI momentarily and immediately deselected - cannot be SOI until exiting markpoint DED screen mark_HAD_bug.trk

Hello all, Don't know if this is the correct forum and if it is a bug or not, but here goes: When I apply roll with the trackir and then pitch, I get pure pitch movment on the screen - the movement should be a result of multiplication of the 2 Euler matrices (pitch over roll). Maybe something isn't configured right, but the current behavior is really annoying. Hope I made myself clear and someone can advise. Best, Mike

Hello, From several updates ago, the F16 starts in air with navigation lights on, even if it is in combat scenario. Please change the default to FENCE off, so we can coherently understand the status of the A/C when we start a scenario. Thanks, Mike

I reviewed your track - the difference is in the angular separation. In my track I launch immediately at mission start. If I wait for 15-20 seconds, the angular separation is large enough for each missile to go to its target. Thanks, Mike

There you go, Mike HARM POS Bug Caucasus.trk

Hello, weird behavior in POS EOM and PB. Two SA6 SAM sites located apart from each other. Launching in either PB or EOM on the first site (SP1) with ASL on target, then switching over to the next site (SP2), bringing FPM to the ASL and launching the second HARM - the two missiles go for SP1. I attached a track with a reproduction utilizing EOM, but it repeated with EOM as well. also attached the MIZ file. please confirm if it is a bug or operation error. Mike HARM test.miz HARM POS Bug.trk

I have seen photos of 54 and 38 mixed loads and I don't see any reason for 103 and 105 on the same rack. Didn't see any evidence of JSOW with CBU or JDAM up until now.