Search the Community
Showing results for tags 'trk file'.
-
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
- 13 replies
-
- log file
- artificial horizon
-
(and 4 more)
Tagged with:
-
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
-
- video
- propeller strike
-
(and 4 more)
Tagged with:
-
Simplest possible mission (~1 second length). Single P-51 start-from-runway ("client") on Cacausus map. All mission defaults taken. Clean 2.7 install. -Start mission (directly or via Mission Editor, same result) -Spawn -ESC -> Quit -Fly again -> CTD crash to desktop Very repeatable, happened ~10 times, never not happened. Replacing P-51 with Spitfire or Bf 109, no CTD. Include mission file and crash log generated by DCS. Open Beta "2.7.0.5118". PC spec, see signature (Commodore 64) dcs.log-20210505-082129.zip P-51 CTD crash.miz
-
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
- 1 reply
-
- spitfire lf mk. ix cw
- spitfire
- (and 5 more)
-
jesusspit.trk
-
Look at "Turn Indicator". "Weirdness" 18 sec into video. Auto shutdown, acts the same if just killing the magnets. Installation as clean as it can be (pristine, no mods no nothing), track as short as it can be. Logs.zip p47turnindicator.trk
-
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
- 13 replies
-
Quoting old thread: Ground Power is for starter, what I always assumed, makes perfect sense. But ... I've noticed many times, engine refuse to turn over, battery seems low, after repairs. Connecting Ground Power doesn't help. So I did a simple experiment with P-51 and with Spitfire (Summer +20'C). 1) Spawn "Takeoff from runway" (This assured engine temp/oil pressure was up, no damaging engine by turning over cold) 2) Shut off magnetos (engine stops) 3) Spun the starter until battery drained (prop stopped moving) 4) Attached Ground Power and attempted to start. P-51 started (as it should). Spitfire prop didn't turn over at all (voltmeter showed 5V (down from initial 14/15V), whatever that means *1) If Ground Power is for starting, which again makes perfect sense, then this is a simple well defined bug. Ground Power should power the starter in an undamaged aeroplane. *1) Would ground power really bypass the voltmeter? If it does, be that as it may, the important point here is that ground power doesn't power the starter.
- 53 replies
-
- volt meter
- battery
- (and 10 more)
-
In video below especially compare IAS red/yellow needle and G-meter red/yellow strip. The latter does not wash out nearly as much. How gauge colors should look? Daylight colors for comparison with night. 1920x1080 (min settings). Attached MP4 video because YouTube quality just too bad. Video: 1:00 AM night, spool engine up max Cycle "Instrument Panel Primary Light Rheostat" min - max twice Crappy YouTube, see attached Video.Zip instead. Deliberately left out Diag.txt in attached files. I'm paranoid, don't want to give out every computer detail on an open forum. logs.zip F-86 panel gauges lights.trk Video.zip