Machalot

Also affects the Viggen. Heatblur said they have fixed it internally, but I haven't seen an estimated date for a hotfix.

I might be able to test it later tonight. But I think it may be correct behavior if it works as you describe. I think the HUD indication is not directly tied to the TGP line of sight, rather it shows the SPI, sensor point of interest, which might be the last point designated in Area/Point Track and is not affected by SP. It wouldn't make sense for the SPI/CCRP target to follow the SP line of sight because it would have to calculate the bomb release time for a point that is moving forward at the same speed as the aircraft, which (almost always) makes no physical sense.

Erratically and randomly? I haven't had any problems recently. What are you seeing?

Would be a nice feature to be able to tag objects in the mission for a high fidelity track file.

This might be caused by the DCS map using a flat Earth model.

Can you clarify why this function would not be supportable via mark points on the F10 map? That's exactly how the Viggen does it -- the user creates mark points and labels them with codes that are parsed by the DTC interpreter and turned into waypoints, attack points, reconnaissance points, and landing points with associated heading information. The Viggen has a step to actually insert the data cartridge and load it, but for the Viper that could be done via the Comms menu or some other special function until they implement an actual DTC model.

I would love to hear an explanation of why it's correct that S-J of 4 HARMs simultaneously launches them at whatever radar is nearby. There is no way to safely drop them from the jet without killing somebody?

This is the most important phase of most missions!

@IronMike I know you guys are working hard to get a fix out for the map mark points CTD. Do you have any idea when a patch might come out? Thanks. Edit: I saw this is already fixed internally! Great!

Maybe Q and Z for you? Or page up / down.

I mapped the numpad directly (RCL as . ), the dobber to the arrow keys, and the increment/ decrement switch to ctrl+arrow keys. The six buttons at the top of the UFC (COM1, LIST, AA, AG, etc) fit nicely into the 6-key group of insert, delete, home, end, page up, page down.

Every time I take a break from the Viggen I miss this feature.

Looks like this also includes the effects of the leading edge flap deflection, I assume, which is subscripted as lef. What is subscript sb, speed brake?

Would be nice if the AI ATC gave that info as well, wouldn't it?

Does this early trigger pull result in the correct release of bombs?

Can't argue with that. But I find the Hornet more clunky to use. Too much clicky clicky through all the screens and sub modes.

I know there are placeholder pages on the MFDs that you can get to in a single press of a button, but I haven't found any that leave me wanting something I need to use.

It's my favorite module by a wide margin. Very easy to fly if you just want to sight-see or do some canyon runs, and has lots of power with the three stage afterburner. The thrill of low level flying is unmatched by any other module (at least among what I own: F-86, 5, 14, 15, 16, 18). But it requires some discipline if you want to be accurate with weapons since the primary bombs it carries are unguided. You will learn to be aware of your airspeed and altitude at all times from quick glances at the cockpit gauges, while using the very intuitive HUD to deliver your weapons, which is almost completely graphical and geometrical with very little text. It predates the computing revolution of the 90s and 2000s, so while it was very advanced technology for its time (onboard programmable computer, inertial navigation with terrain measurements, and a ground mapping/terrain avoidance radar), it's still primarily a fast jet with some electronics attached to it, rather than a supercomputer with wings.

Hmm, you get different results than I do. Even with the Bk90, I have landed two anti-armor Bk90s directly on center of a group of 4-5 vehicles (such as an SA-15 setup and some trucks) and had 2-3 of the vehicles survive undamaged.

A bit off topic, but I just want to second this. I learned the Viper first, and am constantly frustrated in the Hornet by constantly moving up and down the layers upon layers of menus and subscreens within subscreens.

If you fly by the rulebook (no negative g's in the Viggen) you shouldn't need to be strapped in!

So maybe the indexer lights should be off for daytime starts too.

And this is a matter of taste, but I like its avionics workflow and layout, and the way it feels in flight, better than the Hornet.

I have lots of fun with the Viper. It was very buggy several months ago, which made it frustrating to do A-G with laser guided bombs and Mavericks, but after some updates it's now very functional in both A-A and A-G, although still incomplete. It currently lacks an A-G radar or helmet mounted targeting for A-G, but the helmet targeting works decently well for A-A. With the Litening targeting pod and well-placed waypoints it's fun to strike ground targets. It is still waiting for JDAMs and might never get a Harpoon, but it has decent HARM functionality. Some people seem to complain that the flight model is under performing in dog fights, but that's not my thing. It is much less complete than the Hornet at the moment, but still entirely playable and enjoyable unless you really need the missing features or final flight model tweaking.

The new clouds in 2.7 cause large areas of the ground to be shaded. However, the mirrors in the Viggen don't include the shaded effect, they show bright direct sunlight. These screenshots were taken at Sukhumi on the Aerobatics Online Caucasus server while a large cloud was overhead. I'm flying in VR. For reference, here's what is behind the aircraft: