Help for the Help Wiki

[Westernmost]

I'm sure this has been kicked around a lot already, but my newest attempt at this begs the question again.

Is there any plan to better organize the Help Wiki for rookies so that it presents a logical journey through the system instead of leaving it to the user to hunt for needed information that may or may not be accessible if he doesn't know what to search for?

There is a nice page on downloading and "getting started." And then it leaves you sitting there, with no indication of where to go next for meaningful orientation into this amazing world you just entered. Without an opening orientation, nimrods like me get stuck and frustrated. For example, I wanted to find info on the concept of "baseboards." But without knowing it was called a "baseboard," it took me several searches to finally find the page that provided a good explanation of them. Ditto a nice, clean flowchart of the process. If you don't know what to ask for, the answers can be very hard to find.

This is in no way to knock all the work that's gone into writing the thing. I'm just saying that all this knowledge needs to be laid out in a logical order, specific to each version. That "getting started" page, for instance, does have a directory of next steps - for the 2012 version, and doesn't say so until you're there. (The fact that it reminds you that 212 had a manual didn't help the situation!)

I also gladly acknowledge the tutorials and YouTube videos that are intended to help with this. But videos have a drawback in that documentation doesn't - I can print out documentation and flip back and forth through it if I need to. Plus, if the game is already aggravating me, I really don't want to compound the stress by fighting with a video.

For sake of context, I came into this from Train Player. TP may have chintzy layout graphics and 2D only, but it has a superbly organized help section. Plus the downloads are almost instantaneous instead of dying after hours of the Download Store's blazing 4K per second rate.

I dig that even one version of Trainz would need a library of manuals to cover everything. But at least something in concise, logical, printable form would be very helpful.

 

[pware]

I agree, especially with your point "If you don't know what to ask for, the answers can be very hard to find."

From professional experience writing user documentation is a slow and difficult task. A task that is made even harder when the subject being described is current technology. Unlike history where the "facts" (names, dates, places, etc) are "fixed" and well known, the "facts" in technology can change overnight.

Each time a new version of Trainz is released (approximately every 2-3 years) much of the documentation has to be rewritten. Service Packs and Hot Fixes, which appear more frequently, often require some rewriting, but this can still be time consuming. With Trainz Plus significant new features appear approximately every quarter.

For the reasons above (plus the shear costs involved) the days of a complete printed manual with every software product are long gone.

This is where the Trainz Community has stepped in with the Trainz Wiki. In many ways community involvement is a good thing but it does leave gaps.

 

[pcas1986]

TANE was the last version of Trainz that included a manual (pdf) and even that was out of date when TANE was finally released. I remember it well since as a beta tester I read the manual from cover to cover. The last few chapters probably didn't get the attention they deserved.

There is a user guide for TS22 which is outside the Trainz WiKi that might help. See https://docs.trainzsimulator.com/docs/trs22-user-guide It's not TS19 but there would be a lot in common.

 

[pware]

Yes, even PDF based documentation is going the way of the dinosaur. While it has some obvious advantages over paper based documentation (now extinct) it still suffers from having to be redistributed after every update, which means all the users have to download the new copy into their PDF readers. And updating PDF is still not an easy task.

Web based documentation, usually HTML or Wiki (or both in the same document), is now the current "standard". It is generally easier and usually quicker to update and distribute than PDF and does not require the users to manually download the documents. My last contract (i.e. paid) documentation writing project was entirely web based.

 

[pcas1986]

...
Web based documentation, usually HTML or Wiki (or both in the same document), is now the current "standard". It is generally easier and usually quicker to update and distribute than PDF and does not require the users to manually download the documents. My last contract (i.e. paid) documentation writing project was entirely web based.

I like the context style of documentation where you can, say, right click on some menu item and be taken to an explanation of the item in question. I did some of that for Andi and PEV's AssetX before it became unsupported. Trainz does have some in the error messages on asset committal but they are not obvious.