One place to access all the documentation

I've just noticed the standard Start Menu entries point to only module-specific and DCS World manuals while the Doc folder contains much more (controls configuration, charts...).

Proposed solution:

Shortcut to the Doc directory.

EDIT:

Seems not enough, as Flight Manuals are scatered across the Mod folders

http://forums.eagle.ru/showthread.php?t=91552&highlight=Su-25T+manual

http://forums.eagle.ru/showthread.php?t=91151&highlight=Su-25T+manual

Next step:

A wiki with a library with documents useful for specific DCS modules. Document not free to redistribute => include a detailed reference.

Related

http://forums.eagle.ru/showthread.php?t=106481

Title says it all.

 

Improvements, like the Module Manager, are so much more useful when the documentation contains instructions for their use.

 

How many threads currently exist where people cannot install a module because it is older than their up-to-date World install?

 

EDIT: Note, the DCS World User Manual was last updated prior to 1.2.3

An excellent idea! And how about aerospace industry standards for the flight manuals with emphasis on change management tracking and version control?

Woah, buddy, you've got carried away a little bit :) The current manuals don't even include mandatory performance data.

Not really and I'm not asking for exact tech data realism. But if developers are going to put out 500+ page documentation or any page count for that matter; some version control processes are absolutely essential if new features get added to existing products. All of the DCS modules need a version number AND date on the lower right front cover of the pdf document. Inside the document, a thin vertical black line on the left side of the page should denote changed or edited material. These two items are easy to implement and would keep the tech writer organized and help out the user community.

Woah, buddy, you've got carried away a little bit :) The current manuals don't even include mandatory performance data.

Not really and I'm not asking for exact tech data realism. But if developers are going to put out 500+ page documentation or any page count for that matter; some version control processes are absolutely essential if new features get added to existing products. All of the DCS modules need a version number AND date on the lower right front cover of the pdf document. Inside the document, a thin vertical black line on the left side of the page should denote changed or edited material. These two items are easy to implement and would keep the tech writer organized and help out the user community.

Oh, so this is what you meant. +1 then!

I thought you meant a complete version control and distribution system per real avia standards.