Britchot

I'm not sure what manual they are referring to but this website is a goldmine of information, to include the various attack profiles.

I just flew a sling load mission in the Oilfield campaign two weeks ago, I kept the helo around 150km/h and it was fine. This was a SP mission, which I've heard MP is quite erratic.

Yeah, if they've kept on the same lead-up as the Viper and Hornet, Wags will have a string of tutorial videos just before it goes EA. I don't remember much of a concrete date ever given out, though.

If it is based on the current MiG-21bis module's SPO-10, the direction of an STT is still represented by the appropriate light (2 lights if it's from between two quadrants). Not until the enemy is close will it light up all 4 lights, simultaneously. From tests back in 2019, it would start receiving contacts about 50km (26 nautical miles) away. The early module's SPO-10 was bugged with all 4 lights any time you are locked.

Pilot error. Problem: Stable 2.5 Dedicated Server (that you've been flying OB clients on) will not update to 2.7 when launched. Solution: Download and install actual Open Beta Dedicated Server version 2.7

Disregard, found the issue and solved it.

From what I've seen on Discord, it's in ED's hands, and has been since around October or November of last year. The developers have been very transparent.

Why can we not get this loadout? Obviously, it's documented.

JG-1_Britchot MiG-21

This interview was a great insight to the perspective of a developer. It also shows a great light on this fine simulator that all of us are here to enjoy.

Setting an offset from the TACAN along your landing runway's back azimuth at a distance of 10-12 nautical miles would not be messy, at all. Plus, just turn to TAC and the needle will point towards the TACAN for you to follow in to the runway. Or, if you have a VOR on the same runway, you have the thin needle.

This work is amazing! Any fix to the IC issue?

Great work, love the darker version, it's always blinding to see the bright ones in VR.

JG-1_Britchot - MiG-15bis, please.

Very nice looking skins and I love how the numbers are set by the ME. I have one correction to your narrative, though. I. Gruppe (group) Jagdgeschwader 1 used the black and white stripes and checkerboards. I. Gruppe consisted of 1., 2., and 3. Staffeln (squadrons). These groups used the number colors of white (1.), red or black (2.), and yellow (3.). Your renditions are of 3./JG1 and 2./JG1, the squadrons within I./JG1. The use of roman numerals aren't interchangeable in referencing the different squadrons and groups. This is to not to be confused with II. and III. Gruppen, which did not have these iconic engine cowlings. These groups also had a symbol behind the fuselage cross, which your renditions of I. Gruppe correctly do not show. And great thanks to including a version omitting the swastika.

Nice, good to see more functionality!

Very great detail provided by zhukov032186, just follow his steps. The only thing I haven't seen in this thread of exceptionally helpful people in response to a vague post about issues is to check your keymapping. Even if you haven't changed anything, please check to ensure all the commands detailed above, are working in the options>keybinding.

Please see this thread for some videos of Mirage pilots dropping on CCPL (CCRP) and fixing the problem you are also seeing: https://forums.eagle.ru/showthread.php?t=208695

Didn't use mods, ran repair on the default Russian cockpit numerous times. I will try to switch back when I get home from this trip, thank you.

I would be appreciative of the same limits.

I get it regularly when my DCS is not my active window, i.e. Alt-Tabbed or on the desktop. I find it quite useful to avoid clicking buttons on the HOTAS after changing some sound settings. It consistently goes away when I click on DCS's window.

The effect is probably based on several factors, not just active precipitation. Although, I do find it overdone in IL-2, personally, but not entirely unrealistic.

JG-1_Britchot and LadyBrit will attend.

JG-1_Britchot and LadyBrit will be withdrawing due to the requirement to revert the Open Beta.

I'm assuming you're using Open Beta and hopefully today's patch fixes your issues. However, prior to today (still at work, haven't updated) in OB 2.5.6 with an HP Reverb (plus i7 9700k, 2080ti), I did not suffer items 1, 2, or notice 3. I was able to autonomously lase for GBU-12s and 16s, using my TPOD on STA4 and 5.