steamer_ctn, on 15 July 2021 - 01:36 AM, said:
Sadly we seem to always end up at the same point, ie somebody likes each one of the options, and therefore they say that they shouldn't be removed.
IMO this problem can be solved rather easily as follows:
Global Level -- Required.
Content folder (e.g., where /Routes is found) -- Optional
Route folder (e.g., where *.trk is found) -- Optional, file is named for the route
\Activity folder (e.g., where *.ACT is found) -- Optional, file is named for the Activity
The game software starts looking at the bottom of that hierarchy. If the options file is found, use it. If not, go up one level and repeat. If no options files are found, use the global settings. None of the extant options do not need to be depreciated in this approach and I think Chris' ideas about doing a better job explaining what there are -- in the GUI -- is a good idea.
In this way the global settings are the default and as such would be used in most cases. Having the other locations available allows for as-needed customization. It might turn out that only a few routes get options files, and a handful of activities. But right now each of those requires fiddling at the global level and remembering to reset them that to previous values when done. That;s a PITA.
My comment earlier about a GUI is not one I particularly favor but it would provide a firewall against typos, crazy values, and outright stupidity.
postscript added later: FWIW I recommend the same approach to whatever camfig solution is implemented, On one route I work on there are activities that almost require the monitor be in portrait mode. Sine that is not always possible the range of camera movements would need adjustment to being not very far from teh train but having a large range of vertical movement, a need that is rather unlikely in most routes.