Just for my curiosity, is there a reason you prefer the flightdeck to look 'pristine'?
It's a (small) place where two work for hours on end. We asked our befriended pilots to make some photos of the flight deck as they use it. These show often a huge mess, from Mac Donald wrappers via magazines to laptops, cameras etc etc. We have a large collection of flight decks that are almost comically full of 'stuff'. As this is how a flight deck looks in reality we feel it should be part of the simulation. As I said if you prefer a simulation product that focuses only on systems this is not for you, if you want to experience flying an airline, this will work.
It's not on the 'Leaving the cockpit' checklist but there should be something there that makes sure pilots clean up after themselves!
Well, modelling coffee cups is the 3D department while the cold&dark state is the guy who programs the systems. It's a bit like comparing apples to oranges. The modeller had enough time to include the coffee. However, the systems programmer is the one with the longest bug list (that's not because of him - it's the case in every aircraft project), and that's what he focusses on.
One point is right about the coffee though. Only feeble pilots drink coffee. Real pilots breakfast with Jägermeister. Coffee had to be modelled because of the minor age customers (Jon from spanish support just said that on Skype)
What airline are the pilots from that have to start from Cold and Dark? The advisory pilots we use in this project (all flying for the major airlines) are not used to that.
Beside, do note that it still work, you can still start from Cold and Dark, there are just a few tweaks we might do that we are not focussing on now. And indeed many (if not all) systems are done with far more detail, but that is completely in line with what we intend to do. Making the systems better means the crew tasks can be done more realistic.
Unfortunately PSX Navdata is only updated once a year so the SIDs & STAR data is often obsolete before it is even purchased so it is often useless.
If the route data contained the SIDs & STARs then they would be inserted into the FMC without being dependent on the obsolete internal Navdata.
As it is at the moment the only way to enter the new data is by hand. :-(
I don’t really want to criticize your project because I think you’re doing a great job. But I also don’t know where this thing is going... you said that this Airbus will be more focused on systems and their functions, and then you say that you’ll not work on the “cold and dark” state just because a pilot never finds an airplane in that state (and I don’t think so... I know a lot of pilots and most of them starts with the aircraft completely turned off) but you’ll concentrate on modelling more coffee cups in the morning because pilots usually drink it?...
I thought program analysis tools detect such stupid mistakes. I tried clang-tidy, but it did not detect this. However, plain clang (the compiler) issues a warning for these lines, but gcc not. I assume that FS addons are compiled by Micorsoft's compiler, I did not try it yet. I think many of these bugs should be detected before testing using program analysis tools, and some of them are completely free.