Usagi

I managed to get AI indicators to the main screen by changing local shift_X = -0.9 to local shift_X = -6.1 in file <DRIVE>:\DCS World OpenBeta\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua Which I guess, moves that indicator by 6.1 x it's width from the right edge of screen. However, there's indicators that I cannot even see in the screens. They're visible only in screenshots, like the Cargo Indicator and Yaw-Pitch-Roll indicators. I really don't know why they show up only in the screenshots, not in my live screens.

I have kind of a similar problem as I use multiple displays but those extra displays are reserved for MFDs and gauges displayed via Helios. With Mi-8 at least AI gunner panel and Cargo panel will always be at those displays - and when using Helios, under the gauges. So far I couldn't figure out how to move them to the main screen. Example how it's now: I have 2560x1440 as main screen and two 1920x1080 displays on the right side of it. DCS will throw most overlays just to the right edge of my rightmost display. Some I have fixed (like a kneeboard) but some seems to be much harder to fix.

I am was too. When coming to outpost 14, I switched to R-828 channel 1 and my pilot tried several times to contact outpost via radio. Then he just said 'That's a roger. 245.' - but I could not hear or see any messages that tells what to do.. Eventually I tried to land at that outpost, then I realized that there are also 14b and 14c nearby, flew to them and near one of them navigator yelled MANDPAD! and there was explosion really near. Landed on that outpost and mission worked from that point onwards.. Until the famous exploding trucks. I found trucks, reported them and then nothing so I was careful and after a quite long circling I realized that there was a makeshift helipad marked with a small flags. Landed there, picked up guys and some cargo, took of (away from trucks) and then everything exploded. After the explosion, I got ton of messages concerning tripwired trucks - like that I had missed some trigger that would show them? Too bad that there's some trigger problems as this is first campaign that I have for this map and campaign itself seems to be very interesting.

After I figured my initial problem out (My collective didn't go to full zero), I almost managed to pass first mission. However, I ended up at the Hospital's parking area with broken helicopter... SPOILERS AHEAD: For some reason, the official helipad near Hospital didn't work, instead the landing operator (guy in white clothes) was standing at parking lot near by. I managed to land there and patients from my helicopter were successfully transported to the truck and then to the hospital - however in that tight space I managed to hit a lamp with my main rotor... Should it be that way? I was expecting that helipad would be the destination. I had also some problems with first hospital, I had to land several times until it was registered. Does the red circle on the F10 map designate the proper landing area or is it just some other dynamic mark that happens to be near landing area by accident?

This track shows how it usually goes during mission when target location is more or less unknown and there's no long preplanned attack path. The sight disappears so quickly under the HUD that bombing goes south immediately. ajs37-bomb-anf.zip

Yesterday I flew randomly at Sinai map and found these helipads - with lights! So some civilian pads has lights, at least at Sinai map (I don't know are these more common assets).

I really do something differently. Watched that track many times and flied same mission. Still, often when I unsafe trigger, the sight will drop below HUD so I just cannot see range indicators. So level bombing is much ruthless for approach as I really don't see what I do differently when I got sight successfully compared to when it drops immediately down. Plane's pitch? Is there limit like +/-1 degree?

Hi, QFE is set properly. Is there now something fundamentally wrong with my approach? I have bombed usually from NAV mode with SJÖ/PLAN setting, using radar altitude. Enter shallow dive, unsafe trigger and keep target in the sight (which does not appear any more). Alternatively I have used ANF mode, put target on sight, trigger unsafe until sight flashes and then release bombs. Now the sight just goes under nose. I get better success when flying around 150 - 200m above target but then I will be immediately shot to pieces. The safety height settings seems to be usually at medium if that has any effect.

I eventually reinstalled everyhing and the result is still same. In NAV mode there's no more sight available (when trigger is pulled to 1st stage, arming the main trigger) and in ANF mode, the sight falls somewhere below the screen. Currently my flying with AJS-37 is on hold as missions in campaigns requires bombing. I really hope for fix or clarification how this should work now?

One binding that is missing is fuel cut up and down. Currently there's only toggle switch and I am using physical levers for these and there's no way to configure them like for example in ka-50 or in many planes.

Landing at FARP at night or very poor weather is really hard or almost impossible as there's no mechanic for setting up some lights for helping approach. Even spotting a FARP is really hard and sometimes requires a lot of circling and if you are not in exact place, it's impossible to found. If not automated, at least by contacting FARP via ATC menu, there should be option for some guidance lights.

The switch on the left wall near landing/taxi light switch is on by default.

Is there some changes with weapons or delivery of them? I have flown with viggen last couple of weeks and now after patch I have had a lot of problems especially with bombs. For example, when in NAV mastermode and Bomb/Plan delivery mode, there's now no sight. When in ANF mode, the sight seems to behave differently and more dive is required?

Just guessing here, but Viggen had only greenish phosphor in the CRT thus circle and other markings just could not be other than green or black so current representation is better than previous in that sense. EDIT: Ok, the circle is still white in cockpit and in exported viewport if brightness is enhanced to usable level (normally it's either way too dark or cockpit radar too bright):

I will try this too (2D user) as currently ghosting with TAA (DLAA) is so massive. Even head movements with trackIR causes ghosting from cockpit structures. All fine details like masts and powerlines are gone. Strangely I didn't have those problems when first version with DLAA came at October. Only later.