Lixma 06

Just replayed your track and didn't see any flickering on my machine.

This is after today's update. (It's been happening since 2.5.4) Non-VR (and luckily nowhere near as bad as others are experiencing) FXO and Metashaders deleted and rebuilt (shouldn't the updater be doing this automatically?). Running nVidia driver 417.71. I've tried re-creating it (I thought it might happen at some specific angle to the sun or whatever) but I've had no success.

The Mig-15 thing took 18 months.

I was flying around in the Mustang for about an hour with no problem - I jumped into the Mig-21 and within a minute it happened.

Just to muddy the waters a bit....I've been flying around for about an hour and haven't *so far* seen a black flash. My water is full(!) and I'm running an nVidia card. Non VR. e: and there it is - bug is still there

I think this line might be referring to the black flashes

It's horrible - trying to maintain a gentle turn and you're bouncing up and down because you're constantly triggering the 2G bump. e.g.

Which can form the basis of a Korean War variant.

I think it's more or less useless above 6k.

Try it at night....place lights up like a Christmas tree! Only happens with shadows set to 'Off' or 'Flat Only'.

+1 A dim/red kneeboard/map/text etc would be great for night flying.

You want it right at the top. The centre should be visible in level flight, and if it isn't then you need to adjust your position, but the lower the pipper is the less room you have for leading the target.

Thanks for the info. I suspected it was LOD related (the boundary where the shadow becomes less crisp is where the head is revealed) but I thought it was part of the aircraft's 3D model. I've tried editing the Shadows.lua previously to tidy up the in-cockpit shadows but it wouldn't pass the IC.

Seems to happen with all aircraft.

I'd rather have shadows on than off but ever since 2.5 the terrain shadows (both 'flat' and'default' flavours) have become very dark, overly detailed, and seemingly immune to any kind of anti-aliasing. You can see this best (or worst) at low altitudes where an oblique viewing angle turns shadows into hundreds of competing pitch-black lines shimmering like crazy. Maybe it's not so bad with 4K displays but at lower resolutions it looks terrible. Be nice to replace them with something softer.

First go into Options/Misc and make sure User Snap-View Saving is checked. Hop back into the cockpit. Then.... If it's just your default view you want to save (which you say is NUM-5) then simply adjust your position until you're happy then hit RALT-NUM-0 to save it. If you want to save more custom views then.... 1: Decide where you want the custom snap-view (which keypad number) - let's say NUM-3 2: Hit LWIN NUM-3 - the view will jump to whatever is currently stored in NUM-3 and jump back to your default view. This 'primes' NUM-3. 3: Now, move your head and manipulate the FOV to find your preferred view. 4: When you're happy hit RALT NUM-0. This should save your view into NUM-3. 5: Go back to your default view (NUM-5 traditionally) and test whether hitting LWIN NUM-3 brings up your custom snap-view. Hopefully it should.

In Options/Misc see if this box is checked... It was introduced, and enabled by default, in the last patch.

Check here.... https://forums.eagle.ru/showthread.php?t=228793 Maybe ED will look at why it's happening.

Excellent, thanks for the tip, LC. Passes the IC too.

From a fresh aircraft the boost switch is switched off. OK, that makes sense but shouldn't the D-9 behave similar? Or are they different systems?

Why?

Could you reduce the gain on the altitude adjustment rotary as LeCuvier mentioned - it's impossibly fast.

Well, speak of the Devil - the Dora's engine just seized on me during MP. No idea why - I'm really conservative with my engine. I had two sorties punctuated by a hot rearm & refuel. Total MW-50 time must have been less than a minute. Cruising back to base during the second sortie the engine just popped. I think I saw the coolant temperature gauge off-scale to the right as I ditched the plane but I don't know whether the needle was there prior to the engine stopping or only happened when it blew. I have the track but it's 90mins or so and accelerating time wrecks it. When I get time I'll try 'taking control' during the second sortie and see if I can capture the engine failure on video. edit: well, scratch that idea. The track replay is perfect right up until I take off for the second sortie, and then within a minute I plow into the deck. And anyway you can't take control during an MP track....:doh:

Happened to me a couple of days ago. It was OK one minute then I loaded up a different mission (Normandy) and the controls had been reset. Re-loading DCS did not help so I had to import my back-up Input folder. There's a similar issue with the P-51... https://forums.eagle.ru/showthread.php?t=228733 I wonder if it's because both the Spitfire and the P-51 have two variants but are using a single control scheme?

I think that's why BoB and Pacific tend to be much more entertaining in theory than in practice.