Hi guys, there are two things I would like to respond to.
Clive, I have two zip files about making sm models, including exes, bat files and how to documentation. All dated around 2011.
One called smExample.zip, the other MkSMTest Folder.zip. Between them I would think comprehensive tools for converting m3d models to .sm models. Very happy to upload these to mediafire and share.
Back to the landclasses.xml, the simple change I made was to point the various city landclasses (ID 31,34 and 47) to a correct lso file. Where entries were 034summer2.mos and 034winter2.mos, they incorrectly pointed to 034summer1.lso. I changed the entries to 034summer2.lso.
Going to the mos file, the textures referred to in 034summer2.mos are:
a_034summer2roads.dds and
a_034b2su2_trees.dds.
These two texture files look like this:
These two texture files can be found in the terrains folder of CFS3, in the lcmosaic.zip file.
What I would like to do is to sharpen up the roads texture sheet - 034summer2roads.dds. I have no idea whether this will turn out to be a good idea or not.
@MajorMagee, would you like to take a look at that dds file and see what could be done to sharpen it up? Presumably the file will need to be larger. It can be tested by throwing the file into the assets folder where it will be used in preference to the original.
As far as new scenerymodels go, I'm a bit vague about how they get included in the autogen system of object placement. Do they need to be included in lso files?
To me, working on lso files looks like a fiddly and slow job. The scenery improvement I've posted about here was quick and easy by comparison.