TOViper

It just needs 60 triggers (10 for each digit). e.g: Trigger1 triggers the first digit if its 0, setting a value or flag to something Trigger2 triggers the first digit if its 1, setting a value or flag to something Trigger3 triggers the first digit if its 2, setting a value or flag to something ... .. . .. ... Trigger 60 triggers the last digit if its 9, setting a value or flag to something Then it's done

the title was wrong, its not the coordinates, its about dimensions. sorry, corrected it already.

It seems that the trigger action X:COCKPIT HIGHLIGHT POINT confuses Y and Z dimension, so in order to get highlighting of points right, you may edit the file me_trigrules.lua and change lines 259 and 260 accordingly. null null

So we would have to do a "Saab 900" module, or even a Saab 9000 module, hm?

I have to laugh! At least we both get for .... off-topic bullshid ... This topic was about the patch, was it? OK, now in order to steer the ship back into the right direction, and in order to not get banned, I have to say that I am super-super-super happy about Heatblur making updates and repairs for the Viggen. This is one of the main reasons why I am still so much in DCS. Otherwise, I would have difficulties keeping my interest. The Viggen is my most beloved module and none of the other modules changed that (at least so far), despite differences in quality and complexity (e.g. the F-4E, which in these terms is A BLAST).

Updated picture two posts above....

Which seat: Pilot / WSO? Maybe conflicting key bindings that inhibit opening? Which mission? Maybe something is scripted in the mission?

De nada my friend! Unfortunate part of the story is, that (at least) I have no information about the acceptance of the manual, in terms of numbers and hours read. Interesting observation for me is, if I look to the hottest discord channels, I have the impression that nearly no one there reads a manual, simply because of the kind of questions that are asked there. In contrast, It seems a bit different with users here in the forum, where I often notice that pilots look for something special in the manual, but sometimes they simply can't find what they were looking for, or need just a bit of clarification, or post suggestions for corrections, etc. Two worlds? Discord users don't read, forum users read? Is it easy like that? I am sure I get for that ...

This is a draft of the new chapter Miscellaneous on page 382, which is coming with the next DCS update; have fun! null 100% true; we need Sweden mid and south.

Hey nzteddy! Currently you cannot find this topic in the manual. For Kola map only(!), the generation of reference codes for the kneeboard can be done in three different ways: "Use only DCS codes": Only numbers for the available airfields are generated for the kneeboard; currently these are 20 airfields (9001-9020), and 94 reference points (9101-9194). "Only use the real codes": Numbers for all airfields in Sweden are generated; currently these are 69 airfields (9001-9069), and a ton of reference points (9101-9171, 9201-9270, 9301-9341, 9401-9486). "Use real, and DCS codes": Mix of both Look into your kneeboard, you will find them on pages "Airbases" and "References"; on each of these two pages, you can surf to their related sub-pages by RSHIFT+PAGEUP/PAGEDOWN. Note that many of the real codes currently don't make too much sense, because the Kola map has its most southern "border" at a latitude of 65°; many reference points are between 50° and 65°.

Yeah, absolutely. Best trick is to set the switches to incorrect positions after spawning, so the student has to correct as much as possible. Seen from a didactic perspective, a click to correct something is much better than just a "check this and that and press SPACEBAR to confirm". But it also has some taste of "non-realistic", since pilots usually set all cockpit switches to correct positions when turning off the aircraft. You can change switch positions by using the trigger action "X: COCKPIT PERFORM CLICKABLE ACTION" (dev, command, value). Check the status of a switch with "X: COCKPIT ARGUMENT IN RANGE" (arg, min, max) In the mission editor, open up the training lessons for the Viggen on my homepage or Rudel's training lesson for the Viggen; they all contain thousands of such actions and checking of switch positions. But be aware: finding out dev, command, value, arg, min, max requires carefuly study and often time consuming investigations, so be prepared to spend A LOT of hours on making and testing on one single lesson. Good luck mate!

.) Just fire up the DCS model viewer (dcs\bin-mt\modelviewer2.exe). .) There, select File > Load model, and browse to your DCS\Mods\aircraft\MirageF1something folder, there search for the shapes folder, there select the F1something.EDM file. .) Then select Show > Show connectors, and surfe through the cockpit to see the cockpit control or element of your desire, then hover your mouse over it, and the ELEM NAME is then shown in cyan color. Note: this only works for controls, not for indications! BTW: It must read "Auslassdruck und Einlassdruck" (7 is behind the turbine, 2 is in front of the fan).

