[solved] cfg files for sample maps?

Jon

21-10-2005 20:28:32

I must be missing a step. I am building PLSM2 from source, and have pulled down the sample maps in datasrcs.zip. This file has the raw unsplit maps as expected, but I don't see any of the cfg files.

I also note that Samples\Media\paginglandscape (which I assume is PLSM1) has the unsplit maps along with the CFG files. I'm not sure it would be a good idea to use those.

I see that the binary distribution has a Media directory with everything but the raw maps. Should we grab this out of that zip (if so, Paging_Scene_Manager_Installation should probably be updated, or the CFG files should be added to OgreSDKplsm2source.7z.

Directions on where to place the contents of OgreSDKplsm2source would be appreciated. For the most part, I have tried to stuff things in similar locations in the ogrenew tree. There isn't a PLSM folder like the binary distribution assumes. Perhaps this is the root of my difficulty.

Jon

23-10-2005 00:54:45

The result of my investigation into this problem: the config files were indeed in Samples\Media\paginglandscape. This directory was not a PLSM1 leftover.

The configuration files differ slightly from the ones in the binary distribution. One significant difference is that the grand_canyon page/tile sizes are different, resulting in significantly larger map chunks and significantly longer split times. However it is useful to compare the results with the two cfg files.

The other conclusion I came to is that it doesn't matter where the source for buildable pieces (maptool, demo, plugin) go, as long as there is a post-build step which copies the target file into the proper bin directory. So I personally chose to put the plugin with the other plugins, the tool with the other tools etc.

As an aside, I think it would make sense to bundle the .gen.cfg files, the .cfg files with the .raw/.png files when distributing maps. Some directions on modifying maptool.cfg, resources.cfg and paginglandscape2.cfg would be beneficial for those who were interested in building their own maps.

I see people taking an existing map (such as grand_canyon) and copying the .cfg files. Replacing the heightmap, changing a few settings in the cfg files and running it through the splitter. Distributing all the map-related input files separately from the source/binary distribution would make the connection clearer. Just distribute the plugin without any maps, and let people install them as desired later. This is an alternative to distributing the cfg files with the source, and the raw maps separately.

tuan kuranes

23-10-2005 07:56:48

Samples\Media\paginglandscape is plsm2 and plsm1 ans Iplsm.
But I'm thinking to rename it...

cfg file are different ? between OgreSDKplsm2source.7z and OgreSDKplsm2binary.7z ?

problem is .gen.cfg and .cfg might differs version from version but map data won't so it make people need to download maps each new version... wereas all the download size is in the map...

but I look after how to make next distrubution cleaner.