I have c5 standard on XP Pro  My Carrara File Version is 5.1.0.57.  Most of the time it works..but it has started crashing for reasons I dont understand.  I'll usually be clicking on something and C5 just dissapears...process gone.  No error messages.   I also usually get the default user interface settings when I restart the app.  So...how do I resolve this?  Is there a log file I can read?  I have not asked for official support...do you email Daz or Eovia...and will they respond?

I'd also like to backup my usre prefs is someone knows where they are kept.

Thanks

Yeah...if that happens that's how it goes. Dr. Watson/app crash log is about it. daz3d.com/bugs is where to report bugs. Make a seperate acct. The prefs aren't so easy to backup like hex. I think it is in main directory.

Could be Windows.

Same thing is happening to me only I've got Carrara 5 Pro and it's happening when I render.

I've cleared unused objects and shaders, checked the poly count which was under 200,000. The objects in the image render fine separately and image size is the same I've been using.

I've got 2G Ram ,dual core Athlon processor and the video card has 512MB , so it's not something beyond the capabilities of my machine.

And as if that isn't enough, mapped textures are disappearing when I save the file and reopen it.

I definitely would appreciate if anyone has any ideas on what is going on because I haven't changed a thing.

I don't have a solution....my crashing was apparently caused by some eval plugins/extensions I had installed.  I'd recommend submitting a bug report to Daz if you have not already done so.  They did get back to me and seem willing to help track down such problems.
http://www.daz3d.com/bugs/signup_page.php

Thanks, but I went that route last time and still haven't heard from it.  I'm glad you had better luck.:)

I was just hopeful someone might have figured out what causes the erradict behavior. Could end up being one of life's little mysteries.  Without some kind of error message, I could see where it would be a bit difficult to track down.

Nightwind.. sorry, but w/ that amount of info hard to say. What do u meant by the textures are disappearing? what r u using to bring them in? are u saving them internally? Sometimes if u don't it can lose where the maps...are...if they get moved. And yes plugins thro another equation in the mix. I would report it...can't hurt..if u are getting crashes.

The textures are applied and working when I save, after the crash, the textures are no longer there. These are mapped textures from Daz objects that have been imported through native importer or transposer2.  I've tried it both ways and it doesn't seem to make a difference which I choose.  The only thing I can find in common is that the "dropped" textures have transparency applied in some manner. If I don't save the textures continue to be applied until I finish the image or until Carrara crashes, whichever comes first.

I understand that if it crashes while saving, then nothing is going to be right, but if the save is successful, and the crashing occurs during rendering I would expect the textures to still be working if the object is still included in the scene.

I don't save them internally, as I have been told that makes the file bigger and more apt to crash during saving, but my link to Poser is correct and as I stated, no files were moved. 

I've been dealing with this problem off and on ever since I got Carrara 5 Pro. It seemed to get better for a bit, but now it's worse than ever and I haven't changed anything on my system or with the program. I still haven't heard from the first bug report I sent in, so didn't see much use in sending in another one. Only difference now is I've used Carrara enough to learn clean out unused objects and shaders,  and to keep a check on settings after crashes occur.

Yeah u have to clean out the unused master objects and shaders. Saving internally should only add to file size on disk. The file has to load all in mem anyway so for mem usage I can't see that mattering. Have I actually tested this? No. Transposer actually stays linked to the original poser file so not sure how it will save them anyway if something happens. There is a link between them. Don't use poser so that's about all I can say there. For native should keep them fine and if it happens alot just keep them in the file. Haven't seen this or had it happen. Also on XP you can save your prefs for hex and c by going to documents and settingsuserapplication dataeovia, I believe. xml and text files w/ prefs and settings. 2GB of ram is really a good amt. Can use more, but won't notice too much difference. In some cases maybe. Can use less, but I wouldn't try poser stuff w/ less than a gig. Very high poly. Can check your commit charge in windows to see how high it is climbing.

I sometimes get  an "Unknown Error" window with "Cancel" and "OK" Button which sometimes does not work and I have to re-boot.

I'm running

I.B.M Thinkpad T42P + 2GB Ram with Windows XP Corporate Edition.

One Error that is guaranteed to come up is if I  Insert a Replicator and than drag and drop a group of objects into the Replicator and than switch to the Render window to render and It crashes.

I can save the file, re-boot / re-load and render and it will be fine after that.

I'm just starting to live with the crashes and continue but they can be annoying.

Are u using any plugins? Hopefully u r not using replica, which won't support grps.  If u can I would also upgrade vid drivers altho...doesn't necessarily sound like an issue. Hard to say w/ that info. There have been some nasty limitaions particularly in polygon support in earlier ati drivers. Try double clicking on the replicator instead and setting things from the interface to make sure they r set correctly rather than dragndrop. Also remember to constantly clear unused master shaders and objects...they really can accumulate.

Quote - Are u using any plugins? Hopefully u r not using replica, which won't support grps.  If u can I would also upgrade vid drivers altho...doesn't necessarily sound like an issue. Hard to say w/ that info. There have been some nasty limitaions particularly in polygon support in earlier ati drivers. Try double clicking on the replicator instead and setting things from the interface to make sure they r set correctly rather than dragndrop. Also remember to constantly clear unused master shaders and objects...they really can accumulate.

No plugins at all.  However I do it have an ATI Mobility Fire GL T2 video card.  I will check to make sure the drivers are up to date.

I sometimes get the "Unknown error" for not good reason.  usualy shutting down the application and re-opening will clear up.   Other times rebooting my laptop will fix it.