Tucano_uy Posted February 12, 2015 Posted February 12, 2015 Well, there I was, getting ready for a quick flight around the field, starting up my Mustang when.... that happened. :noexpression: The track is only 28 seconds. I was the only unit placed in the mission editor. Anybody has an idea of what could have happened? I replayed the same mission and everything was normal.Strange.trk
ricktoberfest Posted February 12, 2015 Posted February 12, 2015 Not gonna explain what happened for those of us not on our home computers?
outlawal2 Posted February 12, 2015 Posted February 12, 2015 Not gonna explain what happened for those of us not on our home computers? +1 :thumbup: "Pride is a poor substitute for intelligence." RAMBO
Art-J Posted February 12, 2015 Posted February 12, 2015 Spoiler alert! . . . . . . . His plane decided to blow up to pieces when he tried to switch magnetos or booster pumps on. It was a short, yet a pretty good thriller, I didn't know what to expect and it made me jump in front of my computer :D. Only the built-in DCS random damage algorythm knows what's that all about. Sometimes weird stuff happens, although usually not in such an explosive way ;). In Mustang, I had my engine quit on me once, during take-off, with all parameters "in green". Just like that, for no apparent reason. Well, you just live with it. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
msalama Posted February 12, 2015 Posted February 12, 2015 Sabotage. An act of terror. Those pesky insurgents are at it again! The DCS Mi-8MTV2. The best aviational BBW experience you could ever dream of.
BitMaster Posted February 12, 2015 Posted February 12, 2015 Sabotage. An act of terror. Those pesky insurgents are at it again! Man the Choppers !!! BTW, this happened to me a few times in the P-51, never knew why and I thought it's random error that comes and goes with patches as I have random failure disabled. Maybe some scripts overwrite this and it kicks in, who knows, that's a Pilot's life :pilotfly: Bit Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X
NakedSquirrel Posted February 13, 2015 Posted February 13, 2015 Had the same thing happen to me several times in the Bf109K4, plane randomly exploding on startup Modules: A10C, AV8, M2000C, AJS-37, MiG-21, MiG-19, MiG-15, F86F, F5E, F14A/B, F16C, F18C, P51, P47, Spitfire IX, Bf109K, Fw190-D, UH-1, Ka-50, SA342 Gazelle, Mi8, Christian Eagle II, CA, FC3
Tucano_uy Posted February 13, 2015 Author Posted February 13, 2015 Not gonna explain what happened for those of us not on our home computers? Hehehee. That would spoil it.
Rangi Posted February 13, 2015 Posted February 13, 2015 Maybe some scripts overwrite this and it kicks in, who knows, that's a Pilot's life :pilotfly: Bit That's a pilots death..... PC: 6600K @ 4.5 GHz, 12GB RAM, GTX 970, 32" 2K monitor.
Tucano_uy Posted February 14, 2015 Author Posted February 14, 2015 It seems to be rather common now. It happened twice again since my first post. Only difference to what I always did is that now I'm using dynamic weather.
Captain Orso Posted February 16, 2015 Posted February 16, 2015 8< made me jump in front of my computer :D. 8< Made me jump too, and I knew what was coming :megalol: The explosion was 1A though :thumbup: When you hit the wrong button on take-off System Specs. Spoiler System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27" CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
Echo38 Posted February 16, 2015 Posted February 16, 2015 Only difference to what I always did is that now I'm using dynamic weather. That's what causes it. It's a very old bug; a forum search should show up previous reports. The only workaround is to refrain from using dynamic weather. : /
Tucano_uy Posted February 16, 2015 Author Posted February 16, 2015 That's what causes it. It's a very old bug; a forum search should show up previous reports. The only workaround is to refrain from using dynamic weather. : / It's crazy what things that look completely unrelated can do. Bug squashing must be a tough task.
Captain Orso Posted February 16, 2015 Posted February 16, 2015 The most difficult think in debugging is finding the bug. Once you've found it, it shouldn't be that difficult to fix. So what, dynamic weather caused a lighting strike? :P When you hit the wrong button on take-off System Specs. Spoiler System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27" CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
Looney Posted February 16, 2015 Posted February 16, 2015 I tried using ground power to start the p51 the first time I've set foot in one. Didn't read any startup manual so was randomly pushing buttons when the kaboom happened. Managed to recreate it twice after that by using ground power, magnetos and fuel pump... [sIGPIC][/sIGPIC] Commodore 64 | MOS6510 | VIC-II | SID6581 | DD 1541 | KCS Power Cartridge | 64Kb | 32Kb external | Arcade Turbo
Recommended Posts