corvinus

Honestly, it currently works as described in the manual, at least as far as my experience goes. The canopy switch is not animated when you use the keyboard shortcuts, which caused confusion for me, but the functionality is there. To answer your questions: Jamming with U22/A: Put the jammer in mode B/F. In the right warning panel you'll see MOTVERK (countermeasure) flashing when it is jamming. The jammer is a repeater, so it only transmits when the RWR detects a threat radar. Dispensing Chaff with KB: There are several ways: 1. In automatic mode set the KB pod in mode A (automatic) and streak selector to 0. The system will dispense chaff when required. 2. Manual: Set the mode to either 1, 2 or 3 (fast, medium or slow release). The streak mode can be used if you want to pods (assuming you have two) to empty sequentially rather than in parallel. Now to start dispensing set the "countermeasure dispense switch to KONT", this is SAND on the canopy switch, OFF is NORMAL on the switch. You can also use the keyboard shortcut, but the switch on the canopy doesn't move. 3. Fast button: Use the fast counter measure dispense button. There is only a keyboard shorcut. If you only want to release flares you have to set the KB pod to "R" (default is "RF" which means chaff+flares). Dispensing Flares with KB: The only way is to use the fast countermeasure dispense button. The KB mode has to be either "RF" or "F".

Are you on open beta or on stable? I am on open beta and there is a continuous stream of fixes and improvements. There do seem to be problems with the published changelog, sometimes it is incomplete and sometimes it lists changes that did not make it in the build.

Using the mission editor you can. Define a zone where you want to remove trees. Then degine a trigger action at mission start. There is an action to remove scenery objects, which you can configure to remove trees only.

Call me crazy, but I dodge missiles for fun :D But you are right, for the Viggen the appropriate doctrine is to fly low.

Cool, that would be really nice!

You're welcome!

True, but the fast dispense button always uses program P2. In the ECM tutorial by Badjoe he recommends P1, so I went with that. Does P2 works effectively against, say, a Tor SAM?

You are right, it does work, thanks for pointing that out! :thumbup: Well, I tried using the keyboard shortcuts a few days ago, but nothing happened then. I guess I had the dispenser in automatic mode. :doh:

Please? :bounce:

Can we conclude from this that ED has a working ground mapping radar implementation, or did RAZBAM make an implementation themselves?

Maybe it is just me, but I can't get the keybindings for the countermeasure dispense switch to work. I have mapped countermeasure dispense INT/KONT/OFF to 7, 8 and 9 respectively. However pressing any of these keys does exactly nothing. As I usually use this switch when defending a SAM I really don't have the time to reach for the mouse and click the switch. So fixing these key bindings would be a big help for me!

In my mission I have "GroundCrew #1" instead of just "GroundCrew". I'm not sure if the system is that picky though. Here are some missions that you can use if you want: https://forums.eagle.ru/showthread.php?t=222539 Missions M09 - M11 from "Navigation and Landing" are appropriate. In a vid by Badjoe ( ) he mentioned that re-arming only works if you have RB-24J's on the outer pylon. It doesn't hurt to follow that advice.

Being in NAV is the correct approach. The problem here is that in some cases you never reach the pop-up point, i.e. the steering directions do not bring you to the desired distance and heading. As a result there is no switching. Switching to ANF manually when you are close to the popup point (either in range or bearing) sounds like a good workaround. Currently I'm not using the popup points anymore, I'm just winging it. :pilotfly:

Did you take a look at https://forums.eagle.ru/showthread.php?t=224752 ? Currently you have to make sure target is within the pitch ladder. If it is outside the pitch ladder you do not get a response (i.e. you see a diamond).

I have no issues with the AKAN, but all my Viggen experience is 2.5.3. Perhaps something did change wrt 1.5, requiring a small adaptation by the user?

If you are interested in type designations see https://en.m.wikipedia.org/wiki/1962_United_States_Tri-Service_aircraft_designation_system There is also a section on the Hornet being an exception and why. While I am at it, here is the system for electronic system designation https://en.m.wikipedia.org/wiki/Joint_Electronics_Type_Designation_System

The system is kind of picky about the unit names, see: https://forums.eagle.ru/showpost.php?p=3664654&postcount=74

Thanks for that tip! I had just set up VS Code to run some batch script to do the extraction and updating. But the winrar method sounds much easier.

It turns out that you have to add the key in three places: 1. mission - trig - actions 2. mission - trigrules - actions (way down in the file) 3. mapResources Now it works again (but boy that wasn't easy to fix!)! :)

Advice noted! In this case I only started opening the zip file after the problem appeared. I think it all started with cloning a trigger which contained a radio transmission. I changed the audio file for the cloned one and after that both audio files were linked. After changing the audio file in one, then other was changed as well. After pulling my hair out about this, I decided to remove one of the triggers, which lead to my problem of the empty table key (well, that's my hypothesis). The good news is that I have found a way to update the zip file without breaking it. By using the command line it is possible to update files. In this way the resulting zip file can be read by DCS. So I extract the mission file using: cd src 7z.exe x -tzip ..\mission.miz and update files using cd src 7z.exe u -r -tzip ..\mission.miz * The bad news: Removing the empty key leads to a radio transmission without an audio file (no surprise here), but after adding an audio file, the empty key is back again. I've tried adding a key manually, but that didn't work either. :confused:

Thanks for the tips! I'm already using Notepad++ so that wasn't the problem. But I gave totalcommander a try. Sadly I had the same result. If I take the original mission file (that still loads perfectly fine), unzip it in totalcommander and then zip it again, the file won't load. I'm just staring at the load screen with a progress bar sitting idle at 0%. Perhaps totalcommander and 7z use a Windows system library for zipping? This is on Windows 10 btw.

I have a mission that seems to have a corrupt mapResource file: mapResource = { [""] = "example.ogg", ["ResKey_Action_454"] = "voice.ogg", } The empty key in table seems odd, and my problem is that I can't add new radio transmissions as trigger actions. So I thought I would just unzip the mission file, remove the empty key, re-zip, and I'm done! ... no such luck. I'm using 7zip to unzip and it already gives a header error. No worries, because the files seems to be ok. However when I re-zip (as a regular zip file), then DCS can't read the mission file anylonger. It just hangs when reading the modified miz file. So basically my question is: What tool (and with what settings) should I use to manually edit mission internal files?

It should be able to correct, but INS always introduces errors. Being limited in space and weight, the BK90 probably does not have an INS as good as the Viggen. So some drift is to be expected. Now I don't know if the currently experienced drift is due to a modeled INS error (which would be awesome), or that the drift is really due to an faulty implementation. In any case, it is probably best not to plan your attack cross-wind ;)

I suggest going to an airshow, that's your best bet!

It is not a matter of tech, but of physics. A flat road or runway reflects radar waves with a different strength than, say, grass or trees. This makes it possible, also for the viggen, to show runways. It does depend on the beamwidth and pulse length used by the radar. Shorter pulses give better resolution, so choose the short pulse option for the radar. The beamwidth is fixed for the radar, but in cross range the resolution is proportional to the distance, so you will see more detail closer by. The issue with the current implementation is that the reflectivity of surfaces is not always correct, making some distinct surfaces to appear similarly on the radar screen.