Well after having a very long break from Vue, I was feeling creative today, so fired up Vue 10 complete, made a scene, moved some things around, did some test renders all ok.

Then moved the camera and repopulated the ecosystem, and now whenever I click render, the bar at the bottom gets three quarters of the way and then just says render aborted. Oh dear, not a good start for me and Vue 10.

Anyone else have this or seen it before?

Regards

Jon

not personally, but i don't have Vue 10... my suggestion, shut down your computer, let it sit a minute, then start it back up.  Make sure all programs running in the background that aren't needed are off...

For me, vue just crashes whenever i push things too far and my computer is "tired" LOL.  Usually a nice shut down (NOT reboot, as in my opinion - could be wrong there - a reboot doesn't dump EVERYTHING out of the memory) fixes things.  (yes, my computer has a personality - a bit cranky sometimes, like it's operator LOL)

hope this helps...

~meli

Thanks Melika for your reply.

Its not the computer I promise you, its a quad core, 8GB 3D eating monster machine lol. The scene itself is quite simple really as well, however, no matter how much I have my own self belief in my machine, I did restart Vue, and low and behold it started rendering the scene.

So there you go folks, if it all fails on you, restart Vue, I will get one version one day that works all the time lol

Regards

Jon

LOL - yeah, sometimes Vue itself has a temper tantrum!  My "monster" computer is one of those (really) low-end Alienware Aurora's... single core, i believe, but it acts like it has 8 cores (and sometimes this causes problems... talk about split personalities!) ...  and with 16GB of ram, it SHOULD handle everything I throw at it.  NOOOOOOOOOOOOO.  (again, split personalities... one gets mad and stomps, taking my render data with it...)

Keep up to date on your Vue "fixes, patches, and updates"... as they find little issues, they do try to fix them (usually... ok, sometimes... ok, every once in a while!)

Also, the rebooting of the computer isn't just for the computer - when vue throws a temper tantrum, and a simple restarting of the application doesnt work, it's usually cus Vue has "stomped" on your computer's "toes" and made it cry.  ;)  (again, personality thing LOL)

But glad restarting Vue helped... shoulda suggested that first, but (we know what happens with assuming)... well, i assumed ;)  (gotta stop doing that!)

And good luck with getting a version that works all the time... with them cranking out new ones every 6 months or so... i don't see it happening any time soon.  It'd be nice if they'd take a break from making new versions and FIX the ones they have out, THEN go back to creating a new version, making sure it is stable and works the way they promise before creating yet ANOTHER new version.  Or even if they just went back to releasing a new version every year instead every 6 months, giving them time to get the last version 99.9% stable before launching a new, buggy one.

ok, personal rant /off.

LOL

I have been using Vue since version 4,  5 was the most stable for me, after that every version I had has been a nightmare.

To be honest I thought Vue 8 would be my last version, going to see how Vue 10 goes, but not off to a great start, but time will tell

My first version was, i believe, version 6 (esprit, then i added all the packs to it)... it wasn't too bad.  then came 7infinite, and BOY did I have headaches until it finally stabilized.  Then I jumped to 9.5infinite, and as long as I don't sculpt terrains, it "usually" does OK.  something about the terrain sculpting and running into the billions upon billions of polygons... YIKES lol.  (its a tool I have to learn how to control.... or put a clamp on my imagination!)

If you've done preview renders before doing the main render try purging the memory in Vue 10 under File>Purge memory.

Since Vue 8 it's been a good way to make sure that Vue isn't caching stuff which hogs the memory when you go to do the actual render.  If you are still having problems try rendering to image instead as sometimes it's a video card issue.

Jonj1611,

Did Vue say you were low on memory a least before aborting the render?  That's the only reason why Vue halts mine (since I have only 2GB and I'll accidently do an ecosystem that is too dense for my terrain).

Vue 8 used to crash all the time on me with just a barebones V3 with no skin or cloths, but that was because e-on kludged their PZ3 import.  Smith Micro ended up having to write the Poser import code for them which e-on never bothered to rename.

Anyway, Vue 10 Infinite has been the most stable for me even with the current logic bugs it has.

No, it didn't say anything about low memory, it was quite a simple scene in all honest, not entirely sure what happened or why it did what it did :/

Still got a problem with my rendernode deciding it wants to quit like twenty minutes through a render, its happening when using internal network, but is getting right on my nerves lol

Rendernode?  That is a different beast.  I don't have another system to test with.

Yeah, the rendercow thing, its installed on my other pc, and the bloody thing turns itself off when it feels like even half way through a render, the Vue 8 one that was on there never used to do it.

Are you using static IPs or dynamic?  Are you forcing the IP numbers into your host machine?  Or are you letting your host search for and find the rendernodes on your network and use the IPs it finds? 

Dynamic IP's, and no the host machine is finding the rendercow itself. More to the point its finding it as soon as its launched on the other machine. So I know its not a communication problem plus the fact that the rendercow is actually rendering.

And it doesn't just stop rendering after a random amount of time, the rendercow actually quits.

You have a router then that is assigning IPs to each of your computers?  Are you able to render Vue's default scene with some spectral clouds thrown in using rendernodes?

Yeah the router is DHCP, I can render anything on the rendernodes, well until the rendernode decides its had enough and quits :/

What's the health of the renderbox? The cows will hit the swap file when they exceed the system's ram, but if you have a bad memory address, that will kill them instantly. And something like a bad bit on a RAM chip, if it is in the areas where things are rarely accessed, you could never know you have a potential problems. CG apps and games are the programs that tend to eat enough memory to encounter the issue. Have you run one of the downloadable memory checkers and tested the system?

The other options that spring to mind is the renderbox may be overheating. It is also possible that the last update corrupted, or didn't apply itself. Another possibility is crap in the registry. Every dangling registry entry is a potential crash point, either for an unlucky app or the OS as a whole. So running a registry cleaner is a good idea; programs never uninstall themselves as they should.... 

I thought of many of the things you did Dale B, the box itself is good, memory all checks out as does the hard drive, its a fresh and patched install of Windows 7, ram is the same as my current machine at 8GB. However I am starting to suspect it maybe overheating, but its set to shut down when it overheats, and I have neverheard of it just shutting down one app if its getting too hot.

I may try and uninstall the rendernode and reinstall it, see if that does anything, the logs are next to useless to be honest after viewing them, they just stop half way through at which is probably the point the rendernode decides it wants to depart this world.

Thank you for the suggestions, they are appreciated.

I have decided to ask e-on technical support for help on this because I just can't work it out.

Vue 10 crashes on the main machine when loading sample files.

Though my own scenes are ok.

And before anyone says it, my own machine is perfect working order. Its Vue, as has done in Vue 6,7,8,9 and now 10 it seems. :/

Thanks for all the help everyone

Jon