TOViper

Hey folks, thanks for kudos! Regarding the version numbering, the original idea was to create a new version with the RC2 as basis, so the decision was to cratee a RC2.1 (RC2 with just a few modifications according to the first updatelist). I didn't knew at that time if the manual would be accepted by Heatblur (to be put to the module officially). The most important thing to understand is the following: What you have now in hands is the manual RC2 in a state where I say: yeah, that's how I want my RC2.1 to be; having all repairs and changes implement. That's why I never changed the number, because when you compare RC2 with RC2.1, there is no major change in structure and style; in fact it is basically the RC2, but a bit "better". You can trash all versions you have downloaded so far, because ALL of them where BETA, this one now is not BETA anymore. Why? Damnit, spoiler alert ... P.S. Kodus to all of you who contributed in making this manual better!

Hey guys! This time, RC2.1(beta) becomes RC2.1. Yes. Hafe vun! Update 2023-08-31: - page 17: Replaced "The AJS37 Viggen was developed..." with "The Viggen (AJ37 version) was developed ..." (initially this was correct in RC2, but I messed it up during editing, sorry my fault!) - page 32: Replaced "of the gas generator" with "of the engine" - page 45: Added text for the red ELFEL warning light : ", or the ground power is applied." - page 50: Replaced "Warning / Indicator table test" with "Indicator / Warning table test (KONTR LAMPTABLA)" according to the designation in the previous chapters, for better distinguishing of the two tests - page 50: Replaced "Indicator system test" with "Indicator system test (KONTROLL)" for better distinguishing of the two tests - page 56: Modified the engine limitations table slightly (thanks Machalot) - page 159: Moved section "Backup approach" to page 158 for didactic reasons - page 168: Moved section "Altitude hold warning" to page 167 for didactic reasons - page 173: "LS" now reads "LS SKU" - page 189: Moved section "Output of navigation data" to page 190 for didactic reasons - page 233: Replaced "Before engine start-up checklist (with ground power on)" with "Before engine start checklist (with ground power on)" - page 244: Moved section "Take-off on short runways" to page 243 for didactic reasons - page 250: Added missing "L MÅL" in sentence "Cycle runway headings by pressing ___ once or multiple times until the desired runway heading is displayed." - page 271: Rephrased section "Roll" slightly (let's see if it gets accepted ...) - page 373: Reworked all emergency procedures slightly - page 374: Reworked all emergency procedures slightly - page 373: Added picture for OPTIONS > SPECIAL - Chapter 5: removed words "checklist" or "procedure" from some headers (by definition, a procedure is something different than a checklist) - Replaced "Cabin delta pressure" with "Cabin differential pressure" for all instances (hopefully I got all of them) - Replaced "Master Caution" with "Master Warning" for all instances; Note: IMHO this was translated wrong from the beginning on, thus (sorry) I had to change it (HUVUDVARNING must be translated as MAIN WARNING; also, the color is red, which means "warning" and not "caution"; also, a Master Warning is triggered for flight safety relevant issues only > ergo this light comes on only when the shidd hits the fan ...). - Added background picture (I pray it's not disturbing) - Added date of update on the first page (thanks Machalot) - Applied at least a half zillion small text corrections here and there (note: only a half zillion, last update there were more corrections to do ... ) Kind regards, TOViper

Hi folks! Despite all other issues I have with my lower spec rigs, I noticed that the "Scenery details factor" on this map has great impact on my fps. Don't know if that helps anyone here, but I thought it might be an idea to share this information, since it was not discussed in this topic so far (at least I wasn't able to find this combination of words "Scenery details factor"). Hope that the maps becomes optimized very soon, because I start loving it ... and some day IRL I have to visit Rudel_chw for a coffee ...

Sorry to jump in right in the middle, but as a DCS F-16C pilot I often wished that there was a "Skip boresighting of AGM-65" option in the mission editor - even when cold starting the aircraft. For me, this is not necessarily true for MP servers (Buddy spike, etc...), but indeed true for "offline-usage". Now coming to the OT: I understand the claim to waste life time with that if you just want to fly a bit inbetween the carusell "family-job-personal maintenance-other things", so a company like ED with all their experience in creating modules could make this happen someday, at least this is what I wish. We have so many options to configure the aircraft in the mission editor, we have autostart features, we have rope-lengths, we have safety altitudes, we have pre-alignment of INS, etc., so why not having this "Skip boresighting of AGM-65" ... ? Let the user/customer decide in which depth he/she wants to go, and which features of IRL planes he want to skip in order to save lifetime.

Yeah, absolutely right. I hated to create more versions, since I wanted to measure the downloads. If the filename changes all the time, I have to collect all that data garbage. In the credits section of the document you may find the release date and for which version of DCS the document is made (usually the latest OB which contained ANY update/change for the Viggen module). Also, the PDF should contain META data about the document information block (which was entered into the source file before compiling to PDF)

Hey Machalot! No, I initially had the plan that the RC2.1 stays in beta as long as it is not officially part of the module. Let's see when this changes...

