Attached you'll see a crudimentary tower I'm creating, C.
The problem is, I can't get it created because it apparently does not like the .mat chosen, a lovely Normandy stone by Linda, aka FrenchKiss.
All the mats are accompanied by a .jpg, but I've noticed the standard mats that came with Vue4 are not.
Are these .jpg's supposed to be in a place other than the file folder containing the associated mat?
I ask because, not matter where I put it, Vue isn't happy. If you'll read error A, that's what I get when I launch this particular file (even though the .jpg file is present in the folder along with the mat file. And no, the .jpg is not corrupted - it opens fine in several paint programs). Okay...so I move the file to the place it "looked for it," relaunch, and then I get the error B...telling me it can't locate it back in the original place I had it! What does Vue4 want? It's already so buggy it has my sanity.
So, I will yet AGAIN import the .jpg into the Materials Editor, D. Then a short time later, without any changes, it once again "loses it" E, and I have to import again.
During all this time, I get 2 or 3 modifications in on the tower (resizing, adding elements, etc.) before it has a fatal error. Yet, despite all Vue's grumbling about this .jpg, it still renders it even though it can't "find it."
I would have bagged this mat long ago but the client loves it. (I do, too) and my deadline is looming - can someone toss a few jewels of wisdom my way?

When FrenchKiss created her zip file, she maybe has not created exactly the same folders as when she has used the object. You can simly correct this. Open the folder where the jpgs of your object are. Copy these jpgs to a new subfolder called Frenchkiss or whatever you want in your Bitmaps folder. Launch Vue, open or import the object and when Vue askes you, locate the jpgs from the folder you have just created. When you have finished to do so, save your object again wherever you want (even in the original FrenchKiss folder). Now, every time you call your object from there, Vue will remember where the bitmaps are. Of course only if you don't move them:-) :-)Guitta

Thanks for the tips on the bitmap folder placement - I've gotten rid of those errors at last .
The constant quits remain, however. If I change the mapping or oversampling of the bitmap or - heaven help us, add a primitive or move the darn tower - nothing but fatal errors.
I'm not picking on French Kiss at all. I think most of this is the inherent instability of Vue4 for Mac. I remain breathless with relief that I didn't purchase Pro to start with, or I'd really be hacked.
Vue4 for Mac might be great for the talented (and determined) hobbyist, but it is a l-o-n-g way from being practical for someone on a production schedule. A 30-minute creation can take hours because of all the quits and lost data. Not to mention the constant tension you're under, WAITING for it to quit. I mean I've got backups of my backups - because even clicking on a Vue-generated .bak file creates an error.
However, if you can stand it, and you have the time, the results are astounding.
I'm done, now. :) Holly

Oh hi Walther, please answer here as a Mac user. Mac reacts differently then PC.

I'm a Mac user and have had this exact problem but have been able to keep it to a minimum by following this rules of thumb: 1. Always let the previews, all of them, redraw as you modify textures. When previews are done you can change another element. (Yes I know that the update has made this less of an issue but it's still an issue) 2. At the first "Can't find texture" warning, immediately cancel out of the texture edits completly. Then go back and start the edit again. (works about 95% of the time for me) 3. If #2 doesn't cure it, I'll cancel out of the edits again, save, quite and relaunch. So far, given Vue's render speeds, I'm still way ahead in time compared to using Bryce even doing silly things like relaunching! Guess I'm trying to make lemonade out of lemons here. :) Additionally, recently using Disk Doctor and Repairing Permissions fixed a bunch of goofy program quirks - besides Vue's - in other programs as well on my system. Now I Repair Permissions after every program update. Mark

Thank you, Mark, for the info.
It's my first 3D app and a whole new paradigm. The bugs have only complicated the learning curve. But I'm starting to get the hang of it because of people like you.

This child has many fathers. When I give birth, I swear it will be displayed for them to claim or deny!

Holly