BlueBrick: Difference between revisions
(correct links to RB site) |
(minor edits) |
||
| Line 1: | Line 1: | ||
'''BlueBrick''', by Alban Nanty, is software for designing LEGO Train layouts. It has an LDraw output mode, and can produce either .dat or .mpd files. It also can read (but not write) TrackDesigner files. It runs on MS Windows systems | '''BlueBrick''', by Alban Nanty, is software for designing LEGO Train layouts. It has an LDraw input and output mode, and can produce either .dat or .mpd files. But since BlueBrick does not directly use the LDraw parts library, when reading a LDRAW file, BlueBrick may display unrecognized parts with a default "missing part" red cross image. | ||
It also can read (but not write) TrackDesigner files. It runs on MS Windows systems and requires .net 2.0 | |||
It uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are multiple types of layers, Grid, Table, Baseplates, Track, Assignment, and annotation. Thus one can do tables on a table layer, lay down roads and baseplates on a baseplate layer, and so forth. Layers can be reordered, and made visible or hidden as needed. | It uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are multiple types of layers, Grid, Table, Baseplates, Track, Assignment, and annotation. Thus one can do tables on a table layer, lay down roads and baseplates on a baseplate layer, and so forth. Layers can be reordered, and made visible or hidden as needed. | ||
Revision as of 19:32, 31 August 2008
BlueBrick, by Alban Nanty, is software for designing LEGO Train layouts. It has an LDraw input and output mode, and can produce either .dat or .mpd files. But since BlueBrick does not directly use the LDraw parts library, when reading a LDRAW file, BlueBrick may display unrecognized parts with a default "missing part" red cross image.
It also can read (but not write) TrackDesigner files. It runs on MS Windows systems and requires .net 2.0
It uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are multiple types of layers, Grid, Table, Baseplates, Track, Assignment, and annotation. Thus one can do tables on a table layer, lay down roads and baseplates on a baseplate layer, and so forth. Layers can be reordered, and made visible or hidden as needed.
Track and roads feature connection points to allow for easy alignment and there is an adjustable snap-to grid.
External links
- Alban's site for more information.
- The RailBricks site, issue three has a review and a writeup of what was determined about the Track Designer format