corvinus

You can also press the RENSA (clear) button once. First lift the cover, then press the button, it is located beneath the numpad of the CK37 computer. If you press it twice, all position corrections are cleared.

I just did a few tests with the U22 pod. In the automatic mode this pod is supposed to be a deceptive jammer. That is, instead of transmitting noise it transmits a signal designed to make the radar believe the target is in a different place. This will guide the tracking radar away from the target, resulting in a break lock. It does not reduce the initial lock-on range (for that you need a noise jammer). The good news is that it indeed works this way. My findings are: * Initial lock range is the same with or without the ECM pod turned on. This is as expected. * The lock breaks several times (i.e. a for a few seconds the RWR stops beeping at a fast rate). This is all at about 20 nm from a SA-6 site with a straight inbound Viggen, so the radar is well within the RWR reception cone. * After a few lock breaks, the locks becomes steady and the SAM site is capable of firing a missile. * Ultimately the range at which a missile is launched at the Viggen (flying at 2 km msl) is reduced by about 8 km. * If you fly lower (500 m) the initial lock range is reduced to about 14 nm. Apparently the model works in such a way that at close range the victim radar is no longer deceived. So for this altitude I find no difference between ECM on or off. Can anyone provide more details about the underlying model for radar/ECM? For example what is the normal change of the tracking radar breaking a lock, and to what probability is this enhanced when the U22 is active?

I think you are right, but personally I only use the 'T0 Fix', 'T1 Fix' and 'TV Fix' controls. Just map these to three separate buttons. If you press 'T1 Fix' and release the button, it will actually hold T1. You have to press 'T0 Fix' to release trigger fix. You do not have to do that after 'TV Fix'. Mapping 'T1 Fix' to the first trigger stage of your joystick and 'TV Fix' to the second stage should work. There is probably an alternative, as there is a 'T0 Fix (three position switch)' and a 'TV Fix (three position switch)', but no 'T1 Fix (three position switch)'. I'm not sure what to make of those, anyone?

There are some excellent Viggen tutorials on youtube (granted, they are not from Heatblur). For example xxJohnxx GrimReapers Bunyap sims I have found these vids to be very helpful, perhaps you will agree.

Thanks for the tip! The electricity masts are a nice landmark you can use to line yourself up with the road. It is still a dangerous business though (technically I landed, but the plane was not serviceable anymore :music_whistling:). I've created a short mission with the aircraft line-up with the road section. It is based on the mission I made for the short runway near Kutaisi. In the mission a ground crew moves in when you land. Use can use the ground crew to rearm and refuel. Civil traffic is disabled in the mission, so at least you do not have to worry about dodging cars. P.S.: Good luck with creating a beginners campaign, would but nice to do sometimes else than training missions! Viggen Road Landing.miz Short Runway Landing.miz

Yeah been doing that myself, but it is a big map with many roads, so I thought I would ask here. Anyway, let me know if you come across a good road base candidate.

I'm looking for a nice place to practice landing and take-off from a road (a la BAS 90). Most roads have features that are detrimental to succes: telephone poles, trees, lighting in addition to being very narrow and curved most of the time. Does anyone of you know a good road, at least 800 m straight, without any road side obstacles? Preferably the road is within a few km near an airbase.

Technically even without producing water vapor the exhaust plume can cause condensation. If the exhaust plume contains small particles (say, from incomplete combustion) then these particles can serve as condensation nuclei on which existing water vapor can condense. A question, why does all combustion produce water? I get it for fossil fuels, but does it also hold for solid propellants? All you need for a solid propellant is to have a violent reaction of two solid components producing a gas. This does not require the presence of hydrogen or oxygen, per se. Perhaps all currently known solid propellants do produce water? I don't know, that's why I am asking ...

Must be, if there is no weight on the wheels then the system thinks it is safe to retract the gear. Just check this again when the fix comes in.

+1

Azimuth beamwidth of the radar is about 1.8o. At 5 km that leads to a resolution in cross range (perp to your path) of about 160 m. At least this is the rough estimate of the resolution. Being a runway width off, does not sound so bad. In this thread there are more ramblings about RR mode: https://forums.eagle.ru/showthread.php?t=217707 These are mostly about the range error. If you use a waypoint all is fine (technically this is NAV bombing), but if you rely solely on the radar 3 km distance line then, in open beta, you will find that this distance is not placed correctly: https://forums.eagle.ru/showpost.php?p=3592944&postcount=24

