I haven't tried this trick with animation tmp files but the Vue cache of texture files should be in in your Windows/Documents and Setting/[Username]/temp folder (assuming you're using a PC). I've used this to retrieve the alpha maps for Vue's plants.

I tried the tree over a sphere thing too. It turns out that the vertical position value is harcoded at -180 to 180 so you can never have trees or object completely encircled. I spent a day trying to do this before I learned thi unfortunate fact. I think the EON guys will have this in a future release.

Hyperthreading is a total joke when it comes to rendering or any other computationally rigorous application. Unless you have an application that is perfectly optimized for HT, you will not see a performance gain, and in most cases you will see a performance decline as illustrated by Max3DD3. Best to turn it off in the bios as see for yourself. The reason your P4 shows up as 2 cpu's is that HT is turned on, which is a software gimmick that makes the OS think that there is 2 cpus, when in actuality there is only one.

This is a common misconception. There is no difference in screen fidleity between a 72 dpi 4000 x 4000 image and a 300 dip 4000 v 4000 images. The dpi is just for printing purposes. A 4000 x 4000 at 72 dpi image would equate to a printing size of 55.5" x 55.5". A 4000 x 4000 image at 300 dpi would print at 13.33" x 13.33". Just figure out what size you're going to need and for what purpose. For high quality magazine work, 300 dpi is the standard. So if you needed a 5" x 5" picture, you would need a graphics render resolution of 1500 pixels x 1500 pixels.

It seems that even if you re-install a cow, VUE will try and update it with the faulty beta update. The only way to avoid this for now it appears is to revert back to the original (non updated) version.

I tried this and it doesn't work. It just points the ecoobjects downward but still does not fill past the top of the equator -- thanks anyways

Awesome work - I salute you!

Wow! That was easy. Now how about a tutorial on how to use the Smart Graph Funtion Editor. I have read the ref manual on this three times and I still don't understand it.

Okay everybody - take a deep breath - relax. I'm relatively new to the R'osity art world but it seems to me that the TOS is not an intractable position. It's just an attempt to play it safe so that R'osity and its parent company don't get sued -- which is quite understandable in this litigous world we live in. Why don't we try to communicate with R'osity and see if there is some middle ground. Basically what they are trying to do is to steer clear of the child pornography laws so bullet three under the TOS would seem to be okay - "No depictions of young humanoid characters/children giving the appearance of being under the age of 18 displayed in erotic, seductive, provocative poses or context" - the other rules seem to be an over-reach and would not run afoul of any child pornagraphy laws. If they kept rule 3 and added that it would enforced under the "discretion of the Renderosity team", I think the solution could be workable for all.

Attached Link: http://www.renderosity.com/viewed.ez?galleryid=918141&Start=1&Artist=dburdick&ByArtist=Yes

Very cool indeed

I think the lighting looks excellent for this type of scene

I got the e-mail as well and I wish Dave the best. That said, it might be a good idea in future for E-On to cross-train others in the organization to take his place or reassign resources temporarily to the shipping/fullfillment area. These kinds of things happen in business all the time. I really respect E-on for sending the e-mail to explanin the situation which shows they are a quality company.

The memory leak problem is not a static problem. When you check your GDI handles after starting VUE, check it again after opening and after playing around in Vue for 10 minutes or so. If you see this number increasing significantly, then VUE has a memory leak caused by not releasing discarded GDI objects (e.g. popup menus, graphic object caches, etc). Memory leaks are tough problems to solve and often crop up when adding new functionality or in new releases of software. The only workaround is to save often and then quit and restart VUE after a certain time interval. I do this around each hour of working with VUE.