Jump to content

Recommended Posts

Posted (edited)

If you take the time to read the linked thread, you'll see ED changed how the ARK-9  ARK-5 works to be closer to reality.

It's not a bug, it's a feature.

Edited by Flappie
ARK-5, not 9
  • Like 1

---

Posted

I meant ARK-5, sorry.

 

Ramsay and Tarres explained the 3 radio presets in the mission editor implementation was wrong, because the real MiG-15bis didn't have these. I quote Ramsay:

Quote

The module hasn't been broken, the change in ARC-5 behaviour was deliberate to make operation of the ARC-5 radio set more accurate.

 

 

Then Tarres gave a good explanation of how the ARK-5 Near switches must be used:

 

Then Ramsay gave another, more detailed, example:

 

---

Posted
17 hours ago, m4ti140 said:

The only thing the near far switch does is flip the range knob on tuning panel remotely. The default MiG-19 implementation is simplified, but even there there's a way to turn on a more realistic implementation in options. ED didn't do that, since the Mission Editor gives you tools to place your own NDBs. If you want to "roll back" an airfield to 50s to make it MiG-15 compatible, just add a custom beacon on top of the downwind inner beacon with same code and frequency that matches outer frequency on another scale. Otherwise just set it up so it gets as close to the inner freq as possible and tune manually after switch - i should be close enough to do that during approach.

 

I was not talking about near/far switch... I was talking about 3 separate ndb switches...

Posted
5 hours ago, mastershotgun said:

I was not talking about near/far switch... I was talking about 3 separate ndb switches...

 

As the threads linked by Flappie explain.

 

The three switches select the frequency range on the ARK-5 receiver which will be used when switching from far to near.

150 - 310

310 - 640

640 - 1030

Far beacon being within the 640 - 1030 kHz range, tune this in the ARK- receiver. The corresponding inner beacon is within 310 - 640 kHz range, you need to switch the 310 - 640 kHz (middle switch to on).

Overflying the outer beacon, you can now switch far/near switch to near, and the ARK-5 "automatically" receives the inner beacon (without turning the crank), because in the near position, the range selection is used from the switches and not from the frequency range dial on the receiver unit.

Posted

Please read the post above, @Ramsay put it really nice together with pictures.

Only some OM/IM combinations work. Frequency range set and than tune with the hand crank on the ARK-5 receiver on the right side of the cockpit. On the kneeboard there's also a hint for the frequency as the scale is hard to read sometimes due to parallax error and what not.

Posted

Sorry guys, but I still not get it... How do you tune it than? You are not going to mess with the ARK-5 tuning handle, because if you do it will mess up your far beacon settings. Which is exactly you do not want. The whole reason why you have the switch like that, on the so easy reach position as it is, is to quickly switch back and forward getween near and far beacons to get your runway angle approach... This is what give MiG-15 the "all weather" label... If you mess with the handle, you loose that capability...

Posted
3 hours ago, mastershotgun said:

Sorry guys, but I still not get it... How do you tune it than? You are not going to mess with the ARK-5 tuning handle, because if you do it will mess up your far beacon settings. Which is exactly you do not want. The whole reason why you have the switch like that, on the so easy reach position as it is, is to quickly switch back and forward getween near and far beacons to get your runway angle approach... This is what give MiG-15 the "all weather" label... If you mess with the handle, you loose that capability...

 

The near and far beacons frequencies are supposed to be coupled. Same position of the tuning handle, only different frequency ranges. The one for far that you set on the rotary 3-position dial on the right (for the far beacon), the other for the near beacon is set by the switches.  But by design, the tuning handle should not move. Only the ranges.

  • Like 1
Posted

Ok, so taht's the trick, they should be coupled, like there should be some predetermined difference between near and far beacon frequencies... Oki, I was looking at it as what L-39 have... Thank you.

Posted

It's amazing how ingenuous some of those early radionavigation systems were. And how they managed to work around limitations in technology or even (in this case) User Interface. 😄 

 

I believe the Mig-19 has two separate "memories" for the frequencies and thus does not require the outer/inner NDBs to be coupled. I wonder if the Mig-17 has made the jump to that or if it still has the early Mig-15 system that we discuss here. 🤔

Posted
17 minutes ago, BuzzLine said:

It's amazing how ingenuous some of those early radionavigation systems were. And how they managed to work around limitations in technology or even (in this case) User Interface. 😄 

 

Well, that was exactly what I was thinking... Because we also need to deal with different time eras and different countries... Not all countries follow the same logic/offsets for the beacons... So, to preset frequencies is maybe not so realistic as we would like, but it is much more usefull gamewise as what we have... If it make sense...

Posted
3 minutes ago, mastershotgun said:

 

Well, that was exactly what I was thinking... Because we also need to deal with different time eras and different countries... Not all countries follow the same logic/offsets for the beacons... So, to preset frequencies is maybe not so realistic as we would like, but it is much more usefull gamewise as what we have... If it make sense...

 

I understand your viewpoint. If ED aims for maximum historical accuracy, they should also provide accuracy beyond the plane itself as, as we see here, the environment plays (played ?) a part in the whole system. 

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...