Opalias

When ordered to tune the radio jester acknowledges normally, but only adjust one setting on the radio on click. So when ordered to turn CH18 he will switch from CH1 to CH2. and when ordered again from 2 to 3. This does not appear to effect Waypoint/TACAN entry or selection.

Remember, the F/A-18 auto pilot will fly AOA in a landing configuration. If you trim to AOA the FCS will automatically adjust to maintain AOA. Hornet landings should be done almost exclusively with throttle. Enter the break at 800' 350kts, aim to have your downwind 600' landing configuration, trimmed to AOA (aprox. 2-3 seconds up trim) with your abeam at 1.1-1.4nm by TACAN, target your decent for 450' at the 90 on AOA, don't pay attention to speed, speed will change slightly with weight, probably 135-145kts, but what you need to be is on AOA hitting altitude milestones. You should roll into the groove ~3/4nm, 370', on AOA, then you should fly down the whole way with throttle. Make three part corrections, if you are low the throttle input should start from your glide slope maintain power, more power, then less power than your initial, then back up to your maintain. Opposite for coming down. Be careful when you are too high, its easy to pull too much power too long especially in close. Remember to watch/trust the ball, don't spot the deck. You will probably feel like you are landing long, remember you're not trying to put the cockpit on the 3 wire or even the mains, your aiming the hook, which is well behind and below both.

https://en.wikipedia.org/wiki/Infrared_homing I'm not sure about the specifics of the R-73, but the most modern systems are much more sophisticated than simply tracking engine exhaust. I don't think that it would be unreasonable, look how well IR works for ground attack, even on shut down vehicles.

So as some people have indicated you need to hold the NWS button in the F-5 any time you want to turn the Nose wheel, you should allow the nose wheel to center prior to releasing the NSW button, it takes a little while to return to center and it's not particularly controlled. During your take off roll, you want to only use toe breaks (just a tap) until you have enough speed for the rudder to be effective. Do not touch the NSW once your take off roll has started or you will very likely over correct.

The SA-6 Launcher has no radar of its own, you need to add the matching tracking radar (tr) to the group. That will fix both problems.

This would be great especially since bad weather doesn't activate the lights, so you can be Case III in weather riding the minimums and the carrier won't turn on any lights even if you do call.

Digging into this a little more it moved when I shifted a few of the frequencies, and it was corrected by changing all the ewr groups (3 separate groups) to the same Callsign instead of unique names. This might be a larger DCS problem.

Working on a mission with 3 ground EWR stations on 3 different frequencies, I have tried a number of FRQ and spacings with the most recent being 124 131 134 139 Mhz AM, while I can call normally over buttons A and B buttons C and D don't even have my transmit audio, just static, am I doing something wrong or is this a bug?

Having weather with a little more variability within the map without the kinda random dice roll type editing of either the weather lua files or pressure within the editor would be really nice

It would still be nice to not pass out from just bumping the nose down at high speeds.

Multiplayer. But I’ve run a bunch of multiplayer games on that sever before, I’m think it was something unique about the mission, weather, or bugs related to units. No new mods being used, and those that were aren’t extensive.

Careful what you wish for, maybe while they are adding a more realistic DM they will also start simulating the constant jamming if shot while maneuvering.

Has significant bugs crop up with a mission today. The losses were across all player controlled viggens and showed with a variety of symptoms. 3 Marks were made to try to establish the route and then loaded into the Viggen. Planes would randomly lose electrical power withing a few minutes as indicated by a loss of HUD or SAS or engine crank ability, experiences unexplained defueling of the plane when rearms were requested. Is this something that could be caused by the temperature? There were also a number of aircraft that we had not seen in the server until this mission with the Viggen. Su 33 B-52 Weather 0 C QNH 29.92 QFE 29.76 This is a really strange one to troubleshoot, we ran a mission same day, same build with better weather and without the B-52 and Su 33 without incident. Any thoughts or insight would be greatly appreciated.

I can't figure out why when in the precision dive bombing some of the bombs don't release, I think I'm pulling at 3.5-4 g, any thoughts on why some the bombs on a pylon would release despite a full long pull and hold on the trigger?

Built a mission with spawnable MiG 29s for missile employment practice, starting point is about 25-30nm apart. First spawned MiG 29 is immediately detectable and engagement goes as planned. I then respawn into another aircraft that starts in about the same position, and spawn the next advisory at the same spot as well. This advisory does not show on radar, despite being high closing range rate, and high altitude. AIM 120 fired in visual can home on the target, but until guns range, target is completely invisible to radar despite sweeping though modes (1-6 beam and various sweep widths) I was able to at one point aquie the contact with the guns mode, none of the CQ modes were able to produce a lock except for the gun sight.

