Lixma 06

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.

Is this the reason I can't hit a damned thing with the Dora?

That would be good business sense. Maybe make the Normandy map free?

I think you missed the sarcasm in my post :)

Wildcat v Zero is fun. Corsair v Zero is slaughter.

Speaking of which.... (no sound I'm afraid) This was caused by a collision during target practice. There didn't seem to be any drag penalty and it only needed some mild opposite aileron to keep it flying straight. The landing could've been better but I like to believe it was because the starboard undercarriage was damaged when the wing got torn off. That's my story and I'm sticking to it.

While cruising around at appx. 4-5k I noticed my airspeed indicator was reading low. I assumed it was icing and after a bit I descended. At this point I began recording the video below. The ASI then fell to zero but soon rebounded back to life. You'll see me in the video looking for something to push, pull, or twist to get some heat into the pitot. I now know that it's one of the circuit breakers but as can be seen in the video the appropriate CB is pushed in - hence this (possible) bug report. I don't recall damaging the wing during the flight and I don't think anybody hit me. I'll do some further tests.

Yeah....I just checked the quickstart manual and Chuck's guide and both recommend neutral elevator trim and a helping of right rudder trim for take-off. This is what happens as you spawn.... It starts at neutral then hurriedly dials in two notches. ED, make it stop.

Same here. I switch on the MW-50 during start-up and leave it on - the only time I've blown the engine was while manually closing the radiator during speed trials. Not saying there isn't a problem but I've never encountered it.

A being from another dimension has just relayed the following message to me....

When you spawn on the runway the Spit will automatically dial in a massive amount of positive elevator trim. I don't know about any else but I immediately wind it back to something like this.... ....or else the plane just balloons into the sky during take-off. Is there a good reason for this?

Sounds good. I'd like to try my hand navigating for an AI pilot. Probably end up bombing Dublin but they'd understand.

Doesn't seem to do anything.