CompuServe Messages

Hi Kevin, Concerning the city master file: I can see two ways to go with this, I posted a question in DEVCOM to seek feedback. My initial vision was for a fairly low-res city, like oldcity.3ds, but customized. In this vision the master project file would be basically the street layout, with plots of land delineated and numbered. This would be downloaded by all interested developers. Once a developer is cleared to develop a tract of land, they do so, basically expanding their personal project file. When done with their tract, they save their project file, then go in and delete everything that isn't new, except for a few reference points on the map. They also double-check to make sure they've followed all organizational requirements. This smaller file is then uploaded to the library. Another person can then download this new file and merge it onto their own project file. The "master" file in the library does not change; it is just a common starting point. Each person's project file at home, in essence, becomes THE master project file as long as they download everyone else's tracts and don't manipulate anything. People can render views at their leisure, and some nice images can be uploaded to the libs for all to enjoy. It might be useful for someone to upload their "master" project file ocassionally, so new developers don't need to do countless merges to get up to date. A second vision of this city could be more involved, with a lower likliehood that everyone interested would be downloading everything, because of the increased complexity, rendering time, and CIS time involved. In this scenario, there would be the same master file in the libs as a basis for development for everyone. But there would also be a Keeper of the Project, who was responsible for downloading everything and merging it, and arranging for rendering sample views to put in the libs. This may be more of the vision you and Sanford Kennedy have been discussing, especially if this becomes some kind of highly photorealistic venture. See ya, Paul S.