CoBlue

What joystick? redder pedals or twist for yaw? Do you have other planes in DCS? if not you can try the Su-25 or P-51d, does the problem remain when flying them? Try clearing in controls, keyboard assignment x & z for rudder.

Very interesting RagnarDa & the result is awesome :thumbup:.

Yes, 98 in Poland, a bunch of Viggen's & Mig's landed on a road-strip, there was a very nice video, unfortunately it's deleted. https://forums.eagle.ru/showpost.php?p=2637203&postcount=725

Try to in: C:\Users\....\Saved Games\DCS\Config\Input\AJS37 folder, remove (& save) the content (.lua files) in joystick & keyboard folders. That's the joystick & keyboard assignments. DCS will rebuild new .lua files & you have to remap your controllers/keyboard. If it doesn't work you can always put the old ones back.

Mig-21 has a small tactical nuke, A10c: CBU-105/97, can't you somehow combine them so we'll get the destructive force of BK90's? Also if the problem is as described bellow by "mattebubben" there might be a solution..... So why don't make BK90's to brake apart over the target? As long as we get the desired destruction on target area. Nobody is watching them afterwards anyway :smilewink:. Please make BK90 to work as intended :thumbup:.

Arak in Normal range checklist set(according to manual), disabled motion measurement, Grupp or Enkel always hit long? Wasn't this bug fixed before & reappeared again? anybody else having the same problem? Dive Boms precision seems off over water.

I've tried get it to work in 1.5, but I'm confused with all the changes. Can somebody please upload it for 1.5? /thanx

Still the piper is too small compered to RL https://forums.eagle.ru/showthread.php?t=175604 .........but hay nobody cares....

That's only a temporary solution. That switch was never used IRL. https://forums.eagle.ru/showpost.php?p=3078865&postcount=3

Tested in MP & SP, this bug is occurring randomly. On BlueFlag server my first 2 start-ups went ok, the 3:d no heading & no HUD. In SP the same, sometimes it works sometimes not.

This bug is back, can't rearm Rb-04E without exploding.

I can confirm this bug. On BF server today my first 2 start-ups went ok, the 3:d no heading & no HUD. In SP the same, it's random, sometimes it works sometimes not.

AFAIK only Viggen & Mig-21 suffers from this. All other modules I can play-back without issues.

Yes, there should exist the ability to set the clouds to at least 30m (100') & also an overall visibility setting. As it is in RL METAR's or FFS's (Full flight simulators).

In the HB Viggen there's some missing textures. ADI- missing 60° & 0° bank marks. Clock- missing seconds needle. G-indicator- missing resettable needle for maximum G. VSI- Goes only to +/- 3m/s in flight, instead of 5.

Hello, I'm on w10 & I have the taskbar always visible when Radio Overlay is active, described here: https://github.com/ciribob/DCS-SimpleRadioStandalone/issues/103 I've tried the fix & suggestions, but no joy, any ideas how to solve this? /thanx

Yes, very noticeable yaw oscillations, when rolling & landing.

How do I assign the weapon safety button on my joystick, "Trigger safety bracket ARM" & "Trigger safety bracket SAFE" , to a 1 toggle button (on/off)? is it possible? /thanx

I made a simple mission (see attachment). After I rearm & take-off from the road, the ground-crew starts to drive away somewhere? Even though I gave no command to do so & they don't have any way-points to go by. How do I keep the the ground-crew stationery?

You can choose if you want knots & feet in the L-39, by changing between imperial/metric in the GUI options. To OP, A-10C is a good & forgiving trainer & since you fly it, you're the perfect instructor ;).

Easiest way is to check your altitude at starting airfield & target point on the map. Then subtract the value from your altimeter (if target is above). ie. Your airfield alt. = 150m, Target alt. =250m, = 100m difference. Set your altimeter to 0m (starting airfield) & subtract so it reads -100m.

This is amazing! works great on my end (1.5 stable), thank you RagnarDa :thumbup:.

Thank you for the mod Mustang, it makes a huge difference, fantastic work:thumbup:.

Arrestor cables on roads would be impractical. As the tactic was to move from road to road in a war scenario. You would have to have the system ready before Viggen can land, setting up such a system is complicated & takes time. What if the system is not set up for some reason? & Viggen is low on fuel & has to land?....kaboom bye bye Viggen :music_whistling:. However I'm sure the cables & drag chute & other "fancy stuff" were considered by SAAB designers, but found inadequate. After-all they designed the 1st flight computer, TERR Nav & Hud. Much safer to have the trust-reverser on the Viggen, that way the pilot can land on whatever road he chooses, weather the ground crew is there or not, or in an emergency, or for cover. The whole filosofi of Viggen was that it had to bee as mush independent & self sustained as possible ie. no external nav aids, 3 ground crew required for rearm/refuel, fast hideaway on road bases. Show me an airplane of it's era that can: Take-off with Max TOW in 500m. Land with Max LDW <400m. ??? And do it consistently, mission after mission :smilewink:.

Not quite right. What you are describing is an Non-Precision Approach not an ILS. ILS=Precision Approach, uses DA/H (Decision Alt/Hight) minimums. ILS CatI DA(H) 200'(60m), ILS CatII 100' (30 m), ILS CatIII >50'(15m). Visual reference requirements for continuing- approach lights in sight. RVR (Rwy Visual Range) is also important. Non-Precision Approach, uses MDA/H (Minimum Descent Alt/Height). For Viggen the minimums were 60m, in peace time AFAIK.