Hello everybody: An yet another topic of discussion. I'm trying like crazy to get the hang of the free Amapi 5.15 that came with Carrara. I know it's a great modeler and I'm starting to understand it a little bit thanks to the Amapi forum and this guy Brycetech and his tutorials (pretty amazing stuff) So far I've managed to create some pretty weird organic shapes thanks to the smoothing options of Amapi. Then I export it to Carrara (as a Ray dream studio file) and it looks smooth and great (with no shader), but as soon as I try to texture it the problems begin: Forget about using texure maps or a rectangular layer, it just goes screwy. And If I drag and drop a procedural shader all I get is a noisy mess that kind of resembles the original shader. The only ones that work are plain colors and simple metalic textures. (see attached picture) Has anybody been able to fix this or should I just forget about using Amapi in cunjunction with Carrara.? I think that Ampapi 6 exports directly to the .car extension. Does this help? should I get Amapi 6...? Or is there a work around. I really don't want to spend on a program that won't work on Mac OSX... I'm trying to make the switch Thanks in advance for any advice. Sicerely F. Velarde

Hi, Have you tried exporting them to another format that Carrara supports? Maybe like 3D Studio or DXF? Regards, Paul

Try this: Import your amapi object in Carrara and export it in wavefront/obj format. Import in Carrara your wavefront/obj and it works good. If you aren't satisfied you can change the projection mapping mode in the texture editor. You can also try to change the mapping mode in the vertex (with double click on your amapi/RDS object). Good Luck, TOXE

Thanks: Yes. Yesterday I stayed late ant tried exporting to other formats. I exported as a 3D Studio an then sent it to the vertex modeler. From there I changed the mapping mode and got good results. Funny though that I could never make the RayDream Studio format work ; as hard as I tried... that's what got me frustated. well I'm happy there's a work around : )

I think the problem comes from the procedural textures . Most of them are generated from local coordinates, so they are affected by the size of your object in its modeller . When you import in RDS format, try to edit your object in the VM and resize it down a lot . Then you can edit its properties in the Assemble Room and change its overall scale . See if it helps .