@ Green Gandalf,
Quote: " its best to do a fresh install from scratch"
Quote: "Do you mean first install from the original file or CD then install that particular update? I ask because I'm about to install FPSC on a new machine so I'd like to get it right first time."
Install from the cd first, then select the version update you want and install that. So if you want v1.18, install v1 from cd then install the v1.18 update; if you want v1.20, install v1 first then the v1.20 update second.
--
Quote: "A lot of the problems with fpsc is user error more and more than bugs, the latest version is in fact very stable but the main problem I'm finding is people using older packs, maps and models in the engine."
I agree to a point. Levels constructed are the
biggest issue. Seems people do not realize each version handles the load/save data stream differently and have all sorts of issues when trying to open a level from one version to the next. Model packs are not so much an issue, at least from what I've seen. I run each version in a VM and have yet to see any difference in media packs (except one where a script had to be changed).
Quote: "Sometimes its a simple script problem because some of the commands have been renamed."
If I recall
currentweapon was changed to
plrcurrentweapon or something like that. There are a few others, but the number of changed commands are very few.
Quote: "the issue with these segments being invisible is solely due to their usage of "jpg" files, which are no longer supported by current versions of the software, easy to fix however."
Same with entities. V1.18 and up will require the textures changed as well. Only those of us that have JPG support can still use them. Of course, only if we don't need the shaders that is.

There's no problem that can't be solved without applying a little scripting.