Do you select IR-RB on the weapon selector or do you use the fast select button. I've found that if I: 1. Set weapon selector to IR-RB. 2. Master mode to ANF. 3. Radar to A1, 15 km. 4. Point plane at target. 5. Press Tv Then I get a proper attack HUD symbology (see screenshot) with a distance line countdown, which helps if you want to fire the RB-74 at maximum range. When I use the missile fast select button, then none if this works. Only when I dial the weapon selector to IR-RB, I get the proper HUD symbology. Also note that I use Tv instead of T1 (the manual says T1 btw, but that doesn't work for me).

I can confirm both issues. Apparently I was in ANF master mode.

If by "off" you mean that the central indicator goes dark, then this probably means that the radar switches from ground mapping to ranging mode. It should provide you a range, although I do not know where to read off or use this range. Anyhow, it does suggest you had a succesful radar lock.

Here they still work (all three variants of the RB-75). Perhaps your controls got messed up after the update? That has occurred in the past.

Sorry, but I can't load the track due to an enabled mod (range targets).

No tail strike for me, however I find the plane a bit sensitive during takeoff, but being rather new to the Viggen I cannot say if it is normal or not. Perhaps you can post a track?

No need to feel dumb, this was still a useful discussion! Moreover, it led to the discovery of a bug!

I see, remember the RR modes has two submodes: radar release and nav release. If you time your trigger moment on the distance indicator gauge you are essentially doing a nav release kind of thing. This also works for me. Try to remove the waypoint and see if you can hit the target ;-) Without a waypoint you have to use the PPI only (no distance indicator guage to help you). As the 3 km indicator on the PPI is a bit misplaced, the bombs fall long.

You're welcome!

This is how I understood it from the manual. Imho the 3 km cross does not correspond to 3 km, I checked this by placing a waypoint. The distance indicator gauge indicates 3 km before the 3 km distance line in the PPI is over the waypoint. What do you make of the screenshot below? The plane is at 3 km distance from the waypoint, but the PPI 3 km distance line is not at the waypoint. Doesn't that mean that the PPI distance line is not placed correctly? Note that this is after a few minutes of flying, so I don't think INS drift is an issue here.

Sorry to get back at this point, but it is not clear if you use the PPI or the distance indicator gauge (top-right front panel) to determine if you are at 3 km distance.

Thanks for your reply, excellent suggestions! This is a good point, I'm flying about 280 m/s, and the update time is a bit less than a second. So if your radar image is 1.0 s old you are 280 m too late. The error I'm getting is in the order of 800 m, which cannot fully be explained by latency issues like this. In the 15 km setting the pulse length is 0.5 microseconds. If the radar does not use pulse compression that would set the range resolution to about 75 m. If the radar does use pulse compression (I'm not sure if that was common in that era) then the radar resolution would be even better. So one can safely say that the range resolution is better than 75 m. Now if you add the two errors the maximum error is about 350 m, which is significant if you want to hit a ship. Did you also try this with the latest openbeta update? I'm asking because if I use the B-scope, the 3 km line in the B-scope seems way off. Therefore I am also a bit suspicious of the placement of the 3 km in the PPI. I think it was correct before the update, but I'm not sure.

Thanks for the track! I've watched it and you will be glad to know that on my system the bombs also fall on target. It is however impossible to see when you pulled the trigger. I've duck into the cockpit in order to see the trigger, but I think the button is not animated. So the big question is: Did you pull the trigger when the waypoint distance indicator (the gauge on the top right of the front panel) indicated 3 km, or when the reticle in the PPI was at the western edge of the island? If I use your track and take control after you did all your settings and altitude corrections, the bombs still fall too far if I base my triggering purely on the radar echos. Mind you, the target area crosses the 3 km line on the PPI, I'm almost directly above the target. Regarding your other remarks, they are correct I think, but in this case it doesn't matter much (the target area being almost at sea level). Also the commanded height is a safety height, the computer uses actual height for bomb release computations afaik. So to summarize: * If I base triggering on the PPI => bombs fall long. * If I base triggerin on the waypoint distance indicator => bombs fall on target. For me that leads to the conclusion that the 3 km indicator on the PPI is not placed correctly.

Thanks for looking into it, much appreciated! Btw, the radar does not actively "detect" the target, i.e. it does not lock on to anything like the F-18C A/A radar. For the Viggen it is up to the pilot to interpret the radar echos.