You are right Tom. Smart cockpit does have an answer. the link below takes one to the Flight management guidance system manual. A tidy little thousand page document.
Why not include it in your documentation or at least as a directed information source. One shouldn't have to go hunting for an outcome.
To be honest, and feel free to delete this, it sounds like DA really dropped the ball into Aerosoft's lap. In that case, it would be similar to the issue over at Orbx. There you have this prestigious "FTX Global" brand of products with tons of manpower and support behind them, then they partner with Pilot's who frankly won the lottery to get their product into the Global lineup. That's the problem when you rely on another group to do something, it may work, it may work once, or it may just be a hassle. So we get FTX Global Base and the beautiful OpenLC textures, hundreds of decent freeware airports, phenomenal payware airports (and not just Global branded), and then there's cousin Vector.
Sorry Tom, there is a big difference between the MCDU and an engine or hydraulic system. In both the latter instances, one starts it and monitors it. with the MCDU there is a massive amount of user interface and it hasn't been addressed in the documentation. There is nothing more frustrating that getting a 'bad entry' response from the MCDU. it could be bad format - but we don't know what the standard format is. It would take someone in Aerosoft a couple of days max to put together a basic operating format document for the MCDU. As one of the fundamental tools in driving the bus beast it should be explained. The step by step is great and I can fly from LOWI to LFMN with the best of them. But what is the format for inputting a location not in the nav data base. What about anything that is non standard... One needs to understand how to use a tool not just ape the processes someone does for a limited application of the tool.