I just got C4 and it seems very unstable. I have a dual 3.2 cpu PC with 1 gb of memory. I had C3 and there was none of the problems I'm having now. I'm trying to use the terrian modeler and it keeps failing in memory allocation and rendering failure. Any ideas? Thanks.

Post a message screen. Is it failing the same way for the same operations? Or failing the same way at any point while in the program? Is C4 the only program causing the errors?

It does seem to fail the same way for the same operations. I'm trying to use a 6800 x 6800 gray scale map for the terrain and the same size texture map. The wire frame render option fails in the assembly room and it fails to render during final rendering. Maybe Im asking too much from C4, but it says it will do terrains up to 8193 pixels, but I get memory allocation errors at the setting. I would think 1 Gb of memory would be adequate, maybe not?

You aren't asking too much of C4. 1.) If you can reproduce this on cue, send it to support@eovia.com with a good explanation of how to reproduce it. 2.) The code must have memory issues in lots of things. It has video problems for me on both ATI and Nvidia cards, it gets weirded out when I use the metaball modeler, it suffers when I have lots of things turned on during assembly work and am doing lots of preview renders. The code is buggy at the moment but Eovia will fix it (I'm sure about it!). Make sure you send Eovia an email. -Kix

Hmmmmmm vhigh, just tried to reproduce with a 6800x6800 and everything work well here. Eovia tech is very aggressive at fixing platform/system issues. Pass it along ASAP and hopefully it will be addressed soon.

Kix, I know during beta, video drives came up periodically. Make sure you're using the latest and greatest. (I'm sure you are but I have to say that!) I've had some pretty robust scenes where everthing was ok after many previews. Don't you just love hearing that? Same with Metaballs...all ok.

I am so glad I'm not the one writing code to make the software work on all the platforms and systems that are out there.

Message edited on: 11/09/2004 15:18

I have had a lot of wierd things happen with C3 including the "Rendering failed". I usually find that if I copy all my objects and paste into a new document often the new document will work correctly. (Restart C first) Sometimes it is difficult with a large file to accomplish this, sometimes I try to split it up, but its worth a try. You can even open a .car file in a text editor to look for obvious corruption.

Message edited on: 11/09/2004 20:27

I got an error in line 44 message in Carrara Pro 4 just now. I was deleting objects and importing others into a scene. I was able to save the scene and exit/restart CP4 and load the scene and render it without trouble.

I have to treat CP4 the same as C3 it seems.

Message edited on: 11/10/2004 00:09

This is a real bad news i hear now from the group as i always reach this bug with the C3 version (i do heavy scenes !!) . My first concern to upgrade to CS4 was this bug i expected to be corrected. I have 2Go RAM, and the bug occurs before than the whole system reach this limit ! My opinion is that it related to HRDI rendering most of the time..but bad bad bad news for the CS4. I've been in contact with Eovia support a few month ago for that bug (that they told me have reproduced) and it stills there ???? Nothing more frustating than spending days in texturing, modeling, setup lights / shadows and so on, and when you ask for the final render with good parameters, then ALWAYS come this infamous message " a memory allocation has occured".... This news definitely spoiled my day :-(((

Yeah, I've had the line 44 error with C4Pro, generally when trying to save a render. There's a work around for that particular error - the file will save if you over-write an existing file. But having had that one I expect to get others... it's grim. I love this software but sometimes it tries my patience. Also I can't quite get over the idea that Eovia rush things out. There are still no presets with the NPR, which seems pretty silly to me...

Hi, I just received my CS4 pro copy and i've jumped into rendering of some "heavy" scenes that were fu*** up by CS3 because of that "memory allocation error". GOOD NEWS : this bug vanished in the air !!!! I can render the previous scenes i've never been able to before :-)