Jump to content

Lynnux

Members
  • Content Count

    58
  • Joined

  • Last visited

About Lynnux

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The behaviour being totally underpowered on Persian Gulf maps was a bug which is gone. One symptom was the engine RPM going up and down on idle throttle. That's not happening anymore, now engine control only oscillates a bit when you throttle up or down.
  2. 1) and 2) I've tested it shortly before I created this thread, gulf maps I retested later. And tested again now on the MP server with "your" loadout (2 RB-05, 2x RB-15, X-tank): Still not possible to fly on 100% mil with gear down. Strangely, the speed stayed at 300 kph for some time while AoA went up from 10° to 12° then it decreased further. After firing the 2 RB-15s I flew home relatively high (540 m) and the speed stayed at ca. 370 kph. So at least this time it was better after getting rid of some ordnance and fuel. But I assume also from outbaxx' reply that this is a
  3. Ok, thanks for the answer. But that means the Viggen will be in great trouble if the afterburner fails at take-off and also touch and go without AB may be hard, depending on the load. But AB shouldn't be so prone to failure, at least not in a sim. Concerning the Persian Gulf maps: I tried this again and it seems that is fixed. I remember that on maps with this problem the engine RPM was going up and down on idle RPM, obviously engine control had some problems on those maps. Not anymore...
  4. Temperature: +15°C QNH: 755 / 29.72 Altitude: 390 m (1280 feet) in case of 2)
  5. 1) Nosewheel steering On the ground, standing still. Best visualised in low light conditions with nosewheel lights on since they turn with the wheels: Apply some rudder pedals, then accelerate, keep rudder pedal input the same. Observed behaviour: Turn radius tightens with increasing speed. This makes no sense, should be vice versa or stay the same. 2) Rudder Causes tremendous roll rate. At 500 kph rudder roll cannot be countered by elevons anymore. Really ? 3) Rudder and nosewheel steering "harmony" A bit input on the rudder pedals ca
  6. Dear Heatblur, is this the realistic behaviour of the Viggen ? 1) Take-off without afterburner The Viggen can barely take-off with one external tank and 4 RB-74s. The landing gear has to be retracted immediately and the plane has to fly straight in a very, very shallow climb for some time to gain speed => Possible with light ordnance but not really feasible, afterburner needed. 2) Low-level flight with gear down Ordnance: 2 RB-15s, one external tank, 2 RB-74 Level flight on autopilot 390 m above sealevel Switched afterburner off after ac
  7. That's for sure. There are aircraft with contradictions like the Viggen where you cannot tell if this possible but your gutfeeling already tells you that something is wrong. Flying 1600 kph all time but not having enough thrust to fly level with some ordnance and gear down on 100% military is such a contradiction. On some Persian Gulf maps I couldn't even keep the speed at low level and 100% military with gear up and the same loadout. You need to climb to like 1000+m to be able to fly on just military. Don't know if that's realistic. Ah yes, I forgot the Viggen was never build for lo
  8. General hint for 2.7: The direction of the runway used by ILS is in the CP/PD setting of the landing waypoint. It's set automatically depending on the previous waypoint, i.e. the last waypoint before the landing waypoint. So when ILS makes you turn away then likely the ILS expects you to land from the opposite direction because the previous waypoint is somewhere on that side. In this case you have to set CP/PD to the opposite direction (=add or subtract 180 degrees). So check CP/PD to fit your approach and enjoy (almost) autolanding...
  9. Exactly. AIM-9L: - max. speed: Mach 2 - max. range 17.7 km Matra R.550 Magic II: - max. speed: Mach 3.5+ - max. range: 20 km PL-5E: - max. speed: Mach 2.5 - max. range: 16..18 km All have so-called "all-aspect" IR seekers. All data from the same reliable (*cough*) and famous western-oriented source What's to be investigated is e.g. the behaviour to lock onto targets far outside range and then loose the lock until the target is reaquired at a much shorter range. This doesn't make sense to me.
  10. I've read that in case of the AMRAAM the range to activate the seeker in case of small (=small RCS) targets is 5 km. So obviously this setting is used to: - increase the probabilty that the missile locks onto the correct / intended target (setting = small) - increase the probability that the missile locks onto the target at all (stealth target, small setting) - reduce the time until the missile seeker is activated (targets with large RCS / only enemies in the target area, setting = large). Otherwise the seeker activation range could always be 5 km Another
  11. This. But in case of the "Chinese New Year" livery (which is very nice) let the canopy fog once
  12. Oh, that's why... just looked if someone reported this already.
  13. Lynnux

    M-2000C WIP

    Thanks for that info. Has this been changed in 2.7 or already earlier ?
  14. Lynnux

    M-2000C WIP

    Hmm,I tried several times now to drop low drag MK82s in CCRP mode with IP and offset point without updating the IP manually via the diamond, just flying over the IP. Older videos show that at the moment the plane flies over the IP, the offset point is selected as target and the "wings" are appearing on the HUD. The wings never appeared in my case so far, the bombs cannot be dropped. The wings only appear after I've updated the IP manually (which I don't want to do as already mentioned above). Can someone confirm that this is still working or broken in 2.7 ? Tried this the
  15. With the recent autostart fix, ALCM is started early and you can choose the loadout and equip the plane in the meantime. The whole autostart doesn't take much longer than the ALCM alignment then, this is great.
×
×
  • Create New...