corvinus

Great! :cheer3nc:

It is not you, it is the mission. For GRUPP mode to work the RB04 needs to spot at a column of ships at least three rows deep. Since you have only two ships in the mission, the GRUPP mode cannot be used in this case. See the figure on page 325 of the manual, so see what I mean. @Airhunter: The RB-15 works with the Bx waypoints, so I think you are referring to that missile. The RB04 does not use waypoints, you just fire it in the direction of the ships.

That is great news :thumbup: Thanks in advance to you and your team.

I do not really understand why a 2:1 transfer ratio is considered fair. In the old system you had to accompany your bonus points with a big pile of cash. Not so in the new system. If I want to buy a campaign now, I can only use about $2 or $3 worth of bonus. Meaning that ED will still receive some cash. In the new system I can buy the campaign without spending extra cash. The old bonus points were not free to spend, there were strings attached. The new ED miles are with much less restrictions, making them more valuable. So the transfer ratio would be higher than 2:1, which would be the naive monetary transfer value. Note als, that given the fact that there will be a large amount of idle bonus points amongst the customers, any transfer of current bonus points to the new system will mean a drop in cashflow for ED. I think that this also needs to be taken into account. Imho fair would be to give currents customers a fair change of spending their bonus points in the old system. For example increase the amount of bonus points you can use on a single purchase. Now you can trade 20% of the purchase price with bonus points, but ED could increase this to, say, 50%. It would essentially be a sale for people with many bonus points, i.e. the loyal customers.

The Viggen is measuring the barometric altitude, it probably uses the value in the calculations (to account for differences in air density and speed of sound etc.). The altitude setting (barometric/radar altimeter) is only for HUD displaying. Afaik it does not affect the computations. In any case I cannot recall that it affected my aiming. Note that in ARAK/AKAN deployment the Viggen does not provide a CCIP. You indicate the target position by putting the sight dot on the target and pulling trigger unsafe. You then keep the dot on the target (this main radar dish is also pointing at this position in order to measure the range) and wait for the firing cue. Only at the firing cue the sight dot corresponds to the impact point of the rounds.

It is "the dot": The manual further mentions: At least, according to the manual, radar ranging is accurate in case of sloped terrain.

Actually, the Viggen does not use the radar altimeter for weapon deployment. It would lead to serious errors in uneven terrain as, I think, the OP was hinting at. The Viggen does use radar ranging together with the depression (or pitch) angle. For this the main radar antenna is used (ground mapping is then disabled). When radar ranging is disabled or the radar is used for ground mapping, it uses the QFE method. In the QFE method you set the barometric altimeter to the QFE of the target. The barometric altitude is then the altitude relative to the target. From page 283 of the manual: In ranging radar you have the range and pitch angle, so you can solve for the height. In the QFE method you have the height and pitch angle and you can solve for the range.

Yeah, I have the same problem. In the radio menu you can advance the mission, but don't expect your wingmen to land though.

Thanks, glad you like them!

Why would it be useless? Together with the depression angle (how much the target is below the horizon) you get the relative height of the target. This is enough info for computing a firing solution.

The runway position and heading are used when taking off to provide an automatic nav fix. For this to work you have to switch to BER and then NAV on the ground, if I recall correctly. There is no need to press the reference button, this button is only required when taking off under strong cross wind conditions. In such a condition you press the reference button when you are carefully aligned with the runway (see page 241 of the manual).

I added the heading so you can use the LANDING NAV mode. In this mode you are steered to the "LB 1" waypoint, which is placed at an offset to the runway. Once you get there, you are steered to the "LF 1" waypoint, which is at the runway. In order to compute the LB 1 waypoint, the CK37 computer needs to the the heading of the runway. For a TILS landing the runway is less important, as the TILS system will guide you to the runway in (roughly) the correct heading. This is from page 146 of the manual (RC2), I hope it clarifies things a bit:

I thought that was what I was saying ...

The rensa button is giving me troubles, clearing targets does not seem to be possible. See https://forums.eagle.ru/showthread.php?t=221480

And don't forget internal system noise, if you lower the threshold, all you will see is noise ...

The release pattern still works. Setting QFE is still a good idea, if you dont the target indicator ring can seem a bit off as it is placed at the wrong altitude.

Thanks for letting us know. I've got to try this!

Do you have the "sync HOTAS on start-up" option enabled? Fwiw using this option in combination with a X52 does not lead to the problem you mentioned.

Just give it a try and report back!

You speak on behalf of all Italians? Don't think so ... No one is speaking badly of Italians, it is just your personal ideas that cause some raised eyebrows.

That is the meteorological definition of spring, the astronomical definition uses the passing of the vernal equinox. That happens between 19 and 21 March, this year it is 20 March. Not that it matters, this is just fyi.

This is important, but as the radar cue, the 3 km cross, is still misplaced it will not help much. See: https://forums.eagle.ru/showpost.php?p=3592944&postcount=24 The bug was confirmed by HB, in post 25, but I do not think it has been fixed since.

I don't think RR bombing is really working correctly at the moment. Same holds for the A2 mode (or I just don't understand it ...).

Ah ok, that helps. 800000: Carrier is engaged. 800001: Carrier or one of the two closest escorts is engaged. 800002: Random ship within group. 800003: Random ship within group. Assumptions: All ships are within missile seekers search area and carrier+escorts is identified as a group (they need to be "close" in naval terms).

800000: Missile locks on target closest to ATP (which is the Bx8 point). 800001: Missile searches a fixed area around the ATP. Then it determines the three detected targets closest to the ATP. From those it randomly selects a target. 800002: Missile searches a fixed area around the ATP. Then it randomly selects a target, from all the detected targets within the area. 800003: Within the fixed search area around the ATP, the missile determines if there is a group of targets. Then from the group it selects a target randomly. Without a picture of your ship groups and the ATP, it is difficult to say exactly what will happen. It would depend on the geometry of the ship and where you place the ATP.