Ah, I'm glad that you got started sreckoM. Thank you for the results too, that helps.
1 . How to create exit portals?
Any mesh with name starting by
ExitPortal will be an exit portal to Indigo. Trivial, I will certainly change that
ExitPortalWhatever is a valid exit portal name.
2. Can I set value of emitter as lumens (same as in Blender)?
Not at the moment but that could possibly happen in January. Default Indigo units still apply.
3. Is it possible to import materials (created with material editor)?
Again, not at the moment, but material linking is possible. Command:
Select the mesh(es) to link the material to then run the procedure. Next, browse to the desired IGM definition.
Material import is absolutely of an high priority, coming right after the critical initialisation issues we are currently dealing with
4. What is procedure for creating instances?
Command is:
First select the mesh(es) to create instancing locators for, then run the procedure. Instancing locators can be duplicated etc... Don't forget to tick "export MtI instancing locators" down the OUTPUT pane.
Now you can try this, that's an option:
Start Maya, do not initialize MtI. Load the indigoPlugin manually if that's not automatic yet. From the Hypershade's Create Node pane, create a
Spectrum Node (down
Color Utilities).
If the Spectum Node AE shows a structured layout, then we should consider the init issue fixed for the next (soonish) version. If not I will need to know please sreckoM.
NB: executing mti_init; will load the plugin if it wasn't already. Auto-load is not required.