Hello,
Sorry for the lack of explanation regarding multi-markers in the help documentation. They are a somewhat advanced feature that can be little tricky to set up.
A multi-marker is simply a group of normal (single) markers that are treated as if they are a single marker. Multi-markers can be useful for scenes where parts of the marker may be occluded for any reason. As long as at least one of the single markers on the multi-marker is visible, the marker will still be tracked properly.
To create a multi-marker, you will first need a regular pattern file for each of the single markers that are part of the multi-marker. Then you will create a special .dat file that tells BuildAR the locations of the pattern files and how they are positioned relative to each other on the multi-marker.
The .dat file is just a normal text file, and you can create it using a text editor like Wordpad. The format of the .dat file is explained in this image:
http://www.hitl.washington.edu/artoolkit/documentation/images/multiconfigfile.jpgI've attached an archive to this post containing a sample multi-marker .dat file along with the individual pattern files. You can edit the .dat file to use your own pattern files.
Please note that the paths to the pattern files in the .dat file need to be relative to the BuildAREditor executable.The transformation matrix part of the .dat file entries may seem confusing, but you only need to worry about the last column of numbers if the patterns are all facing the same direction. From top to bottom, the top three numbers of the last column of the transformation matrix represent the x,y,z position (in mm) of the current pattern file relative to the origin of the marker. You don't need to worry about changing these numbers if you are using the same layout for your multi-marker.
Let me know if you need more help with multimarkers. My guess is that you do not have the correct file paths in the multi.dat file. Make sure the the file paths to each of the "abcdef" patterns is relative to the BuildAR executable.
Cheers,
Giles