Keeping Customisations-What's lost on installs/un-installs?
Posted: 31.12.2005, 14:21
I recently installed 1.4.0 and shortly afterwards had some problems with frame-rates to the point that it became unusable. The day-night shadow had a jagged edge and FPS was about 0.6. (I'd also installed a few alternative textures for earth etc...)
I wasn't sure if the problem was due to 1.4.0 install, or changes I'd made in solarsys.ssc and nearstars.ssc (defined new barycenters), so I decided to re-install 1.3.2.
Can someone give me the definitive answer on what is wiped/retained on installs/uninstalls. Obviously solarsys.ssc is replaced, which makes me wonder what else could I have wiped out?
I seem to have solved the problem I was having and would like to re-install 1.4.0, but would like to do so without overwriting current situation in Celestia root/data/extras/textures etc...
If you use windows Add/Remove to get rid of a previous version first, does this wipe everything in the Celestia folder including add-ons?
If you just install 1.4.0 over the top of 1.3.2 rather than uninstalling first, what gets replaced/deleted/retained?
I'd just like to have some certainty as to what I'm going to lose in situations where I just want to re-install the executeable, then I can backup the appropriate files beforehand.
I have a lot of customisations to solarsys.ssc, so I usually back it up before doin anything dangerous, but I don't usually backup anything else, and I'd like to know what else is affected (particularly if the extras folder could get trashed).
Is there an option on the self-installer to just install the program and leave all data, extras etc un-affected. For example, if you've made a lot of changes to solarsys.ssc over a long period of time it would be quite good to be able to upgrade the software without wiping customisations.
Also, how will 1.3.2 handle 1.4.0 features in .stc, .ssc, etc...
Can anyone recommend a straightforward procedure to follow to ensure that up-grade or downgrade of software can be done as quickly as possible while retaining customisations and add-ons?
I wasn't sure if the problem was due to 1.4.0 install, or changes I'd made in solarsys.ssc and nearstars.ssc (defined new barycenters), so I decided to re-install 1.3.2.
Can someone give me the definitive answer on what is wiped/retained on installs/uninstalls. Obviously solarsys.ssc is replaced, which makes me wonder what else could I have wiped out?
I seem to have solved the problem I was having and would like to re-install 1.4.0, but would like to do so without overwriting current situation in Celestia root/data/extras/textures etc...
If you use windows Add/Remove to get rid of a previous version first, does this wipe everything in the Celestia folder including add-ons?
If you just install 1.4.0 over the top of 1.3.2 rather than uninstalling first, what gets replaced/deleted/retained?
I'd just like to have some certainty as to what I'm going to lose in situations where I just want to re-install the executeable, then I can backup the appropriate files beforehand.
I have a lot of customisations to solarsys.ssc, so I usually back it up before doin anything dangerous, but I don't usually backup anything else, and I'd like to know what else is affected (particularly if the extras folder could get trashed).
Is there an option on the self-installer to just install the program and leave all data, extras etc un-affected. For example, if you've made a lot of changes to solarsys.ssc over a long period of time it would be quite good to be able to upgrade the software without wiping customisations.
Also, how will 1.3.2 handle 1.4.0 features in .stc, .ssc, etc...
Can anyone recommend a straightforward procedure to follow to ensure that up-grade or downgrade of software can be done as quickly as possible while retaining customisations and add-ons?