TOViper

Hey folks! Please don't forget to add bugs/issues/errors of the RC2.1(beta) manual to this thread. Deadline for reports is the 30th of December 2022 in order to have changes implemented in RC2.1. Thanks and happy flying, TOViper

@whisky.actual Seriously, I can't wait to fly the new version of the Gripen MOD. I even started physical traning in order to sustain the higher g's and roll rates of this bird in comparison with the AJS ... Can you estimate in ... let's say months from now for the new version to become available? Anyway, happy XMAS + modding

OB 2.8.1.34667 SP The argument 165 (STD flag of the main altimeter) is faulty: .) If the STD flag is not visible, the argument is 0 (which is correct). .) If the STD flag is visible, the argument 165 appears as empty and not 1 (which is a bug). Furthermore, once the STD button is pressed for the first time to have the STD flag visible, and then pressed to have the STD flag not visible, the triggers show that the flag 165 is somewhere between -0.1 and 0.1. HB, please make this flag to work correctly (to reach the value of 1 when the flag is fully visible and exactly 0 when the flag is not visible). If you wanna try out, I attached a small mission with 3 triggers. Thanks and kind regards, TOViper AJS-37_Viggen_id165_failure.miz

Hello Machalot! Initially, I am not 100% directly answering your question, but - at least - the other way around in order to separate the two systems 1st point for me is the following: Referring to SFI Flik 13, sida 8ff, where the indicator is explained. I can see no indication in the book, that there is any direct connection between the Reservekursanläggningen and the Potentiometer KURSKORR, neither in the description, nor in the drawing (-3959 O-1). 2nd point for me is the following: Referring to SFI Flik 20, sida 3, where the schematic is shown. There is no indication in the book, that the KURSKORR (which can be seen on the most left side of the schematic), is connected to the Reservekursanläggningen (which is not part of the schematic at all). Now, coming back to your question: The schematic on Sida 13 (-3959 DY) shows the KURSKORR (bottom, mid) and how its signal is fed into the system. FYI: For answering your question, I again quickly overflew the text of Sida 3 - Sida 13, and it (again) gives me no indication that there is a connection between the Reservekursanläggningen and the Potentiometer KURSKORR. My first reading of this chapter was a few weeks ago, when I started to revise RC2, but to be honest ... right at that time I was sick and had fever, so seen in hindsight things might have appeared differently then ... But anyway, thanks for digging into this at that level ... SFI_FLP_AJS37_Del1_1994-11-15_Kap_I_Beskr_Flik_13_Sidas_08_09_10_translation.txt

Now in OB 2.8.1.34437 the KURS indicator works again. The implementation of the course correction dial is still wrong, because when turning, it turns the standby compass (KURS), but it shouldn't.

True. A slight speed up would be good, though ...

Maybe interesting to all Viggendrivers who think their Mavericks are not working: They need a warm-up time of (I think) 3 minutes before they can be used. What I am asking myself is from power up (electrical system online), or wheels up after lift-off?

Me Update by HB

OB 2.8.0.33006 SP Caucasus If flying slower than M0.8, the standard turn radius (turn initiated by the trim hat switch left) is not 4.1 km (as stated by RC2) but 4.9 km, see screenshot and TRK. The Initial course before the turn was about 075°, after the turn it was about 255°. The distance from the point where the turn was initiated to the point where the turn ends is about 9.9km, which is 0.8km too much. 2022-12-14_AJS37_Standard_turn_radios_wrong.trk

... what happened to forum user @corvinus ? I would like to contact this guy, but unfortunately he seems disappeared, last contact was in 2019. Thanks for any hints! TOViper

DONE 2022-12-06

*LOL*, I already thought it would end in some complicate stuff. @Aenonar, can you provide a solid track of the happenings. This should help the guys here to see what you describe ...

"especially if unaware of the met convention" < That's the problem for this long term story.

1. "BLOWS TO DIR" is the *sorryforblamingED* totally-OFF-any-world-standard-met-information regarding aviation. Its a ED thing. In aviation, wind is always referenced to "where it comes from". At least, the ME says where the wind is blowing to. The CK shows 270, which is correct. The 33 is not correct, it should read 36. 2. Are you sure Doppler works at 2000 meters? If not (which I am pretty sure it doesn't), a forecasted wind is put into the CK when the aircraft is spawning. Maybe at this stage something goes wrong with the 10% error. 3. "Aircraft is flying north with the wind coming from the right while the SI says you're drifting right as the CK37 thinks the wind is coming from the left." Considering 1. and having in mind that Doppler wind in the Viggen is in the standard-aviation-met system ("coming from"), this statement is wrong, the aircraft behaves correctly. I can see that in the RC2 there is not even one hint that the Viggen uses another reference system for wind. As said, the "blowing-to" is an invention by ED, which makes absolutely NO SENSE. It caused and still causes headaches of people, and costs so much usesless time and efforts...

@hilmerby How tall are you?

There is definitely the wrong frequency set for the wingman's radio. Also, the briefing should say "Special channel 1 (305.000MHz)", currently it is only reading "Special channel (305.000MHz) Also, the ATC is clearing the flights for the wrong take-off runway, which should be 07, not 26: 1. RWY 07 is what the mission desinger had in mind 2. RWY 07 would be correct according to the wind setting in the mission (meteo wind 080° with 2 knots) @IronMike I think it's time to re-check all campaign missions to compensate for any changes in the DCS core that came with the last updates since March (the campaign was last changed on 17th of March 2022). The problem described here can be easily repaired by assigning 305 MHz as the frequency for the Viggen flight instead of 124 MHz. 2022-12-05_AJS37_Mjolnir_Response_Misson_1_Take-off_runway_wrong_RadioWingman_wrong.trk

OK folks, I re-assembled pages 174-176, please go through it and give me feedback: DCS_AJS37_Flight_Manual_EN_RC2.1_re-build_Version_2022-12-05_pages_174-176.pdf

Hello Shibbyland, welcome to the Viggen world! Which campaign are your refering to? Mjolnir?

Myse1234, in which way does it currently not work correctly?

On which page in the SFI did you find this?

9 hours ago, Machalot said: I can't figure out the difference between time error on target and timetable deviation. @IronMike Maybe you can take a look and hand this over to the author of this documet, or even explain it. I assume its the same. 9 hours ago, Machalot said: What does it mean when a Bx point is selected and it calculates time "for the previous waypoint in the polygon"? What is considered previous? I have no f..... idea.

Hi Viper99! Can we find infos related to this function somewhere, maybe in the SFI? In this case, which page?

For the moment I re-phrased this part on page 174 in the following way (also consider the last part about Indication) : null

Vettefan, which radar mode are you using during usage of the EP? A0 or A1 or A2? A0 would be black on white, A1 white on black, A2 automatic. Maybe this is the problem you are running into when your controls are synced?

Guys, is the bold text clear to you? See RC2 page 174: "Flying time to target serves as a reference to time error on target calculations and is only presented if no time on targets are set. If a time on target has been set, a timetable deviation is presented instead." IMHO, the last sentence should start like this (changes are in bold now): " 'Flight time to target waypoint' serves as a reference to 'time error on target calculations' ..." You agree?