Robo76

SAAB A/ C JA 37 Viggen Aircraft Flight Manual, ( English Language ) , - Aircraft Reports - Aircraft Manuals - Aircraft Helicopter Engines Propellers Blueprints Publications (aircraft-reports.com) SAAB JA 37 D Viggen Aircraft Flight Manual Sicuro | Aircraft, Manual, Blueprints (pinterest.com)

Hello. Years ago there were requests here in the forum for a Viggen JA-37 Mod D. Does Heatblur Simulations have future plans to redo the AJS-37 to a new standard like the F-4, or make a new JA-37 when the Kola map is done ?

Aero L-39 MS.mp4

Since this pedal axis setting mainly adjusts the turn signal sensitivity in flight, you can't set the wheel turn separately. Do you have any tried and tested settings where both the landing gear and rudder work well ?

null

Isn't the turn sensitivity of the aircraft when taxiing exaggerated ? The other modules are not. And the Viggen has non-steerable rear dual wheels, which are supposed to, among other things, better hold stability when reversing the engine. The rear wheels keep the same track and logically prevent turning. The front wheels try to steer over the stable rear wheels, so cornering can't be as responsive as it is in the simulation. Or is it different? Translated with www.DeepL.com/Translator (free version)

I don't have WWII, so I don't know how it's adapted there, but if it goes there, why shouldn't it go throughout DCS. Maybe it would be possible to modify an area using zones on the map and limit the speed and landing gear endurance on those zones so that DCS would treat it as a "grass runway", which would prevent F-15s, F-16s, F-18s, Su-27s, etc. from taking off over other grass areas on the airfield (which is happening), but allow machines that were suited for it to taxi and take off from the grass runway. If the point of DCS is faithful simulation, the ability to take off on grass is also a strategic feature of the aircraft that becomes very apparent in MP missions where the "red" machines are not just reliant on the airfield. Military eastern doctrine counted on their airfields being destroyed. Western military doctrine dealt with this largely by way of STOVL aircraft. Translated with www.DeepL.com/Translator (free version)

I suppose the inability to land on grass or get stuck in grass while taxiing is a bug. These aircraft (like the Su-25) were designed to operate from grass airfields. L-39.mp4

I have tried the procedure on 24.11. (after several updates) and it is already working correctly as before. INU saves the coordinates of the fixed point EXACTLY. I was instructed in the debate above that this works, but it didn't. Similarly, INU no longer saves unambiguous coordinates because it can't know if they are correct. Thanks to the authors for the correction.

Would it please be possible to add the option to map mouse buttons 4,5,... like most of the other modules ? For example, I set the mouse to turn on the flashlight and toggle the coordinate system on all modules, but Viggen is one of the few that doesn't support this.

Thanks for the explanation.

Will this ever be fixed or will we be forced to tag the cables ?

When HOTAS Virpil is plugged into a different USB hab socket (i-tec USB 3.0 Charging HUB 13 port) than was plugged in during setup, some axis settings change randomly. For example, the throttle pedal locations are set, or the axis invert is swapped. Teammates on other devices and USB hubs have the same problem. It's annoying to look for why autostart broke. Uploading control settings from a backup for each machine is unnecessarily time consuming. Translated with DeepL

When the Viggen is on the ground, its wheels are stuck in the ground/runway, see picture.

Klíčové funkce MiGu-21 nelze mapovat na vícetlačítkovou myš jako v jiných modulech.

When dropping weapons on the inner pylons, the AA Igloos are dropped at the same time. The AA MIS-EXT button is not implemented, select jettison is not possible.

Of course I changed the coordinate system in ABRIS, that's why I mentioned it. The problem is that the selected fixed point coordinates are not saved exactly in the INU. And if arbitrary coordinates are entered, that doesn't work either (INU doesn't know which coordinates are correct). It used to work correctly ... until it was recently "improved". Or is it no longer used to insert 2x Uncage Shkval ? According to the procedure in the current manual it doesn't work. Translated with www.DeepL.com/Translator (free version)

Ka-50 III The INU coordinate correction using the flyby method does not work. The entered fixed point coordinates (setup ABRIS coordinate format xx° xx´ xx" => xx° xx,xx´ = PVI-800/INU format xx° xx,x´) are not saved to PVI-800/INU after double pressing the Uncage Shkval button (they were before). I further assume that any fixed point coordinates (for function checking) should go in as initial for the INU system. INU cannot know if the fixed point coordinates are correct, so it should set them as initial. If this correction cannot be made correctly, the TDC positions on ABRIS and Shkval do not match. (Translated with DeepL)