nomdeplume Posted August 18, 2011 Posted August 18, 2011 how is this related to the option 'Random system failures' which CAN be turned off. With it turned off I have never ever had any failures other than induced by gunshots or MY flying ;) The post you're quoting pre-dates the introduction of the option to disable random failures.
Stingray66 Posted August 18, 2011 Posted August 18, 2011 The post you're quoting pre-dates the introduction of the option to disable random failures. :music_whistling: Stingray ASUS P8Z68-V Pro - Intel 2500K @ 4,2GHz - Antec H2O 920 - 8GB Kingston XMP 1600 MHz - GeForce GTX 560 Ti 2GB - WD 1TB Caviar Black SSD Intel 311 20GB (cache) Textures: High | Scenes: High |Water: High| Visibility: High| Heat Blur: On | Shadows: High | Res: 1920x1080 | MSAA: x8 | Vsync: On | HDR: Normal| TSAA: On| Mirrors: Off | Civ Traffic: Medium| Res Of Cockpit Disp: 512 | Trees: 12000m | Clutter: 500m
Evil.Bonsai Posted August 20, 2011 Posted August 20, 2011 Rainmaker's post are Hilarious! Why? 'Cause I work in an industry that uses VERY expensive equipment (semiconductor manufacturing.) And pretty much w/o fail (see what I did there?), the more expensive that machine is, the more likely it is to fail. I work with millions of dollars' worth of equipment daily, most of them are crap. Not all, but most. They ALL have something wrong with them, but unless it's a) critical to the outcome of what's going in or b) I'm just seriously annoyed with clearing ANOTHER damn alarm, we just deal with it. Doesn't sound to much different than what Rainmaker describes. :)
711Hancer Posted August 21, 2011 Posted August 21, 2011 (edited) Just to give a quick note for CADC errors for the ones who don't know: It generally happens when you forget to enable pitot heating which is sometimes missed during pre-takeoff checklist. Also via CDU System/Reset Sub Page, you can check the status of CADC and various systems (V = Valid, F= Failed) and try to reset and re-initialise CADC system during flight which may work. Edited August 21, 2011 by 711Hancer
Frostiken Posted August 21, 2011 Posted August 21, 2011 (edited) While the content of this thread is old, I for one would like to see this, or at least future DCS modules expand the failures Rainmaker described. We both do the exact same job - he's 100% correct. For those reading the thread, one thing that wasn't brought up by him was that Speed kept throwing around this "200 hours" number - 200 hours is a very, very long time in ANY aircraft, especially a military aircraft. While the CADC failure rate was excessive and has been fixed, I can safely say that yes - all displays - to include the HUD and MFCDs, are almost guaranteed to break by then. When you suffer display failures you can have bad color channels (annoyance), it could be slightly crunched (annoyance), it could randomly blink off and on (annoyance)... these are all failures, but would be reported as Code 2 more often than not. Unfortunately due to time and budget constraints we couldn't get all these kinds of failures modeled. BTW: There's talk in here about 'preventive maintenance' - sorry folks but as far as avionics goes there's pretty much zero preventive maintenance. We only really have two kinds of fails - internal or external to parts, and if it's external that means wiring, and that means it's going to take a while. What little there is we can do (RFTLTS cables) we probably don't even have time for because there's 4-page recaps coming out of debrief of pilots who set up their IFF wrong and wrote up 5 Code 3s for 'No reply on Mode C'. **** YOU IT WORKS FINE, LERN 2 FLY. Edited August 21, 2011 by Frostiken [sIGPIC][/sIGPIC]
Recommended Posts