Lixma 06

Yes...all this happens in the simulation. We know this already. The question remains - is it realistic? If 'our' P-51 was sent into combat there would be a placard in the cockpit that read 'AVOID VERTICAL MANEOEUVRES LIKE THE PLAGUE'. I think if your engine is liable to explode after three seconds of reduced speed during combat you'd want to know about it - and then ask for a transfer to the P-47.

That's what everyone has been doing - but it doesn't mean there's isn't an issue. Thanks for taking a look, though.

Which is a red flag in itself - A brand new P-51 on the edge of exploding after barely thirty seconds of Military power?

@NineLine I think Reflected beat me to it by minutes (curse him and all who sail in him!) but here's a couple of easily replicable examples from an air start. Procedure - 1: Full military for about 30 seconds 2: 60° climb 3: Cut throttle at 150mph and watch the temps - blown radiator every time. p-51 blown 1.trk p-51 blown 2.trk

In the P-51 checking your six requires a turn + lean movement, whereas in most (all?) modern DCS modules the leaning is already built in. Here's a comparison between the P-51 and the P-47. Can we get an 'auto-lean' option, perhaps in the special tab?

Quick vid - I let the needles stabilize then ran it up to approximately 'max continuous' on the ground (couldn't go higher without tipping over). The temps (coolant & oil) both increase, but only gradually. Then I do a few climbs. Near the top I throttle back (certainly less than power than I was using on the ground) but you can see the gauges shoot up vastly quicker than when I was stationary. I pop the radiator on the third one. It's possible I damaged the radiator during the ground test, but the main reason for the video was to show the lightning-fast temperature increases during flight.

The biggest killer (for me) in the P-51 is when you attempt, during combat, some variant of a wing-over or stall-turn. The temps will skyrocket to the point of blowing the radiator in under three seconds if you get caught in a low speed manoeuvre.

The cooling gills might as well not be there....makes me wonder.

This is on the Marianas map - 40°C max in the mission editor. Ran the test again and the temp reached 102°C (limit on gauge is 95ish) and stayed there until fuel ran out - 51mins total test time.

I don't think it was the anti-virus because DCS was running perfectly fine for the few days after I migrated to new SSD before the patch. After the patch the only modules I could use were those I installed specifically in DCS's new home on the new SSD.

Utilizing the active pause function (in lieu of chocks) I ran the engine flat out (1.42) on the ground for 25 minutes, and the max temperature was 82°C. This strikes me as....optimistic? a-8 heat.trk

Brilliant - thnx, Mud. -- Rudder Trim Wheel { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = -1.0, name = _('Trim Rudder Left'), category = _('Flight Control')}, { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = 1.0, name = _('Trim Rudder Right'), category = _('Flight Control')}, { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = -0.5, name = _('Trim Rudder Left Slow'), category = _('Flight Control')}, { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = 0.5, name = _('Trim Rudder Right Slow'), category = _('Flight Control')}, Passes IC too.

I think this is the trouble I was having - during a fight I'd normally just throw everything to max (i.e. 72") instead of holding it at 64". You can get away with max throttle/boost/everything on the deck, but above 100m everything starts getting complicated - god knows why. I'm not convinced the turbo should behave like it does. Lag is one thing, but I see no reason for the turbo to spin up uncontrollably when you're flying straight and level with no throttle changes.

Great catch, fellas.

There's a few threads on this - the turbo will suddenly surge (don't know why) drastically increasing the manifold pressure, and causing terminal damage if not quickly noticed and brought under control. I've just had an awful couple of flights online with mysterious* high-speed vibration and engine failure while boosted. *I'm pretty sure I followed the book on everything, but still....

This type of crash has happened a couple of times to me recently, but I can't honestly remember whether it was during an Anton session (I have been flying it a LOT, though). The symptoms sound familiar; requiring me to terminate DCS via the task manager.

I've had trouble with DCS forgetting my P-51 bindings - I've never sussed out the reason, but the moment I realise it's happened I just shut down DCS and on the restart it's all back to normal. If separate controls for all variants solves this (or just merging them in to a single P-51 entry) then +100 from me. Re: P-47 - there's only one folder 'P-47D-30' which seems to cover all variants.

Other WW2 sims (no names, no pack drill) have a convincingly bright, and tactically useful, sun. Here's a couple.... DCS looks like this.... I know it can be improved (slightly) by enabling 'Flare' in the options....but a) that's a photographic effect and b) it can be turned off by the client. Please ED - a nice blinding sun to hide in, or get murdered from.

Thanks, LC!

Cage is there.....but no uncage?

The elevator and aileron are fine but the rudder is much too fast for me. I guess they've coded it this way to quickly trim out the huge torque when you go flat out. Is there an .lua edit that will dial it back a touch?

Thanks to Phil et al - hope you change your mind, it's a shame to lose a great server, especially at the height of its popularity. Good luck on your next project.

OK, I deleted all the modules then let the moodule-manager re-install them - seems to be fine now. The TF-51 needed a repair thingy but fingers crossed everything is back to normal. Note to self - migrating DCS to another drive isn't as painless as just copy 'n' paste.

It's not only these modules unavailable. Module manager says all modules installed but they're not available in-game. I moved my installation to a new SSD a couple of days ago - might that be the issue? Up till the patch everything seemed OK. I noticed the terrain modules I installed after the migration are available to use, while everything else is locked. Is there a way to re-activate everything or is a full re-install needed?

It's not just the Spitfire. DCS graphics are constantly evolving and the textures and techniques used on aircraft a few years ago tend to react a bit weirdly with the current lighting. And so there's a constant call for modules to be re-textured to take advantage of the latest tricks.