This is what I received from the support (they managed to be more responsive at last), first you can read our questions, and then their answers.
1_ I have just followed the instructions provided by one of your tutorials testing a simple brick materials on a simple plane lighted by 1 corona light: As soon I start rendering with corona 3ds max freeze and does not work anymore, seems that displacement (0,5 cm) Is causing the problem. I managed to do a rendering without but of course we need displacement to work properly.
1. This sounds like it is Corona specific. Or it just takes very long period as the displacement structure might be quiet complicated. We've never seen problems with displacement maps for example with VRay 3 or scanline. We will have to investigate that on our end I am afraid. Which Corona version are you using?
2_According your tutorial ( I noticed max 2012 has been used)I should be able to preview in my viewport: gradient maps of any loaded pattern, bitmaps with material Id of different patterns and I should be able to preview randomized JPG of patterns (bricks in my case). Nothing of this is actually happening using the current 3dsmax slate material editor.
I have tried to use compact material editor and in this case I am able to preview maps; however maps are not shown in the correct scale and I can’t see the variation of the pattern when JPG are loaded.
This is very weird also because when I do a rendering test (no displacement) maps appear to be rendered just fine. Basically my viewport is showing something has nothing to do with what is rendered.
2.Well Corona's viewport rendering support AFAIK is known to be very limited supported. If you use Corona materials. Omnitiles map itself does not yet have the viewport flag supported. So I don't think you can set the viewport shading on it. It wouldn't be hard to support on the map itself but it would require to switch your viewport texture size setting down to a reasonable map size, otherwise updates will take long. As 3dsmax offline renders a bitmap that have no native Direct3D shader to use that as a texture for the shaded viewport. I have to confess I am puzzled why slate is behaving differently to traditional material editor (Personally I usually use the classic editor most of the time) but that might be because the viewport shade support in Omnitiles itself is not implemented yet and relies on the parent map/material which might not work correctly with Slate. Is that something you only see in combination with Corona parent materials or even 3ds max standard materials?
3_Generally the speed the plugin is working at is very slow, but that might depend from our network??; However when I try to delete or to load a map, VP Omnitiles modifier does not update or it is very slow at doing that.( slate material editor)
3. This could maybe be because you have a large number of rows and columns in your tiling or a pattern that contains many shapes?
