TOViper

Update 2023-05-17: .) page 21: Item 6, separated Central indicator and Radar display from each other .) page 63: shifted blank page to position 61, now page 62 and 63 are besides each other when printed double-sided .) page 126: reworked U22 ECM pod .) page 226: reworked RB75 .) page 342: added note about BK90 <500m doctrine Have to leave the desk now until late evening. Hafe vun!

Hey! Can I unhide my hidden posts?

Consider it done, looks like this: null

Hey Buzzer! I will change the title accordingly ... thanks for your input!

Whatever they do, I will try again (maybe) in 6 months, because the trial expired already ...

Still work in progress, but I think in July - once I find a minute - I will start over ...

Hey Zabuzard! Two question came up during reading: 1. Did you consider fuel flow too? Following the information given in the manual, there should not be fuel flow to the internal fuel system when the light is on due to missing tank pump pressure. 2. Do you know why the Tank pump switch TANKPUMP (NORM / AVST) on the right wall console was not modelled? Thanks and kind regards, TOViper

Openbeta (the version that was the newest one as per 23th April 2023) MT MP Nevada AI F-15E wait behind tanker for refuelling, and they fly into each other but don't collide. TRK file too big, MISSION file too big.

Hey Big! I have Normandy in trial, but looks like its not having textures in London. Attached find my log and a screenshot from today. dcs.log

I can't wait for the release of Kola. This will most probably change my life again (as the Viggen did ...).

Beautiful! It's a great pleasure to see that the Viggen becomes polished more and more.

Yup. De nada.

Update 2023-05-11: .) page 338: replaced AKT POS / IN with AKT POS / OUT @Zabuzard thanx for the info!

Hey Mik! See RC2.1 manual page 253, section BANA / GRÄNS: .) Go to BANA / GRÄNS .) Chosse IN .) Type the heading, e.g. 2530 for 253.0° (you can forget about setting a TILS channel) .) Press LS Considering the runway was already entered (e.g. Ramat David), then this should work. If you have to use corrdinates for a runway for which no code (e.g. 9013) is available, you might use reference points or type in coordinates by hand via REF/LOLA.

Taxi from ramp to holding point in master mode BER. Once on the holding point, or even better once aligned on the runway: switch to NAV and check runway heading with NAV system (BANA GRÄNS). You then have two minutes to throttle up and become airborne, otherwise the bay becomes too hot. I don't know if its modeled in DCS, but that seems how the real Viggen behaved obviously.

Update 2023-05-10: .) page 46 and 48: added indicator and warning panels .) page 342: slight changes to text

thnx for clarification!

Hey Zaburard, I am a little confused now, thus I am asking: Does this mean the codes 91xxxx can be used and approach height works after the next patch?

Hello Money! Make sure you go through all NVIDIA control panel settings again, just to make sure they are still set correctly (e.g. get rid of setting "Optimal power", etc.) Also make sure the second tab for application settings shows no other settings for DCS.exe. I delete all user settings during installation of new drivers, so I have to go through them again, and therefore they are set for sure, and I cannot forget anything. Plus Rudel's tip too....

Will change RC2.1 accordingly once patch is released.

Yup

I was able to land RWY 07 with ILS. Localizer came in range before glideslope, everything seems fine. See track 2023-05-08_F-16C_Landing_Kutaisi_ILS_RWY07.trk. OB 2.8.4.39731 MT Caucasus Mission Editor Single aircraft edit: I did a second flight, this time at wind 250/06, and Kutaisi turns off the ILS (2023-05-08_F-16C_Landing_Kutaisi_noILS_RWY07.trk). 2023-05-08_F-16C_Landing_Kutaisi_ILS_RWY07.trk 2023-05-08_F-16C_Landing_Kutaisi_noILS_RWY07.trk

Or just lack of reliable material...?

A little help here: Look at the thrust equation: Thrust equals Mass flow times (exhaust gas velocity minus true airspeed) The problem is: the faster you go, the less thrust you have (actually forgetting about RAM effect). The RAM effect gives you a certain amount of re-compression of the air when it hits the inlet (IIRC goes with a quarter times (1+Machnumber)^2), thus the thrust minimum at medium Machnumbers is preventing further acceleration due to already large aircraft drag (increased by a2g loadout). Once the engine "feels" enough RAM re-compression at higher subsonic Machnumbers, the thrust might then be enough to compensate for the higher drag at higher Machnumbers. It now STRONGLY depends on how high the aircraft drag really is (very difficult to predict, must be measured during flight test) and how good the re-compression of the inlet works. Obviously, in DCS Viggen these two values (total drag versus thrust) are the same at M0.8 for that configuration which you figured out.

Update 2023-05-08: .) page 343 (BK-90 input codes 91xxxx VALB/STD for approach height: [currently no function in DCS])