Probably not the most easiest part to start with if your new to Citect. I know Bradley (one of the moderators on this forum) is working on a document 'Building Composite Genies', but I don't think it's finished yet. Creating your own composite genies from scratch is not very easy. I developed some composites and to speed up I started by copying an existing composite, preferably one which looks like an existing one. There are two UIDs in the file, you have to replace them by some new created UIDs. You can them start playing by modifying the composite xml. If you make a modification you can check directly if it doesn't contain error in the Graphics Builder. If there's an error it pinpoints you to the exact location of the error. You can also monitor directly what the composite will look like in Runtime. If you have worked with XML before things get easier. The hardest part is always figuring out what you have to create / how it should look like / which options should be available. Good luck!
Probably not the most easiest part to start with if your new to Citect. I know Bradley (one of the moderators on this forum) is working on a document 'Building Composite Genies', but I don't think it's finished yet. Creating your own composite genies from scratch is not very easy. I developed some composites and to speed up I started by copying an existing composite, preferably one which looks like an existing one. There are two UIDs in the file, you have to replace them by some new created UIDs. You can them start playing by modifying the composite xml. If you make a modification you can check directly if it doesn't contain error in the Graphics Builder. If there's an error it pinpoints you to the exact location of the error. You can also monitor directly what the composite will look like in Runtime. If you have worked with XML before things get easier. The hardest part is always figuring out what you have to create / how it should look like / which options should be available. Good luck!
