SexyTomato

In the current build, the command steering is activated automatically upon receiving localizer signal as advertised in the manual. But according to the HAF manual, command steering can be enabled/disabled by placing the asterisks on the CMD STRG in the T-ILF page and depressing the MSEL button.

@Lord Vader This is the first item I presented but whatever, I am not gonna argue about it. Yeah this is the second item. Normally, if you do a normal alignment on the ground, the INS will do the true heading and attitude alignment from 98-90. But if you turn it off and do the normal alignment again (I think it is legit when I am on the ground and not moving), the INS wouldn't do the true heading and attitude alignment again. Because when you do it the first time, you will notice the pitch ladder on the HUD moves as the INS tries to do the attitude alignment. When I turn it off and NORM again, the pitch ladder doesn't move anymore. I don't know if this behavior is simulated intentionally or not and currently in DCS the true heading continues to be updated even I turn it OFF. So in order to prove it, I did the trick to get the true heading stuck (which I think it is another bug?). Then when I did the realignment again, you will notice the INS doesn't do its job to align the true heading. However as you judged that it got stuck because I broke the system and the true heading may keep working in degraded navigation mode, I guess only your team can clarify it.

Not sure why you are ignoring this obvious bug, so I am gonna further explain it. As you can see in the track, after I turn the INS knob to OFF and wait for 10 seconds according to the manual, the INS is still working apparently. On the INS page, the LAT/LONG coordinate, altitude, true heading, and ground speed still change, the pitch ladder in the HUD still has relative movement relative to the aircraft movement. And in the previous track, the INS doesn't stop aligning as you can see the pitch ladder still moves after I switch it to OFF, indicating that it still tries to find the attitude. Viper INS doesn't stop working with knob in OFF.trk

Hello @Lord Vader Well just test things out in case I would like to restart normal alignment. First, the INS shouldn't be working when I set it to off, that's the bottom line. Second, in Normal alignment, the INS should begin to attain true heading and attitude information from 98-90 according to the manual page 164. It doesn't do so when I turn it off and on again, that's what I am trying to say.

The INS keeps working even I set the knob to OFF. The alignment just keeps working. If I set it to ATT and then back to NORM, then to OFF and back to NORM, the normal alignment does not seem to work. As you can see in the track, the true heading completely froze up. Viper INS doesn't stop working with knob in OFF.trk

Yep!! Thanks for the help. Yeah, visual reference for the canopy haha. Sorry for the confusion.

Hey, thanks for your reply. BSA is Basic Surface Attack. It is a basic way to drop bombs I guess? Here are the explanation of BSA and canopy code:

I would like to do some BSA training in Mirage F1, but when I search Google, I can't find the canopy code. Can someone kindly provide it? haha

Hello, After the comms checks and clear take off from tower, Weasel 52 just stay at his bunker with engine running. I have tried this twice.

Yes both. Oh, I didn't know that. I think that is the issue cuz I just lock the guy right in front of me. Yeah I think it's the range issue, thanks for the suggestions.

Should it enter RAID mode when I use RAID command, either by HOTAS or by DDI button?

Just wanna try out the new update and I encountered this problem. When I command RAID in TWS BIAS and MAN, the radar just reverts back to AUTO without entering RAID. Track attached.Honet cannot enter RAID in TWS.trk

Here is a better representation that the radar would acquire a real contact at its first raw hit. I reset and silent the radar and wait until all the track files are faded and deleted then re-enable it again. As soon as it gets the first raw hit, I immediatly use Fast Acquisition and it locks the target. Same thing happens to the Viper. It doesn't attempt to get a SAM lock against a false target. If you want me to open a post in the Viper section, I am happy to do it. Honet real taget first raw hit.trk

Here is the summary that what I did in the track: 1. TDC cursor on the false contact -> Castle switch to the radar DDI to attempt Fast Acquisition -> The radar enters AACQ and locks the real target with existing track file 2. Reset and Erase all the contact -> Enable Silent for a few seconds -> TDC cursor on a real target once the radar gets its first raw hit -> Castle switch to the radar DDI to attempt Fast Acquisition -> The radar enters AACQ and locks the real target 3. Disable LTWS -> TDC cursor on the false contact -> TDC depress to attempt Manual Acquisition -> The radar doesn't do anything 4. Disable LTWS -> Reset and Erase all the contact -> Enable Silent for a few seconds -> TDC cursor on the real contact -> TDC depress to attempt Manual Acquisition -> The radar successfully acquires the target Honet false taget behavior.trk

