- Wed Jul 23, 2008 11:42 pm
#276633
Hi Yugo,
I tried to duplicate this, and I think I can explain what you are seeing. Given that:
- Rhino block references do not support texture-mapping
- the material you used may have textures with projectors > 0
These two factors could combine to give you the effect you see. Since block references cannot be texture-mapped (the definition geometry gets the current viewport mapping 'baked' into channel zero when it is blocked), you may have textures in your material which do not work with the block. You would need to switch all textures to use Channel 0 in the Maxwell texture editor to get around this issue. This means that it is not possible to have multiple texture-mappings on instances - so this is a Rhino limitation regarding block references, and not really a Maxwell issue.
Also, regarding your other post, I did find one way to make it so that blocks do not export correctly: if I:
1. made some geometry
2. blocked it
3. copied the blocks
4. rendered successfully
5. deleted the blocks
6. purged the drawing
7. started again at (1)
In this case, the plugin did not find the new blocks in the drawing, and no instances were exported. If I then saved and re-opened this drawing, the instance table seems to have been fixed up and the references are now correctly given to the plugin when it asks for them. I would have to look into the code, but this seems to be an obscure Rhino SDK bug related to the Purge command. Please let me know if you think this seems applicable to the scenario you described.
Thanks,
JD
Next Limit Team