Jump to content

Lixma 06

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Lixma 06

  1. How many contradictions does it take? What difference does it make if they are de-leading the spark plugs or just burning off fuel for fun? Do you honestly not see the contradiction between the real P-51 sat happily running 61" 3000rpm at 0mph for at least a minute without any prospect of damage, and our P-51 overheating and exploding within 30 seconds under the same conditions?
  2. With respect NineLine - We all know this. Everyone in this thread, and online, knows how to avoid breaking the P-51's engine. There's no mystery, it's common knowledge. But having the knowledge to fly 'around' an issue does not mean there's no longer an issue. Nor does flying around an issue mean you're flying 'properly'. The issue is our P-51 has an engine/cooling system that goes from OK to CHERNOBYL within seconds; behaviour that's contradicted by the aircraft's own manual.
  3. But the actual P-51 manual states it's shouldn't be an issue. If you can harmlessly hold 61" 3000rpm for a minute at zero mph where's the problem with stall-turns? There's nothing special about stall turns, in fact they're a lot less stressful than the above ground test as there's a lot more airflow through the radiator.
  4. Can you honestly not see why the ground test is relevant to the issue? The P-51 manual states it is safe to run the engine for at least a minute at 61" 3000rpm at 0mph. And it does no harm to the engine whatsoever. Our P-51 cannot survive 30 seconds doing this, whether on the ground or in the air.
  5. The P-51 manual states that to de-lead the plugs (or annoy the neighbours, or impress one's girlfriend) the engine should be run up at 61" & 3000rpm for one minute prior to take-off. The unstated, but obvious conclusion, is that the P-51 can safely run at 61" 3000rpm at 0mph for at least 60 seconds without any risk - if it was likely to damage the aircraft they wouldn't recommend it; especially not prior to take-off. In contrast our P-51 overheats and explodes within 30 seconds. Now to slay the 'active pause' demon. If anyone else wants to try this you just need to pull full deflection on the elevator, full brakes, and very gently increase the MAP. I couldn't stop it rotating but it doesn't matter. Result: Exactly the same; in fact the engine was blown before I could reach 61". LOL. I am reminded of Baldrick from Blackadder, who famously solved the problem of his mother's low ceiling by cutting off her head. p-51 ground no ac-pause.trk
  6. The switches were in 'Auto' and I wouldn't expect it to make any difference - but just to make sure (Science™) I ran it again with both oil & coolant shutters wide open. No real difference - maybe 5 seconds extra before it blows at 8:01:41 p-51 ground 2.trk
  7. Here I let the temps settle for a minute. At 8:01 I run 61" 3000RPM and hit active-pause (just before the plane tips over). Result: Radiator blown in under 30 seconds (audible at 8:01:31) p-51 ground.trk
  8. 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.
  9. That's what everyone has been doing - but it doesn't mean there's isn't an issue. Thanks for taking a look, though.
  10. Which is a red flag in itself - A brand new P-51 on the edge of exploding after barely thirty seconds of Military power?
  11. @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
  12. 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?
  13. 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.
  14. 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.
  15. The cooling gills might as well not be there....makes me wonder.
  16. 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.
  17. 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.
  18. 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
  19. 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.
  20. 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.
  21. 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....
  22. 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.
  23. 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.
  • Create New...