Difference between revisions of "Upgrading to a newer version"
m (4 revisions) |
(Replace " with actual quotes) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Manual/Usage}} |
||
| − | |||
| − | '''''What you need to do if you're upgrading TTDPatch from an earlier version.''''' |
||
| − | |||
| − | =Upgrading to a newer version= |
||
| − | |||
What you need to do if you're upgrading TTDPatch from an earlier version. |
What you need to do if you're upgrading TTDPatch from an earlier version. |
||
If you had a copy of TTDPatch before, and are now upgrading to a newer one, there are a few things that you should pay attention to. |
If you had a copy of TTDPatch before, and are now upgrading to a newer one, there are a few things that you should pay attention to. |
||
| − | The first one is that TTDPatch may ask you to delete |
+ | The first one is that TTDPatch may ask you to delete <tt>ttdload.ovl</tt>, because it has become outdated. This file will then be generated again the next time you run TTDPatch. It is generally a good idea to delete this file anyway. |
| − | The second thing is that you probably want access to the new options, but they are not in your configuration file. |
+ | The second thing is that you probably want access to the new options, but they are not in your configuration file. To do this, start TTDPatch with the following command line:<pre>ttdpatch -W ttdpatch.cfg</pre> |
| − | Alternatively, put the line<pre> |
+ | Alternatively, put the line<pre>writecfg ttdpatch.cfg</pre>as the last line of <tt>ttdpatch.cfg</tt>. |
| − | The above start TTD too, if you prefer to only update the configuration but not start TTD yet, use this:<pre> |
+ | The above start TTD too, if you prefer to only update the configuration but not start TTD yet, use this:<pre>ttdpatch -!T- -W ttdpatch.cfg</pre>(the "-!T-" bit must be the first switch; it is technically a [[DebugSwitches|debug switch]], with the "T" standing for "terminate.) |
| − | All of these tell TTDPatch to read your current configuration from |
+ | All of these tell TTDPatch to read your current configuration from <tt>ttdpatch.cfg</tt>, and write this configuration back, along with the new options. Then you can edit the new file, and change the options as you like. |
| − | By default, the above lines add the new switches but leave them turned off. |
+ | By default, the above lines add the new switches but leave them turned off. If you like to turn on all new switches, use<pre>ttdpatch -a -C ttdpatch.cfg -W ttdpatch.cfg</pre> |
| − | This tells TTDPatch first to turn on all switches (-a), then read your current settings for the old switches (-C ttdpatch.cfg) and finally write the settings back into ttdpatch.cfg (-W ttdpatch.cfg). You can of course add the |
+ | This tells TTDPatch first to turn on all switches (-a), then read your current settings for the old switches (-C ttdpatch.cfg) and finally write the settings back into ttdpatch.cfg (-W ttdpatch.cfg). You can of course add the "-!T-" at the beginning to make it not start TTD as well. |
| − | Finally, and especially when upgrading from 2.0r1 to 2.5 or from 2.5 to 2.6, you may need to update your copy of ttdpbase |
+ | Finally, and especially when upgrading from 2.0r1 to 2.5 or from 2.5 to 2.6, you may need to update your copy of ttdpbase[w].grf. TTDPatch will complain if your copy is too old. The most up-to-date version is usually [http://www.tt-forums.net/viewtopic.php?t=31471&start;=0&st;=0&sk;=t&sd;=d in this thread]. Note that link sorts the posts newest-first, instead of the standard oldest-first. |
Latest revision as of 13:51, 31 July 2011
Introduction
Usage
Patches
Additional Reading
Additional Reading
What you need to do if you're upgrading TTDPatch from an earlier version.
If you had a copy of TTDPatch before, and are now upgrading to a newer one, there are a few things that you should pay attention to.
The first one is that TTDPatch may ask you to delete ttdload.ovl, because it has become outdated. This file will then be generated again the next time you run TTDPatch. It is generally a good idea to delete this file anyway.
The second thing is that you probably want access to the new options, but they are not in your configuration file. To do this, start TTDPatch with the following command line:
ttdpatch -W ttdpatch.cfg
Alternatively, put the line
writecfg ttdpatch.cfg
as the last line of ttdpatch.cfg. The above start TTD too, if you prefer to only update the configuration but not start TTD yet, use this:
ttdpatch -!T- -W ttdpatch.cfg
(the "-!T-" bit must be the first switch; it is technically a debug switch, with the "T" standing for "terminate.)
All of these tell TTDPatch to read your current configuration from ttdpatch.cfg, and write this configuration back, along with the new options. Then you can edit the new file, and change the options as you like.
By default, the above lines add the new switches but leave them turned off. If you like to turn on all new switches, use
ttdpatch -a -C ttdpatch.cfg -W ttdpatch.cfg
This tells TTDPatch first to turn on all switches (-a), then read your current settings for the old switches (-C ttdpatch.cfg) and finally write the settings back into ttdpatch.cfg (-W ttdpatch.cfg). You can of course add the "-!T-" at the beginning to make it not start TTD as well.
Finally, and especially when upgrading from 2.0r1 to 2.5 or from 2.5 to 2.6, you may need to update your copy of ttdpbase[w].grf. TTDPatch will complain if your copy is too old. The most up-to-date version is usually in this thread. Note that link sorts the posts newest-first, instead of the standard oldest-first.
