Jump to content

Recommended Posts

Posted

I was on the second leg of what ended up being a 1.9 hour sortie (on one tank, no externals no less!) and pulled a modest amount of Gs... when my CDU blanked off, cautions flashed on the screen, and just as quick as it came up, it went away and the CDU reset itself, booting to a 'warm start' screen. Needless to say it seriously messed with a few of the things I was doing, but I thought it was a great touch, a nice change from the old 'works fine or never works at all' problems. As an avionics guy this is exactly the kind of problems that pilots see in-flight.

 

Now we just need component sub-failures :)

 

I really just wish failures were documented in the pilot log at the end.

 

Honestly for the next DCS I hope they focus even more on the random failures aspect, with a boatload of component subfailures and other problems. Actually what would be really neat would be a dynamic campaign with a maintenance aspect, where jets accumulate Code 2 and Code 3 writeups and have to undergo repairs, so if you treat your planes like crap you may eventually run out of planes to fly, or end up taking one with a handful of Code 2s like 'radio induces lots of noise when keying', 'HUD video is crunched too small', 'RWR random tones and spikes with no correlation'...

 

Anyway, horray for simulating what real military aircraft are like :)

[sIGPIC][/sIGPIC]

Posted
I was on the second leg of what ended up being a 1.9 hour sortie (on one tank, no externals no less!) and pulled a modest amount of Gs... when my CDU blanked off, cautions flashed on the screen, and just as quick as it came up, it went away and the CDU reset itself, booting to a 'warm start' screen. Needless to say it seriously messed with a few of the things I was doing, but I thought it was a great touch, a nice change from the old 'works fine or never works at all' problems. As an avionics guy this is exactly the kind of problems that pilots see in-flight.

 

Now we just need component sub-failures :)

 

I really just wish failures were documented in the pilot log at the end.

 

Honestly for the next DCS I hope they focus even more on the random failures aspect, with a boatload of component subfailures and other problems. Actually what would be really neat would be a dynamic campaign with a maintenance aspect, where jets accumulate Code 2 and Code 3 writeups and have to undergo repairs, so if you treat your planes like crap you may eventually run out of planes to fly, or end up taking one with a handful of Code 2s like 'radio induces lots of noise when keying', 'HUD video is crunched too small', 'RWR random tones and spikes with no correlation'...

 

Anyway, horray for simulating what real military aircraft are like :)

 

 

+1 :thumbup:

Oculus CV1, Odyssey, Pimax 5k+ (i5 8400, 24gb ddr4 3000mhz, 1080Ti OC )

 

 

[sIGPIC][/sIGPIC]

Posted

It would be really nice to have a failure log in the debriefing so you exactly know what went wrong and if something went wrong.

Intel Core i5 750 @ 4 GHz, 8GB Ram, ATI Radeon 5800, Saitek X52 HOTAS & Pedals, TIR 5, Wondows 7 64bit

Posted
The next step will. E to have a virtual maintenance department to A-799 your gripes.

 

 

A-799 is the Navy/Marine Corps VIDS/MAF code for "Cannot Duplicate".

 

LOL ......11-1-A-799 to add a bit more from my memory.....only thing I remember from the navy after being out for 22 years.

Airdog

| Asus ROG Strix Z370-E Mobo | i7 8700K @ 4.7 | 32 GB DDR4@3200mhz | Gigabyte 2080Ti OC 11GB| Samsung M.2 960 Evo 250Gb and 500Gb | Win10 Pro | Hotas Warthog #02743 | Track IR 5 | Toshiba 47" 120hz LED | Acer 23" Touchscreen | HELIOS |Oculus Rift-S|

 

http://www.blackknightssquadron.com/

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...