If I castle switch to the radar DDI on a brick, the radar should enter mini-raster scan to try to lock the target. It works when the brick is a real target, even only one brick is obtained, which the radar should not have a valid track file on that. For the false target however, the radar would not do anything. The radar magically know which is a real target and which is false.

Hey bro, you gotta setup the lazer code for my GBUs after the last bomb fuzing update. I flew all the way to south central Iran and only found out my bombs missed because the code was 1688 instead of 1665 as advertised.

It seems like you are focusing on the "Designation" mode, while I am talking about the behaviour after slewing. Again, the pod only drifts after TDC depress and slew with NAV designation. But with Radar and HUD designation, the pod will be slaved to the last slew LOS even without TDC depress prior to the slewing.

Just press the Undesignate/NWS to undesignate the target, then you will get the cross and the pod isn't slaved to anything. Yeah it should refer to "Designation" mode in the manual, where it is repersented by the diamond symbol. So it should be ground stablized or slaved to the coordinate. Strangely the "INR" symbol appear after slewing the pod in this mode and it's also ground stablized. In fact in page 275 the F16 manual, "INR (inertial rates). In INR mode, the TGP maintains its LOS on a position using only inertial integration. It does not do any image processing. INR track mode is effective at approximately maintaining the TGP LOS when the target is at risk of being masked or obscured." And in page 227 of the F18 manual, "Tracking Mode. Indicates the current target tracking mode. See Tracking Modes, below. Pressing the SCS in the direction of the FLIR format cycles between designation, SCENE, and AUTO tracking modes. Pressing the Undesignate button activates INR tracking mode." So I think the manual of F18 needs to clarify a bit more for this mode. Moreover, if you do a Radar Designation or a HUD Designation, you can still slew the pod in "Designation" mode without TDC depress. And the pod is still gound stablized afterward. And as I mentioned, I somehow managed to get the pod gound stablized after a NAV designation with a TDC depress and slewing the pod, which is in the end of the track. So I think it is definitely a bug. When this bug happens, you can notice the coordinate on the pod keeps changing, which is unresonable to show the coordinate I think if the pod isn't meant to be gound stablized. Yeah for the time being this is the only thing I can do.

If I want to move the targeting pod after a NAV designation, I need to TDC depress first. However, after that the pod isn't ground stablized in INR track as you can see in the track. If I SCS to the pod DDI to get AREA(SCENE) track first, the pod can be ground stablized while I can move the pod around. But during the recording of the track I messed around a bit and was able to get the pod ground stablized after a TDC depress as you can see in the track, so I am pretty sure it's a bug. Hornet ATFLIR bug.trk

After the fight against Iranian strike package, alert 30 should come to relieve us. But it seems like they were stuck at the carrier. I have already played this mission twice and get the same result. Track attached via google drive link. https://drive.google.com/file/d/1_dbwgETABGeXonpuYkFjoxkHVLG5kw3l/view?usp=sharing BTW, the mission completed image and "fence in arm strong" was activated before I took off.

Please give some love to this mission. TvT

I found one video edited by one of the member indicated that the radar indeed wouldn't reset the scan when rolling, at least not in a relatively fast roll rate. As you can see in the video, rolling is involved in all three examples of real life footages while the radar just keep continuously scanning.

When the aircraft is banking in EXP, DBS1 and DBS2 mode, the radar just stops scanning and reset the scan after stop banking. I have no evidance that it's the correct way the radar works. But I believe it's the same logic that causes freeze mode go blank as reported in the this thread. As you can see in the track, freezed radar image goes blank even it's inside the gimbal limits. It occurs in f18 as well. F16 AG radar bug_20230326.trk

Nope. Everything is stock except for the CMDS lua of F18 that I amended so that I don't have to program the counter measure every time. The first time I played this mission is in November and it already existed. I tried this in MT in this update which I don't have reshade for this version and it still happened.

In the JSOW deployment phase, I used the radio manu to tell reven34 to drop his bomb. He responded but kept following me. The strange thing is, he would call fence in from west when we arrived at the west from the target and call pigs away when I decided to drop by myself instead. Can't attach the track file cuz it exceeds 50MB.