This BTW doesn't work for AI aircraft, but only for player (and client) aircraft.

I think the best you could do was to follow the suggestions in the Notes section of the lesson.

Hm. In the training lesson guide I found this:

Good day dear Viggen drivers! Here are the manual updates that came with the DCS update October 30th, 2024: Manual update 2024-10-18: .) page 29: Removed double information about the airspeed index dial; added info about red/white off flag. .) page 29: Added pressure values for all common measuring scales. .) page 30: Reworked description for the Attitude indicator. .) page 31: Renamed chapter "Course ring and Course index" to "Heading ring and Heading index"; this was done for didacic reasons, because a "course" is typically used to describe a direction (a line) from or to a navigation facility (like a VOR), and a "heading" is the direction where the aircraft longitudinal axis is aligned with. For this change, a lot of literature was considered. References will be adopted in the next weeks. .) page 58: Moved last sentence between the two pictures for didactic reasons. .) page 73: Added header "Overview" for didactic reasons. .) page 74: Moved subchapter "Differential" to page 73 for didactic reasons. .) page 76: Added subchapters "Pitch trim", "Roll trim" and "Yaw trim". .) page 76: Added description for new subchapter "Roll trim". .) page 76: Added text " and works for pitch and roll" to chapter "Trim system". .) page 103: Added "... reference altitude is ..." in 4th paragraph. .) page 165: Changed sentence to "From the static pressure from the flight data unit, the barometric altitude adjusted for sea level is calculated by the computer.". .) page 165: Added "(above transition altitude)" in last sentence of section "CK37 calculated altitude". .) page 168: Added "Beredskapsvarning" to header "BER mode warning". .) page 168: Changed wording of first sentence in section "BER mode warning" slightly. Thanks to Discord user Anarion! .) page 360: Changed section "M1-M9" slightly. Thanks to Discord user Bobthe28th! Kind regards, TOViper Edit: This version became part of the stable version on December 4th, 2024 with DCS 2.9.10.3948.

Thanks Naquaii for coming in on this. Despite the fact that ENKEL seems not to give satisfactory solutions, at least I am personally happy about two things: I basically remembered correctly most of the story (it was 2018 when we discussed this and that), and - much more important - I had a beautiful dinner. Both saved my day

I don't know if I am now turning away from the point of which we are talking now, but IIRC the aim point that is shown in the HUD is for the 4th rocket in the salvo, so a few land short, a few land long and a few land very near or at that point. If using ENKEL, the rocket leaving the pod is "the first" in the salvo, and I guess that is why it lands long (or was it short?!?) But I might be wrong on that ... and I think I should now shut up and go for dinner ...

Just besides all written above: Didn't we come in the past to the conclusion that a more steep dive angle (e.g. 30°) should increase the probability for hitting the target significantly? A very shallow angle increases the chances for the rockets to miss.

IIRC1, there has been a "training pod" in real life for the ARAK rockets, which had a switch on the pod to choose for firing only one rocket per trigger press, or fire the salvo (all). IIRC², HB implemented this function in a sense to use that function from the cockpit, and solved this via the ENKEL mode, in order to give at least the pilot the option (which was much more elegant than just selecting this via a kneeboard or something else). IIRC³, The computer calculates for the center point of the salvo, thus firing a single rocket might miss the target always (too long or too short, I dont know for sure) @MYSE1234 @Cobra847 please correct my 3 statements above if you know more on that old story.

I think it is worth mentioning it in the manual update after the next, which was already finished and locked; therefore I set a reminder for the next revision.

RC2.1 pages 293 and 295

The line not beeing visible or blinking is a current bug, which Myse is aware of, and I think for the upcoming patch he already solved that issue. Can you remove the above info about the line not showing from your post please, just to keep the necessary info there and throw away the uneccesary one...

I was able to exaclty replicate this situation, where the HUD + ADI leads me to the wrong point of the circle:

I am currently in the process of finding out if the distance to the runway has an influence on that, and if the TILS does something to that, because initially, the TILS is blinking, despite I had turned it to another channel (in this case to 01, and not to A - which would be 12 for Kholki) which would mean it uses the localizer for horizontal guidance for a short period of time.