PE_Tigar

Installed, and noticed a couple of things: a) can't find SoH terrain anywhere b) tried starting several instant action missions, CTD every time (did the cleanup and repair as well)

+1 :) I love the Viggen and the shirt looks cool, but a size guide would be very helpful. Or at least some "testimonials" :D.

Well, here's to hoping this gets addressed soon.

HUD brightness up/down commands exist, but do nothing when mapped VTB image controls below the display do nothing RWR dimming knob only dims RWR lights, not the display itself - kind of hard to understand, all other a/c with similar RWR displays dim the display Tried with or without deferred shading, same results

1.5.8 as well

Correct - the problem was with one of the "mods" that require export - LotATC, UniversRadio, SimpleRadio, or Tacview... Strange, just that one campaign has problems with the export.

Sorry to resurrect an old thread - in current version of 1.5.7 this campaign is broken for me, mission loads and when I press fly on the briefing window DCS freezes.

Konkurs has 4km range - if BMP launched without entering Tiger's effective gun range it would have a chance. If in range Tiger would've destroyed it with impunity.

Torso - could you please share the design for the housing you've mentioned above (if you've finalized it of course)?

There are significant differences - 25T basically doesn't exist, and never existed in its game form, while 27K was build and deployed in numbers. 27K is much faster. 27K carries Kh-25L and Kh-29, but not Vikhr, etc . In my view, 27K is closer to AJS-37 in its capabilities than to Su-25T, (with Viggen being more versatile).

All air forces in the world do initial training or screening in small prop planes. I guess, but I'm not sure, that Russia uses Yak-52 for basic training, USAF uses Diamond (looks like DA20) etc. I agree that having such a plane in DCS would be interesting, for RPG purposes, and for training in general (shooting ILS approaches in a fast jet is not the best way to learn if you've never done it).

At altitudes and speeds that MiG is flying, my preferred way of defining waypoints is RSBN radial/distance. It takes a bit of preparation, and requires a nav log prep as well, but if used properly you will be reasonably accurate. We can't really do 2x RSBN radial intersection method because we don't have two RSBN sets.

Yep - the game does that. But in reality I imagine that your INS drift would be pretty high after landing. So you get a choice between a reset (as it is now) and large drift (how it should be in reality) - in both cases the remedy is new alignment. So - for me - a minor niggle.

What? Navigation simplified? Do you even fly MiG?

Yep, still here - confirmed in extensive testing yesterday.

Also - test switches for autopilot and FBW test are buggy. - both can be engaged and operated with covers on. - in addition to that, if the switch is in the "test" position, and test is finished, if you left click it again (which should have no effect), the test is annulled/restarted. It is obvious that the switch registers only the action (to start the test), not the condition of the switch.

Great - I'll look into that template and post it back here with changes.

Same here - the original link works for me - and thanks again emolina for creating the missions, really appreciate your work. BTW, some observations, after flying a couple of missions: 1. Conditions - it's very hard to hit the exact second when your wheels leave the ground. IRL you would ideally count "breaks off" at the start of the takeoff run as your takeoff time. I don't think that the game logs that, though. Suggest change this requirement to minutes, or at least penalize less for not hitting the exact second. Same with landing. 2. Conditions - however, on the other hand, it would be good to put altitude and position triggers on waypoints - that's how navigation competitions work IRL. You should also use more stringent limits for aircraft with advanced navigation suites (A-10C, Ka-50, M-2000C) and those without. 3. Kneeboard - weather report could be in internationally recognized format. Here's how it looks for example: METAR LKPR 301000Z 19008KT 9999 FEW036 20/11 Q1016 NOSIG RMK REG QNH 1013=. You could give METAR (=weather report) for departure airfield, and TAF (=forecast) for destination. For MiG air pressure should be given in mmHg, standard pressure (1013.25 HPa) is 760 mmHg. AFAIK military ops are flown on Qfe BTW. 4. Kneeboard - navigation. You got mag headings and distance - perfect. IMHO altitudes should be rounded in meters for MiG (9000 instead of 9144, for example), it's easier to maintain. Nav aids - TACAN is useless for MiG, you can remove that. Instead, RSBN channels should be used. For NDBs Sector and number should be used instead of frequency. I think it would be easy to replace NDB and RSBN frequencies with channels/sectors+numbers automatically using a simple table. Same goes for radio frequencies. 5. Speeds, TOC and TOD - MiGs performance is much better than many slower planes in DCS. For example, your required cruise speed of 740km/h TAS is actually very low for MiG. MiGs normal cruise speed is 600 km/h IAS, which translates to around 900 km/h TAS @30k feet. Of course, the speeds should be defined in IAS in the nav log as well. You should also think about time to climb and time to descend. Top of climb and top of descent should be defined if you're flying as high as the missions stipulate. In one of the missions my last WP before landing was 86 km from destination @30k feet. That required very steep descent. In nice weather it's no big deal, but in shite weather could mean additional workload. Also, ideally you would aim to have an initial approach fix as your last waypoint before landing in the nav log. So, to conclude - so far so good, and keep up the good work :). If I was you, I'd perfect the missions set, packaged it as a training/challenge campaign and sell it.

Tried it for L-39C, but having these missions for MiG is much better for me - I have 10x more hours on it :).

Thanks Cobra! Looking forward to it!

Donated, and will seed until I reach 10:1 ratio. Thx for your hard work Starway!

This is pretty cool, considering that the carrier does not seem to be moving. Ditto on the headwind question.

I'd do a repair and try again.

It's a simple question really - S-5K and KO have been used normally by all Warsaw Pact countries, and MiG carried them as well. Can we have these two versions implemented for MiG-21bis please? The funny part is that all other planes that carry UB-16s or 32s have S-5KO, and not M, or K for that matter...

@Babushka: check your axis mapping and calibration (if you use an axis for throttle). You want to check if your throttle axis goes all the way to 100%, and re-check if the throttle lever in the cockpit moves visually to its forward stop. If you use keyboard - wait for the patch. Regarding your questions on how you turn on one or the other stage of the AB, check the attached image (these are default switch positions, cold start). Or maybe RTFM.