Anyone have this problem before?
I open a model (a simple lathed waiter's tray shape which I made in the Vertex modeler), which I'm looking to texture with a photographic jpeg image of a woven basket. So far so good. I get into the texture room, and have no problem applying the texture as a normal shader. But I'm interested to see the result if I use displacement mapping instead... so I click on the "Displacement" tab in the shader and go to "Texture map" in the drop down menu, so that I can load the jpeg image. Am I right so far?
Because, BAM! when I click on "Texture map", Carrara disappears in a puff of smoke (well, it crashes).

So, I've tried doing the same with a bog standard cube, with no problem. I've also saved the textured and displacement mapped shader, which works fine with standard objects, but crashes and burns when I drag it onto my .car tray model.

However, I tried saving the tray object as a .3ds file, and there is no problem when I apply the shader.

This tells me that there is an issue with the tray, but only the .car version? It's such a simple shape though, what could be the problem?

I've tried several times, with the same result each time. Does this confirm me as a klutz?

Not having seen the object, there is obviously an issue with it - an issue that you've found an way to work around with the export/import option. It could be an open polygon, overlapping points etc. Those types of items are usually fixed during an export. Haven't had this issue myself though. :-/

Thanks for the speedy response, Mark. I'll go back and check the vertex model to see if I can find the problem.
I'm a Photoshop jockey, and all these points, vertices and polygons are fiddling with my head!
Onward!

That's odd because I've always been pleased with how robust Carrara5's displacement is. I usually import models that I've built in Wings and exported as .obj models, but I'm slowly getting the hang of Carrara's vertex modeler. I use Carrara standard on a fairly old system and the displacement has never caused my machine to bog down or crash. It could be because I often use procedurals instead of a jpeg or bitmap.

I've checked out the original geometry, and can't see any problem... but I am a noob so I may be missing something. It's a simple profile with a simple lathe action, so I may try remodelling from scratch to see if I get different results.

You might want to try a sweep instead of a lath and see if you have the same issue. Different methods can yield different results.

Thanks for the tip, Mark... I'll give it a bash.