Guys, regarding the roll inputs, I have some news. I tested this in DCS, and managed to see the fluctuating airspeed / g-load / roll angle speed. 2g, 350km/h, pull and roll > swinging around the longitudinal axis is clearly visible, and also swinging of the accelerometer is visible. Therefore, I rephrased it: Please go through it and give me your feedback! THANKS!

Next update scheduled: August 31st, 2023

@Silhou: Can you please check if this has been put the tracker? If not, please be so kind, thank you!!

@Silhou : Is this bug already in the tracker? Problems are: Texture, and FÄLLD LAST not illluminated during the first KONTR LAMPTABLA test.

@IronMike Please note, this keybinding is still not working in latest OB 2.8.8.43704. While the sound for depressing a button is played when using the keyboard binding, the button in the cockpit is not definitively not depressed, thus no test is carried out. Problem here is obviously that in the file "clickabledata.lua" the line 475 elements["warnpanelcheck-PTR"] = default_button(_("Warning Panel Light Test"), devices.ERRORPANEL, 3002, 344) shows 3002, and in the file "default.lua" the line 258 {down = 3001, value_down = 1.0, up = 3001, value_up = 0.0, cockpit_device_id = devices.ERRORPANEL, name = _('KONTROLL light test'), category = _('Lights')}, shows 3001 for depressed state. Also, this keybinding has a wrong name in the file input > keyboard > default.lua (and maybe in a few input files more) It should be labelled with "KONTR LAMPTABLA Indicator and Warning Table Test".

Thank you guys for your answers. Maybe I will make something out of it for the next update ... cu soon!

+1, but please let us decide also in milliseconds (have to use this for some very sensitive X: SET COMMAND() trigger actions regarding pitch trim and roll trim controls.

Guys, I have read the section Roll during g-load on page 271 at least 150 times per day, and I still come to the conclusion that it needs a little rework. I have a few versions (not only these 3) which could (!) maybe explain what the original author maybe had in mind: Version 1: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can only be achieved when reducing the g-load. This should not be confused with inverted spin. On the other hand, if the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Vesion 2: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can be achieved as the g-load decreases. This should not be confused with a flicked roll. If the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Vesion 3: During strong roll input during g-load at low airspeed (Vi < 350 km/h), high roll rates can be achieved as the g-load decreases. This is similar to a flicked roll. If the roll input is neutralized, the roll ceases, and the g-load returns to normal values. Another question came up for this: Is this behaviour of the real aircraft and how is it modelled / does it behave in DCS?

Don't worry too much about imagination. Sometimes our impressions reveal something wrong, sometimes the impressions are wrong, so ... it's all human factors. You caused no trouble, and many of the questions in the forum - whatever they are about - contain something interesting or something to dig into (again). What really surprised me btw. was the fact that the measured flight data match the data in the permormance sheet very well; this is a really nice fact and therefore thanks goes to the developer!

Very observing, thanks Machalot for this hint! DONE

Hey guys! I did a test flight this evening with latest OB MT, and I have to say that the measured values in the sim fit perfectly to the data provided by Lazybot. I was able to reach M0.77 after 2 minutes 30 seconds flying @15° in 100m altitude with the bespoken loadout. See attached trackfile. 2023-08-18_AJS37_MS_with_X-tank_4xARAK_2xRB24j_2m30s_for_M077.trk

Manuals are usually smarter than the pilot, aren't they??? Regarding a printout: For sure, the next bigger update of RC2.1 will become necessary someday in the near future, but in case you would like to print out a "solid" version (I know it might sound a bit overbearing, but not meant in this way), the current version of the RC2.1 (August 8th 2023) is a version which I personally consider as "not too bad". If you find a minute or two, you may now test on your own, using the data of Lazybot. I am not sure about if I would make it today in the evening to my rig ...

Thank you lazybot, I will use it in the evening, once I have my rig available!

I think you didn't mess up anything. The values you reported seem reasonable, although the 94% seem a bit low. Maybe you can move the throttle just a little more forward, until it snaps in to indicate that the burner range zone 1 is coming ... Regarding the values, check RC2.1 on page 56: null Anyway, I will install an older version of DCS this evening and will test it against the newest version.

Hm, strange. I was able to reach M0.80 using MS at ISA conditions with X-tank, 4xARAK and 2xRB24js, despite - to be honest - the acceleration seems indeed less than before. Version is MT OB 2.8.8.43489. Are you at ISA conditions? 2023-08-18_AJS37_MS_MACH_ISA_with_X-tank_4xARAK_2xRB24j.trk

Good work djacd! *LOL* ... did the same yesterday. I am uploading mine not in a sense of competing, but adding value, for those who like the voice of a "woman" more than a "man" ... Hafe vun! Kind regards, TOViper BASIC_M05__Visual_Landing.miz

With which version are you comparing?

De nada!

yes: 1. in DCS, select the "Display resolution" of your desire (256, 512, 1024) 2. Quit DCS 3. Clear *.fxo cache from user profile 4. Restart DCS and *pray* that it works Post result ...