Search the Community
Showing results for tags 'engine'.
Found 10 results
-
There are some inaccuracies, but according to the DCS manual, we have the V-1650-7 engine. However, ED lists the wrong engine ratings. The ratings in the manual are for the -3, which needs to be corrected. I have tried finding the engine specs for the -7, but I could only find the ones with unrammed filtered air. The parts with ram air is missing. Perhaps someone has a better chart. I submitted both for clarity. Source for the historical charts: http://www.wwiiaircraftperformance.org/mustang/P-51D-manual-5april44.pdf
- 6 replies
-
- 1
-
-
- supercharger
- critical altitude
- (and 5 more)
-
hello everyone , i have this issue while flying p-47 all gauges in good range : oil temperature CHT Fuel & oil pressure and cowl flaps are fully closed.. & i still get the shaking stick ( inside the cockpit ) is that normal? note : i warm up correctly before take off..
-
Hello! I never seen or knew that this mechanic actually had a model/visual difference in DCS. Just amazing... My questions are now: If the P&W-TF-30 engines made it necessary to diffuse the air into slower meals for the engine to reduce damage to the engine face etc, why does the F-110 GE-400 engines need it, is it just safer and not necessary to remove? Would I be wrong in saying the F-110 has a much stronger ''face'' that the engine simply could have ignored this system? The F-16 has used practically the same engine but doesn't have these ramps, is it because the F-16 simply uses a different solution or never was intended to fly that fast? (solutions like a submerged intake or a twin curved intake, etc)
-
Dear Sirs! I have a problem, and I can't find solution or reason for it. It happened 2-nd time in 2 days. What am I doing wrong? P-47D30 Early Straight flight / gentle climb, without dive. Multiplayer, 4Ya Overlord. -2300rpm -manifold 50 -oil pressure "blue", oil temp "blue", air temp intercooler "blue", turbo about 1400 RPM. loud "kaboom" from behind a cockpit: ["failureDisplayName"] = "Engine #1 erroneous ignition timing induced damage", ["t"] = 10579.065, ["target"] = "P-47D-30bl1", ["targetMissionID"] = "596", ["targetPilotName"] = "=Crow=Kermit", ["target_coalition"] = 2, ["target_object_id"] = 16777475, ["target_unit_type"] = "P-47D-30bl1", ["target_ws_type1"] = 1, ["type"] = "failure", ["weapon"] = "Aw shoot.", second kaboom behind a cockpit: ["failure"] = "ENG0_DAMAGED_BEYOND_REPAIR", ["failureDisplayName"] = "Engine #1 damaged beyond repair", ["t"] = 10579.065, ["target"] = "P-47D-30bl1", ["targetMissionID"] = "596", ["targetPilotName"] = "=Crow=Kermit", ["target_coalition"] = 2, ["target_object_id"] = 16777475, ["target_unit_type"] = "P-47D-30bl1", ["target_ws_type1"] = 1, ["type"] = "failure", ["weapon"] = "Aw shoot.", "boost" throttle goes down: ["failure"] = "ENG0_MAIN_BEARING_DAMAGED", ["failureDisplayName"] = "Failure.ENG0_MAIN_BEARING_DAMAGED", ["t"] = 10579.065, ["target"] = "P-47D-30bl1", ["targetMissionID"] = "596", ["targetPilotName"] = "=Crow=Kermit", ["target_coalition"] = 2, ["target_object_id"] = 16777475, ["target_unit_type"] = "P-47D-30bl1", ["target_ws_type1"] = 1, ["type"] = "failure", ["weapon"] = "Aw shoot.", engine stops: ["initiatorMissionID"] = "596", ["initiatorPilotName"] = "=Crow=Kermit", ["initiator_coalition"] = 2, ["initiator_object_id"] = 16777475, ["initiator_unit_type"] = "P-47D-30bl1", ["initiator_ws_type1"] = 1, ["t"] = 10600.145, ["type"] = "engine shutdown", P-47 CKBWL.log
-
Fresh DCS install, no mods whatsoever. Made a 15 sec track. Spitfire is my absolute favorite. What I describe below is new behavior I'm quite certain. This bug is specifically about the electric starter, not the whole starting sequence. Description. 1) Spawn Spitfire on airfield as "Takeoff from ramp". I.e., engine stopped and cold. 2) Flip open start and booster covers 3) Hit starter button and engine turns over. Release starter button. Hit starter button again, propeller doesn't move. This is what my short track shows. Now the weirdness. This only happens when the first starter button press is very short (less than a second). If the first starter button press is longer, say 5 sec, it will not happen. Also, it will only happen once. Meaning, if I "Quit -> Fly again", it will not repeat. The autostart sequence (Right Win + Home) seems to always work when applied after spawn. But ... if autostart is tried after a failed manual attempt (as in the track), autostart will not move the propeller either. Modules: [I-16] [Normandy 1944 Map] [WWII Assets Pack] [Bf 109 K-4 Kurfurst] [UH-1H Huey] [F-86F Sabre] [Flaming Cliffs 3] [Spitfire LF Mk. IX] [P-51D Mustang] Free Mariana map NOT INSTALLED. Version, latest as of today. openbeta/2.7.16.28111/ Downloaded my track (above) and confirmed it runs as described. Spitfire manual start fail.trk
-
Hi, I'm sure there is some kind of operator error on my part and in the past the P-47's engine was pretty reliable with WEP usage, recently I have been experiencing a brief drop in the engine and a rolling moment followed by an uncontrollable rise in oil pressure with the message in the debrief "Engine Degraded". It happens randomly sometimes during WEP usage other times afterwards when I return to a lower power setting for cruise. Sometimes, I can really abuse then engine and will will tick on just fine for several Rearms and Refuelings on multiplayer until I run out of Water injection...other times it dies if I just tap the water for minute. I'll attach a track that I tried to stay well below 65" for the fight and around 2 to 3 minutes on the 3rd 109, I get the "engine degraded" failure. Pardon the shooting but its the third time I ran it and got similar results. I'm sure it's probably operator error on my part and maybe someone more knowledgeable can set me straight but nearly all my losses since November this year have been due to this and I'd like to know what I might be doing wrong or if it's possibly a bug. I don't have random failures enabled and it happens online and offline for me as well. I have repeated with oil cooler full open and slightly open from neutral and got similar results but random times it fails. engine dead3.trk
-
Hello! When I start up the Mossi from cold and dark (following the manual and checklists from other users) the left engine starts smoking white, sometimes on ground. sometimes in air... It seems there is no temp problem. The right engine has the same temps and settings and is not smoking. SEE SCREENSHOTS: https://imgur.com/a/zvgavU4
-
2.7.6.13133 OB, Mossie engines die no matter what
SmirkingGerbil posted a topic in Bugs and Problems
Load up any free flight, or Mossie mission. Engines die no matter what I try to do to avoid it, almost immediately. All was fine prior to this update. Throttles, pitch etc. mapped to TM HOTAS and stick. Thinking a "problem", and not a bug. Possibly a new mapping interfering? Any help would be appreciated, can't fly my bird. Tried re-mapping, checked Axis controls etc. Trk file attached, happens immediately after mission start. Did I miss something in the change log? Tried instant missions with my P-47 which has similar HOTAS mappings, and all is well with engine management. Any Mossie mission, you get that chugging and stuttering on near full throttle, and one or the other engine will die quickly. Video coming soon - apologies for all the background noise. Had mic on, you get to hear my chair squeaking! Comment will take you to engine failure at 1:09 - engines always drop in RPM on mission start, even with throttles full forward, can see this at beginning of vid. Happens on any mission. MossieEngineshutdown.trk -
The Hornet was designed to be a ground attack/strike aircraft from the design table. It does not use armour to defend itself but rather redundancy of different systems. This extends to the engines as well. With the Hornet soon to be out of EA, I'd expect to at least get an engine failure, or damage of some sort to a single engine on our twin engine jet. This is not currently possible. The damage model treats the engines as a simple block that can only get visual damage. The engines can only be shut down with fuel starvation, or the complete destruction of the jet. (according to my testing and gameplay) Systems such as the avionics already have a simple damage and destruction modelled, which is fun and exciting when trying to RTB with a stricken jet. The bare minimum what I'd love to see done to the engine damage models: -Possibility of seperate engine damage/destruction from external threats -Visual damage seperation (right now the visual damage treats the engines as a single block from the bottom) -Engine fire from exteral threats -Reduced thrust from damage -The ability to create failures to a specific engine from the mission maker Other nice-to-have but not neccessary things: -Vibrations from damage -Fire spreading to the other engine (a real threat with the engines near each other) -Generator failure -Fuel control system failure -Oil leak with a black trail All of the bare minimum things are already in the game with FC3 planes and some FF modules such as F14 and A-10C.
-
Hi everyone, I've noticed a minor bug which has been present since the release of the F-14A. According to the pilot procedures in the manual, step 6 is to check to see if the start valve caution light illuminates prior to advancing the throttle to idle during engine start. Since the release of the F-14A into OB, it doesn't illuminate and never comes on (excluding the LTS test) prior to setting the starting engine's throttle to idle; what happens instead is when the engine crank switch returns to centre at ~50% RPM, the start valve caution momentarily turns on for a split second before going out - it's a very quick on/off and it basically perfectly coincides with the engine crank switch returning to centre. IIRC what used to happen is you'd position the engine crank switch to start whichever engine, then I think somewhere between 10-20% the start valve caution light would illuminate, at 20% you'd advance whichever throttle to idle, and the start valve caution light would turn off when the crank switch automatically returns to centre at ~50% RPM. This problem is present in both the F-14A and F-14B. Track attached. F-14A_Start_Valve.trk
-
- 1
-
-
- start valve
- f-14
- (and 1 more)
