Search the Community
Showing results for tags 'spitfire'.
-
Just noticed the four downwards sticky pins and suddenly grasped their purpose (or so I believe). The compass "sticks" at any significant bank or pitch preventing compass accumulating spin momentum. Real (glider) compasses I've seen, spins on turning (a glider turns all day long...) and keeps oscillating after straightening out. It's unreadable while turning and 30 sec or more after. But whenever the Spitfire turns (banks) the P8 compass sticks", doesn't gain spin momentum, it then unlocks at straight and level, making for a more sedate settling. Made a video, external view and compass splitscreen (two DCS Replay recordings, frames synchronized). Video White cross is north. Compass is free on takeoff, sticks on ascending left turn, unsticks at level [1:37], sticks (flips twice) while rolling. Sticks/unsticks intermittent right descending turn before landing. Funny it doesn't stick at -43 bank, but giving benefit of doubt to modelers, it's more complicated than angles, there's also acceleration. Note, pitch and bank are very readable center of video for comparison (after YT gets focused at 15s). Note to self (and interested) making the video Command line FFmpeg is a very versatile free open-source Swiss knife software for video editing. One would think GUI packaging of FFmpeg like "Handbrake" would include menued templates for common things like splitscreen. It doesn't. FFmpeg is the simplest, if not only, free tool I found for this. It's akin to linux or dos scripting, powerful, terse, complicated, incomprehensible... Anyway, found templates online to adapt. Recorded DCS Replay with Xbox Game Bar [Win + G]. Used click "Fly" scene-shift to synchronize, that's why they're staggered. Obviously couldn't click "Fly" at the exact same millisecond both videos but single stepping MPC-HC video player to scene-shift and then go "MPC-HC -> Navigate -> Go to..." gives the current video frame (and millisecond). 43 - 36 = 7 frames. Also, Right-click MPC-HC time display "High Precision" gives milliseconds. Found (adapted) command online: ffmpeg -i video1.mp4 -i video2.mp4 -filter_complex "[0:v]null [left];[1:v]tpad=7:start_mode=add [right];[left][right]vstack" Spitfire_compass.mp4 The relevant part is "vstack", stack vertical and "tpad=xx", delay XX frames. I'm sure this includes redundant syntax. Just: ffmpeg -i video1.mp4 -i video2.mp4 -filter_complex vstack video3.mp4 will vertical stack videos ("hstack" horisontal) but what's the correct syntax to add "tpad" delay? I copied and adapted something that works including redundant syntax. -
12/16/22 Preface: In this Friday's OpenBeta update, the easy coding fixes have been added for the P-51, 190s, Spitfire, 109, and 47. However, the Mosquito has been missed. Additionally, the armor plates that are missing from DCS entirely haven't yet been included. Items that were fixed in the 12/16 OpenBeta update will be highlighted in green, and marked with the update date. TL;DR: Many warbirds have incorrect armor values, or are missing armor. If you open the x-ray.edm in the Modelviewer, and the individual aircraft's Lua, you can see the IDs from the Modelviewer and see what those objects' properties are. Please click on the photos here, as while I've minimized them in this post so it doesn't get cluttered, but if you click on them you will see them in better resolution. The P-51D (INCORRECT): [FIXED: DEC 16, 2022]The headrest and seat back armor (aka XArmor01 and XArmor00) - If we open Aircorps Library and look at the drawings for the late P-51D, like ours, we will see that these are two pieces of armor welded together. The headrest being 7/16", or 11mm...and the seat back being 5/16", or 8mm thick. Meanwhile in DCS, it is given a thickness of 22mm! For both plates! Almost three times the value of most of the area of the armor. I have an idea on how this value came to be, but I'll drop it into the spoiler below: [FIXED: DEC 16, 2022]The armored glass (aka XArmor02) - In DCS, it is given a thickness of 75mm. Using the schematics from Aircorps Library, we can again see that it is 1.5" thick, or 38mm. [FIXED: DEC 16, 2022]The instrument panel (aka XCockpitElement02) - In DCS, this is given a thickness of just 1mm! In truth, the instrument panel is a part that's for once, thicker in truth, coming out to 0.128", or 3.25mm. [FIXED: DEC 16, 2022]The firewall (aka XArmor03) - This is given a value of 12mm in DCS, or just a scratch under 1/2". For our 51D, it appears that a more possible value would've been 1/4", or 6.35mm. The P-51D (MISSING): The coolant header tank armor - This is a piece of armor that has been missing from the Mustang's damage model. It is 1/4" thick, or 6.35mm, and lies just forward of the coolant header tank within the engine nacelle, between the coolant header tank and the spinner. In summary for the P-51: -[FIXED: DEC 16, 2022]Change XArmor00 from 0.022 to 0.008 -[FIXED: DEC 16, 2022]Change XArmor01 from 0.022 to 0.011 -[FIXED: DEC 16, 2022]Change XArmor02 from 0.075 to 0.038 -[FIXED: DEC 16, 2022]Change XArmor03 from 0.012 to 0.00635 -[FIXED: DEC 16, 2022]Change XCockpitElement02 from 0.001 to 0.00325 -Add coolant header tank armor. Steel, 0.00635
- 29 replies
-
- 10
-
-
- protection
- dcs
- (and 17 more)
-
This video represents the fulfillment of a four year vision and a celebration of the accomplishments of the amazing AuthentiKit community. if you’re already an AuthentiKit fan, you’ll also see a sneak preview of the new second generation flight stick. It’s a lot better.
-
- 4
-
-
Can anyone tell me how long it normally takes a reported issue normally take to rectify? After an update in July the Spitfire VR hands control stick grip became non functional. I reported this to ED and they confirmed this was problem and I've been waiting ever since. I like using the VR hands it works so well on Oculus Quest via Steam and would buy more modules but I'm reluctant because of this.
-
.thumb.jpg.fab6819b47c2136bb075253c904b9aae.jpg)
I’ve flown WWII flight sim’s since 1996 and spend the majority of my “sim time” flying, as opposed to engaging in combat. I recently started to work through the Spit’s “instant action” missions and the one that has really got me stumped is the “Landing” mission using the Channel Map. My problem is that in perhaps 90% of my landings the Spit’ rolls along nice and smoothly (after landing) and then pitches forward into the ground … with no braking on my part, and with my joystick pulled fully back (to keep its tail down). I do occasionally pull it off but the aircraft still tips forward and then tips back with a big thud !! I’m interested to know whether others find this (Instant Action) mission such a problem (for a pitch forward/prop strike) and if they don’t, is there a little trick that I’m missing? -
For quite some time now, it's been widely noted by the WWII community that aircraft when shot will sometimes duplicate an entire tail piece (sometimes multiple times but that's less frequently observed). It appears very possible that this is linked to DCS attempting to model the detachment of the entire rudder. For instance, with the 190A8: When the rudder is detached, it spawns the object "...oblomok_tail" This is that "...oblomok_tail" for the Anton: Same for the 109K4: Of note with this screenshot, the damage arguments do not match that of the actual 109 itself. This tail in this screenshot can be recreated with these arguments For a detached rudder, these are the arguments needed for a coherent rudder detachment animation This appearance of a regrowing tail has also been observed with the Spitfire, Dora, P-47, and I believe the P-51.
-
So if you can't really have: - Beauty without the Beast - Laurel Without Hardy - Angels without wings - Cinema without popcorn - Love without kisses .....how can we really have The Spit without the Hurricane.....? Anyone support this? C'mon folks, back me up here. Please ED - I REALLY want the Hurricane - to go with my Spit.
-
Never seen that before. Maybe it's old. Used to be, fly through power lines, nothing happens (power line tower strike has always been a thing). What's new? Visible flash on power line strike (nice touch), propeller vibrates whole plane (only apparent at low speed) but engine doesn't stop. Big chunks of three blades gone. New damage graphic(?), all four blades damaged on ground strike(at least in old 2.5.6). Someone (me?) will use the track, take control and see if and how much top speed is reduced and whine if it isn't. spitpowerlines.trk
-
I've always wanted to fly one of these beasts in a proper sim. I'm not big on IL-2 so I won't be purchasing Bodenplatte. Any chance we could get a Spitfire that rivals the Bf-109K we have in-game?
-
At 9:57 the pneumatic hiss is very audible in this real Mk9.
-
No comment.
-
The Artificial Horizon is very often badly out of whack (henceforth "wrong"), as many have noted. A little surprised that despite really trying (loop, roll ...) I have yet to find a quick way to get it "wrong". I'd love to make a short track but I couldn't. Interestingly, one real Mk IX (see film), messes up it's horizon anytime it rolls and then takes 9 minutes to self correct. Two things. DCS Spitfire horizon does not get "wrong" on rolling and it never self corrects (at least not in 80 minutes). Anyway, after 50 minutes, I manage to make it wrong by doing "donuts" and then finally I could do the test I set out to do: 1) Parked on runway, RPM 2200 (to provide suction) for 40 minutes+, horizon does not not self correct. 2) Fly plain and level for 40 minutes+, horizon is not self correcting. Note1, the 50 minutes Batumi - Soochi were flown straight and level to see if it would get wrong spontaneously. It didn't) Note2, I found the behavior after it's "wrong" weird. If I turn, in the air or on the rwy, I can get the horizon "right" again) Real life video references. 1) Hadley, Spitfire MK IX. https://youtu.be/Njjl_smtMoQ Within the first 40 sec, one can visually see the horizon creep in self correcting while on the ground. 2) Spitfire Mk IX crossing the channel. https://youtu.be/O-_AwgYxUW0 At 17:01 it rolls. Horizon gets instantly wrong. Watching from 18:06 (film cut) horizon is 90 degrees wrong. After 7 min (25:00) it's corrected itself in roll axis and after 2 more minutes it corrected itself in pitch axis too (total 9 min to completely self correct). The real Mk IX, in the film, rolls twice (at least), at 17:01 and at 27:15 (31:40, 32:40, 37:50, 38:47, 39:08, 39:40). Both (all) times the horizon gets instantly screwed up. Seems any roll always messes up the horizon in the real thing. In DCS it does not. Anyone so inclined can fast forward my track to the end (~10:24 [F2] time) to quickly verify non straight horizon is not just me.By [F2] time, I mean the lower right corner clock. ~ Track timestamps ([F2] view) to fast forward to: 8:00:00 Takeoff Batumi. 8:49:30 Full stop Soochi, horizon still good. Repair (nothing) Refuel. 8:52:00 Start donuts. Horizon gets "wrong". 8:59:15 - 9:42:15 Parked runway, horizon "wrong", RPM 2200 for 40+ min. Observe horizon not correcting. 9:43:40 - 10:25:12 Takeoff, course 270 (gyro) fly plain & level 40+ min. Horizon not correcting. Installation completely kosher, no mods no nothing. DCS 2.7.6.12852 Open Beta (recorded track) DCS 2.7.6.13133 Open Beta (replay) Intel Core i7 3630QM @ 2.40GHz (Max Turbo 3.40 GHz) 16.0GB Dual-Channel DDR3 @ 798MHz 2047MB NVIDIA GeForce GT 635M 447GB KINGSTON SA400S37480G (SATA-2 (SSD)) (~ 9:43:40) Soochi takeoff. Horizon "wrong" (10:23:40) After 40 min+ flight plain and level . Horizon still "wrong". spitfire_horizon_v2.trk
-
As in the title. Players might as well never close the canopy if it costs no speed to them, and only gives more visibility. Same with the P-51. P-47 and Spitfire do have some additional drag, but it's extremely little, only costing a handful of knots of top speed at SL. The drag from an open canopy should probably be a lot higher for those. canopy drag test.trk
-
When opening the canopy, it has little or perhaps no additional drag. So players might as well fly around with their canopy always open if it never slows them down. Test is performed by flying at mil power at SL with canopy closed for a couple minutes. Then pull a loop, open the canopy, and continue flying at power at SL. Test also contains the Spitfire, FW190A, and P-47. canopy drag test.trk
-
AUTO is forward, not rearward. All three switches are marked ON (rearwards) / OFF (forwards). The fuel pump and the pitot are ON rearward so I assumed for the radiator ON (rearward) = AUTO as well. There would be an "in flight" symmetry to that. All switches rearward = fuel pump on, pitot on and radiator AUTO. But no. ON for radiator switch apparently means flap fully open, auto off. Indeed key command [LCtrl A] AUTO does put switch forward (marked OFF) while [LShift A] OPEN does put the switch rearwards (marked ON). I tagged to this today when flap started to open in ON position with temps way below the 115°C overheat limit. I'm just asking for confirmation. This is how it works?
-
So I noticed multiple times when spawning P-51 start on runway engine spins up. When I touch the HOTAS throttle lever (Warthog) it goes to idle. Same thing Spitfire. HOTAS throttle idle but engine roars away until lever touched on mission start. Began with first 2.7 release I think. Yes, I checked the checkmark, I've relied on it for years.
-
Not bug report. Maybe this is how it should work. Flew distance (time-accelerate) Batumi - Sochi Adler, 2850 rpm, 7 boost, speed ~280mph (~230 knots). Temp set -12'C (as cold as settable). Pitot heat on. Below 5000 feet. Same trip, -3'C, IAS works all the way. But at -12'C it malfunctions at Sochi arrival. But (as headline says), fly slow ~100 knots (80-100 mph) for 1-2 minutes and IAS works again. So interpretation could be: pitot heating too weak at -12'C, 280 mph but slowing down reduces wind factor and pitot tube ice melts. One can see how needle drops while flying slow. To eliminate time-accelerate weirdness, I kept speed up (~280mph) circling the field for 5 minutes in real time and noted IAS did not fix itself until I slowed down. ~ Attached a track. 99.5% sure install is 'kosher'. No mods, only thing is MB-339A & A-4E installed "SAVED GAMES" folder but they're not activated here. spit_cold_pitot.trk
-
Multiplayer, so no meaningful track. Don't know how to recreate so therefore not a bug report. 1) Oil pressure Generally oil pressure is at 120 psi or over unless boost & rpm set low. Recommended is 60-120. I find it a bit off that oil press is almost always at 120 or more. Specific case now. Flew 100 nm abouts. Boost 7, rpm 2850. I noted how the oil pressure was stuck at upper range (150). Why? Wasn't stressing engine at all. -3'C degree Aerobatics Online Server. Landed, engine quit. Figure it was the high oil press was the cause. I've noted typically oil pressure drops with radiator closed (switch forward off). Flipping switch rearwards (radiator auto, opening), oil pressure always goes up even more. 2) I long noted occasional weirdness with the starter. Specifically sometimes it refuses to turn over after repair and adding ground power does nothing. Brand new weirdness (same flight as above). Attempting to start after engine quit, it didn't, as expected, assuming engine seized. But, further, volt meter dropped and stayed dropped after releasing starter button. Then I could watch the voltage dropping as if something (starter engine?) just drew tons of current. Immediately after repair finished, prop turned over as if starter engine was still stuck. Watching the voltmeter I clicked the starter button and prop stopped turning and voltage shot up a bit again (as if "unsticking" the starter button). Attempting to start to start after repair. Voltmeter at 10V (which I remember is to low, needs 13-15V). Prop turns over slowly. Add ground power and once again confirm ground power does not work. With ground power, obviously prop should spin over fast enough to start. I even believe starting by battery was the exception in real life. Add a link to my old thread when I find it. One thread (commented but not started by me) on no working ground power. I observed some weird volt flickering, which i note is commented on in linked thread also.
-
jesusspit.trk
-
Used to think 1600 was an extremely low. No, it was a used setting. DCS manual states: and also from a book, a homecoming panicky Spitfire over London "I got 7 gallon!". Flight leader: "You can break formation, set 1700 rpm Boost 4 and go home". Also discussed, 1 lb 2650 rpm gives the same speed as 4 lb and 1700 rpm (but the latter will save 7 gallons an hour *1). ~ I find I can set 1800 rpm and I can set 1200 rpm but nothing in between. Thought at first RPM-lever problem but running Thrustmaster "Target Script Editor" -> "Device Analyzer" (scale of 0-I6384) I can see that RPM-lever setting: 15974 -> 1200 rpm and 15972 -> 1800 rpm at both 0 boost or 4+ boost. Made a chart. RPM-lever is readout Thrustmaster "Target Script Editor" -> "Device Analyzer". Never mind the dropping line, the interesting part is the linearity (lack thereof after ~15970). By "throttle" I actually mean RPM lever (chart below). Anyone run Release version? A simple test might be interesting. Can 1600 be set with pre 2.7 version? ~ *1) Not a typo, flying slow as you can is NOT the most fuel or range efficient, this war time memo emphasizes, because of dynamics of slow speed drag.
-
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
-
All, Looking to join a relaxed squadron to join to fly during the week or weekends. I am on EST I have a Discord Server. Name PKP_Coole#3299. Thanks, look forward to flying! -
Happened twice now, first in Aerobatics server (see link below) and now in Hoggit server. I decided it's not a fluke, it's a bug. 1) It repairs visually but damage remains 2) Repair cycle can be repeated in perpetuity. Can do F8-->F3 "repair" any number of times and get a new 170 sec cycle. First time tail wheel didn't repair. Link to old "is this a bug?" post. This time, again repair visually but main gears refused to retract no matter how many times I repaired. Track file is multiple flights, hour long and larger than 5 MB, so skipping. Taking a guess, it's something to do with new damage model. It's probably not gear related (because two different gear problems) or even Spitfire specific. Someone else must have seen this?
-
Something i have noticed based on reading the aircrafts manuals and seeing real life videos on the spitfire, the issue regards the mixture controll lever as it is currently it is inccorect, currently to start the engine you must, set the fuel cock, build fuel pressure using either method, prime the engine, open the covers press both at the same time and once the engine begins to splutter or "catch" move the mixture into the "RUN" position from "IDLE CUT-OFF" referencing "Air Ministy Air Publication 1565J, p&l-P.N. September 1946 Pilots notes" (this covers the merlin 61,63,66,70 and 266) it should be done as follows, (PRE-START) set fuel cock ON Ignition (magnitos) switches OFF Throttle 1/2 in.-1in. open RPM lever fully forward Mixture lever (Marked correctly as Idle cut-off lever) Fully Aft Supercharger Auto Carburettor air intake filter control Filter in operation (START) Switch ON the main tanks booster pump for 30 secconds (this is done as both the wobbly fuel pump and booster are mutually exclusive and it is used instead of the wobbly hand pump) Then switch it off (at this point the low fuel pressure light should extinguish) and set the mixture (idle cut-off lever) to the forward RUN position Prime the engine as required based on the outside temps switch on the ignition (magnitos) and press the starter and booster coil pushbuttons when the engine fires release the starter button; keep the booster could button depressed until the engine is running smoothly the issue is, that this is not possible in DCS you can only start the engine with the mixture aft then wait untill the engine "catches" and move the mixture to run, as you can see in the manual this is inccorect you can also find videos for the real thing starting up in the manner described in the manual and not how it works in DCS, this is something that has bugged me for a long time, and i could not find a report on it so i thought id make one. I own a phisical copy of this manual can have a digital vertion i can send if you need it both are identical i can also provide a video if you wish regards minty
-
Is it just me seeing this? ~~~ Turned yellow after the October 19 Beta update "DCS 2.9.0.46801 Open Beta" "Updated cockpit textures" I believe. Recycling old screenshot from November. Latest version "DCS Open Beta 2.9.1.48335" still yellow.
