Hi all,
As you may know I abandoned cfs2autocoast development and support over two years ago. Last week I started development again. I'll be using this post to keep you updated as to what's going on (and to help me keep on track and focussed)
The following tasks are on the roadmap for the VTP1 creator:
- Routine for converting coordinate/width line data (in first instance from SBuilder SBX files) to polygons (80% Complete)
- Apply UV texture mapping (50% complete)
- Clip polygons at LOD13 intersections
- Create ASM file for compilation by BGLC
The new LWM's from Rhumbaflappy add 2 new tasks to this list
- Either use decompiled BGL's or Rhumba's sources as input for the VTP1 creator. In either case, the only problem I probably won't be able to solve is where to use "ocean shore" or "perennial shore" type textures....one size fits all...
- Find new source data for roads/rivers/railways that is compatible with the new LWM and preferably passable as 1940's infrastructure. This must also be editable, preferably in SBuilder.
That is, IF I'm going forward with using Rhumba's files..... I kinda would prefer to go on with the FS2002 data from a technical point of view; the shorelines are reasonably neatly mapped out, it all kinda works together, at a level of detail that CFS2 handles very well. On the other hand, using Open Source/Public Domain data is very sensible too. Decision pending! I've only just downloaded Rhumba's files (Thank You Ickie that the files are available again!) so I still have a lot of testing and deliberating to do over this.
The end goal is to have a directory full of source files covering the planet, and a single button "BUILD WORLD"
Once I start building a repository of SBX and other assorted source files covering the whole world, I'll set up an SVN (subversion source control database) in the cloud somewhere where we can share the source files for editing; if someone needs/wants to edit/add to any part of the world, (either for terrain data or airfields, landmarks, you name it), it is available for download, and the result can then be slipstreamed into the build. End users can sync the latest changes automatically and incrementally (after testing/approval)
Bookmarks