Does your helmet also say 9M?

The BK90 navigation points are updating ME waypoints via radar fixes, the problem I was having before I think was that there were buildings masking the returns of the tanks near the initial location that I was targeting. I made probably 8 additional passes and was unable to achieve better than a glancing blow once I removed the interfering radar returns. So likely these could be my fault, just an inability to get the targeting precise enough. I do still think that the problems I saw on the multiplayer server were fundamantally different, but I need to go back and try to verify that based on what I am observing now. The only variables I think I had between these tests and the MP server was the MP and the fact that I had entered the waypoints manually instead of the ME. I still am not sure why my radar altimeter fixes won't go above condition 3, but that is probably unrelated.

So I went back and did some more testing. I move the waypoint further off the target for this track, and noticed that the bk90s were closer to the tanks than the previous waypoint. I think that the radar return from some of the buildings near the airport was masking the return from the tanks. I move the tanks off the air field as was able to get better accuracy, but still unable to achieve a hit. These misses could be operator error, but if that is the case the skill required to quickly target even a large group of tanks may be beyond me. Tracks attached. I still need to go back and see if the manually entered waypoint behaves differently. When I was in the multiplayer server the misses seemed much larger and the impact points seemed more consistent even though I believe that I had targeted different units. On a side note the axis for the radar stick takes a lot of curve tuning to get to work well, and small smooth motions are still a challenge, accurate enough for a RB 15 for sure, but i'm not good enough to use it for ground attack apparently. bk90 test 2.trk bk90 test.trk

Further experiments in single player show similar results, pre programed waypoints work normally, as well as manually entered waypoints, but waypoints that are updated in flight using the radar do not update in the BK90 and the weapon will proceed to the next waypoint as it was entered prior to updating with the radar, this is true for both B and M waypoints. My testing method was to plan a flight in the mission editor, with the target waypoint being offset to once side, fly the track, update the target position. Weapons hit as expected if the waypoint was accurate in the mission editor, if the target were to have moved, or if the waypoint was off, there appeared to be no way to update the point. Also based on the fact that the waypoint was not updated for the weapon even if the weapon was being shot at a B waypoint, I wonder if INS drift is being taken into account when employing the weapon, or if the weapon would still be aiming at planned attack point regardless of INS error at time of fire.

Recently I was flying multiplayer on the Caucuses and I was unable to get the radar altitude fixes to work. I started cold, waited for the ball to settle and align, did a normal data load (9099) and then programed waypoints to the target manually. I navigated to the target, which was designated and a "M" updated its position based on the radar, but for both salvos of the BK-90 the weapons naviagated to the same point, that was not near the target even though I overflew and ensure that my target waypoint was accurate. Not sure if I'm employing this wrong, but I used to be able to do this without any trouble. I did reload the BK90 after a RB75 attack if that makes a difference.

There are still some switch shared switch limitations, but especially when sling loading a human spotter would be extremely valuable. The gazelle had to basically divide the cockpit to get everything to work, and there are still some persistent bugs being stamped out.

Now that we have the Persian Gulf map I find myself flying Iranian OPFOR quiet a bit, having the AAR option present on many of those planes would be greatly appreciated. I’m not sure how much documentation exists or can be inferred about those planes. But I would gladly pay for this as an add on like the GPS if given the chance. I would also buy a separate variant if a whole redesign was needed to capture the differences.

Is dive bombing sensitive to QFE? I have been trying to dive bomb in the caucuses recently and I did not set waypoints. I used the map to determine the altitude and divided by 27 to calculate QFE, the area is pretty hilly, and I made some adjustments during my approach to get the QFE adjusted altimeter to agree with the radar altimeter in the HUD. I went through my normal bombing run and the bombs fell well long of the target. Any thoughts and strategies when bombing in a hilly area?

Roger that, my biggest concern was that somehow the F-14 landing gear might have similar modeling/coding techniques, and not being able to drive that around on the Stennis would have been a much more pressing problem. I thought it very strange that I’ve only seen this with the Viggen. I’ve managed to get a few other aircraft down on the carrier and at least had never noticed it before.

Also the clipping manifests as almost a stutter rather than a complete failure of the interface.