Ken S,
I think this is a direction to try.
1. First thing is cut/paste the console log from starting up with your
working 4.12 system. This gives us a baseline of your setup.
2. Make sure you open/save any panel files you are using.
3. Make a minor change in the preferences, something you can change back,
like add a startup action.
4. Those steps make sure the files are written at the 4.12 version level.
5. Update to 4.16.
6. Startup with 4.16 and cut/paste the console log. This will show what is
or isn't not happening.
Make no other changes. From this we can see the where you start and finish.
Then we can give meaningful comments.
Sometimes there are changes that make updates along the way. If someone is
jumping too many versions, the old version might not be able to be correctly
read by the new version. Making regular updates, the issue doesn't come up.
For a while a new version will still read the old version files, but it is
using old code we have replaced with new methods. Eventually we clean up
things and remove that old code. That is when somebody who didn't do
updates, and then did a load/save to save all new way entries will have an
issue. It happens very seldom, but making a few more steps here should
figure out if this is a part of your problem or if something else is
happening.
You might also use the Help->Upload Debug Info, it will send a package or
details like your profile and log files, with some system details too. That
may also give us more clues when it isn't working.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
Ken Cameron