Machalot

But you really should create a new topic, by the rules and by etiquette. They are free and a new thread is much more likely to get the attention and help you deserve.

I just ran a single player mission about 9 times, testing codes 921, 922, 923, 921, 922, 923, 921000, 922000, and 923000. Each time, I set up the weapons, launched, and then watched in F6 view overhead to see the flight paths and dispersal patterns, then ejected and respawned. I didn't find anything unusual with the weapon employment. The patterns always matched my inputs. (Although after about 6 respawns my altimeter QFE setting went to 300 something, but it only affected my release queues, not weapon performance). I can provide the track if you want. But do you have a track showing that it doesn't work? Edit: Just reread your comment and I think I missed your point. You're not saying 922000 doesn't work, you're saying STD shouldn't disable it, right? I ran all my cases in VALB. So my test was probably not relevant to your post.

That would be a good callsign

This might be improved by setting your trim properly based on weight. I typically set it to about +3-4 deg for a full load of fuel, a2g ordnance, and an external tank.

Yeah. I'm trying to hit all the points that might affect nav accuracy generally. I can't account for an observation that M points have error but B points don't. Could be a misperception, but we can't know without a track. I've definitely misperceived what was happening in my bug reports before, and once I got everything else fixed up I saw what was really happening. For a road takeoff you need to enter the runway heading. It's also very important to do a nav fix before employing BK90s because the nav initialization in a road takeoff has more variance, which affects everything downstream. How consistent is your liftoff point in these multiple tests you're running? That affects nav accuracy because your nav state is set equal to the LS point when the wheels lift off. I wonder if that affected your observation that QFE affects BK90 accuracy, it could have been different liftoff points between the two runs with no nav fix to correct it. I'm also not completely sure how LS works with road basing and the F10 map. It might accept your LS point from your cartridge, or override your LS point with the location of the FARP in the mission file. Do you know?

This should not happen if your LS information is properly set in the CK37 and you are aligned within 15 deg of a runway centerline. Are you taking off from an airbase?

Yes, it now has a random offset at every spawn. A wrong setting contributes to nav drift. This might be part of the issue too. Can you try without the high Gs?

Some shots is the dark then, without seeing your track: 1. Are you setting the MagVar properly? 2. Are you waiting until you are on the runway to switch from BER to NAV? 3. Are you aligning precisely to the runway centerline and pressing the Reference button before starting your takeoff roll? 4. Are you flying below about 300m AGL so you get full TERNAV updates? You should see the last two digits of the CK37 readout as 50 when in AKT POS/OUT. 5. Are you doing any visual nav or radar fixes en route that would move any waypoints? (T1-TV) 6. Are you doing hard maneuvers or rolling more than one revolution? 7. Are you taking off from the runway designated by your LS waypoint? 8. Is your Doppler switch in the right position for the surface you're flying over (LAND/SJÖ)?

I haven't tried this, but I presume you could copy the miz files from the campaign to your Saved Games folder where you keep custom missions. Then open them in the mission editor and edit the aircraft. Change the Viggens and Tigers to "Client" instead of Player or AI. That should let you select which aircraft to fly at mission start and even to use the missions for multiplayer. The challenge is if you then want the Viggen to run the player's original role as AI. You'd have to give it a series of orders to do so, which might not be trivial.

I didn't know that. Thanks!

With SPA points you can't move them, each fix becomes a new point.

Does this mean trimmed to hold the correct approach alpha, or trim set to zero?

Redundancy: two main landing gear.

When you open the trigger safety in NAV mode with high drag bombs, you activate CCIP mode. The HUD displays the CCIP symbols on the ground. If you are too slow, too low, or too high, the CCIP symbols will drop off the button of the HUD because the bombs will impact down there. The HUD symbols will reappear when you close the trigger safety.

High drag or low drag bombs?

I agree with @Kite Ryder, this sounds like a compressor stall. The HUD has a limited display range; if you pitch up or down more than about 10-15 deg from the horizon, the HUD symbols will not be visible.

I think the one that is hardest to judge and causes the most problems is the spacing of Bx9. It has to be far enough away from Bx8 that it will take at least 30 sec to get there if it fails to find a target. @MYSE1234After reading that rule again though, it is unclear whether it means 30 sec from Bx8 to Bx9, or 30 sec from now to Bx9. What do you think? I can see why the latter would be an obvious safety feature.

HB confirmed that is the case. So I think this should be reported over here: https://forum.dcs.world/forum/540-weapon-bugs/

I think missiles are ED's responsibility once they leave the rail. But I'll check.

Just curious -- I haven't seen the words "zoom" and "spyglass" in this thread. Are you aware of the VR Zoom and VR Spyglass Zoom keybinds under the UI Layer / VR section? I have a first gen Oculus Rift (like @Pasquale1986) and have not adjusted the Text Size nor used any cockpit mods. There are some things that are hard to see in standard view, but a quick tap of VR Zoom, or in rare cases Spyglass, makes everything visible.

You can make a copy of my spreadsheet. https://docs.google.com/spreadsheets/d/1UO-FqLKl_dQl50_dzuHEvxhtSyU5kxsMvIvesEfPFMY/copy#gid=0

For 3 km turns you can use the plot I made above. If you want a general capability for any radius I can give you the equations.

I don't read Swedish. Is this saying 4 lysbombs per station/pallet like the M71s?

Submitted to the official bug tracker.

So far the suggestions are: 1. command a circular orbit and end it after a half orbit. 2. maybe there's an aerobatics task that will do it. Doesn't sound promising.