i just have to scream, here.... AAAAAAAAAAAAAAARRRRRRRRRRRRGGGHHHHHHH!!!!!!!!!!!!!!!!!!!!!!! okay, now i know vue is flaky about resuming renders to disk from the get-go. so i should have known better than to tell it to render to arabesqueg1.bmp instead of arabesqueg1.vue.bmp. but i was smart, you see. i copied my arabesqueg1.bmp from my f:svuepictures directory to my stupid 'my pictures' directory, and even made it say .vue.bmp. just in case it rendered where i wanted it to, it had the file in BOTH places. and yet, both .bmp and .vue.bmp look like this. which leads me to say, "vue, where the @(&%#&% did you put my image!!??!" or perhaps, "what did you DO with it after rendering for nearly 80 hours over the course of two weeks??!" :: to top it off, i can't get vue to tell me where it thinks it goes. because when i hit 'browse' on the 'save colour image' dialogue, nothing happens. i can't browse. which, okay, is pretty much a safety feature, since changing where vue wants to put the image will mess up the resume rendering. but did it have to be WORSE than it used to be? with the .vue in there? and to 'my pictures' instead of vue's directory? ::sigh:: and DO i still have to, in ver 5 (regular d'esprit), save the file after each rendering session? which i did! but i noticed it has a separate 'saving resume render info' status bar, so... i dont know, maybe the resume render info is somewhere besides in the file? but, faithfully, i hit stop render and then re-saved the file, so i could open it next time and resume from where it left off. ::sigh:: well... at least the 16/32 min/max sampling on the soft shadows on the floor plane look smooth. so far. from what you can see of them.

With the danger to start another flame - i reported that to technical support. I had a problem as well when i did what you described.

Sorry bloodsong...I feel your pain, but I'm laughing...not at your missfortune, but because I remember the good ole days, many moons ago, when you use to come on here with your tails of despair...oh, its good to see you've not changed....or should I say "oh my god! Vue hasn't changed!!!" lol! Cheers

try My Documents -->E On Software or some such sometimes puts them in there for me

You can also look in My documents-My pictures-e-on software, I think that's where it always wants to save my images to.

Ah yes, Djeser is right! :)

To keep you updated, the following email i got right now: ####################### This e-mail is to let you know that a response to your message #1123504161 to e-on software online support services has been posted by one of our technicians. The e-on software support technician responded: Hi Walther, Indeed, I could reproduce this problem. I will tell our development team about this. Thanks for reporting it. Best regards. ################### And hopefully the problem is out soon. Response was - you can see it in this thread. From original report of Bloodsong until this answer from me. Not too bad i think.

Hey Bloodsong..are you working on a vulpture?..missed that one in your Eagle Expansion 2! ;-)

Hey Bloodsong..are you working on a vulpture?..missed that one in your Eagle Expansion 2! ;-)

I'm always afraid something like this will happen on my long renders. When I close Vue for an internet surfing, I save the image and scene file in their project folder. During the save, I always add an incremental number to the file names. For example, the file names go from 'Project 120-001' to 'Project 120-002' and so on. The '120' is the 120th save while the '001' & '002' are the continued render session versions.

heyas; yes, i still have the agony of artistic defeat :) (wait, why am i smiling? well, okay, it IS funny.) no, no vultures. nor vulptures either! now, sitting blue... if you resave the image and file as a new name, vue won't be able to resume the render. cuz... i dunno, it's looking for the resume with the old name or SOMEthing. see, i used to do that, and i'd end up with like five patchwork files with different slices of the picture. (which, fortunately, could be spliced together.) and i told yas, the picture i saved in the vue/pics directory and the one in my documents/my pictures/whatever e-on, is exactly the same as the one shown above. (although 3000x instead of 256x) it just... aint rendered. ::sigh::

I had problems with render to disk of large stills with Vue 4 Pro (haven't done that with Infitite yet). I found if I cleaned up my hard drive and defragged, it would usually render to disk ok then. Even if my hard drive had been recently cleaned/defragged and there was plenty of space on it.

I haven't had any trouble resuming renders to screen, even ones that go on for many days. In SW FL, you cant just leave your machine run this time of year (too many heavy thunderstorms with power blips, etc). I don't change the name and resume render works just fine. But I do save the file every time. Fortunately, I can surf the net and work in other apps while Vue is rendering to screen.

heyas; no, the problem is ONLY rendering to disk. you guys rendering to screen are fine. when rendering to disk, vue gets very uptight about where it wants to store and retrieve the image file from. and in what format. if you want to render to disk, you have to tell it to render to disk, and then DONT TOUCH the filename and location it gives the render. nor the format. you can turn on your alphas and depth renderings if you want those. then you have to start rendering, interrupt, and re-save the file -- WITH THE SAME NAME -- to open and resume again later. if you change the scene file name, vue will automatically change the rendered image file name to match, then it won't find that filename (since it started with the previous name) to continue rendering.... and it makes a mess. im rendering 3000x, so rendering to screen isnt even an option. btw, vue 5 d'esprit is trying to save my image thus: F:SVuescenesarabesqueg1.vue.bmp needless to say the stupid 'my pictures' directory isn't on drive f (nor is drive f in 'my pictures'). so as far as i can tell, it's not putting the render anywhere. wabe, if you want to follow up to e-on's follow up on this situation, you might want to give them that info. my 'my documents' btw, points to my d:notes directory.

You can render just fine to the screen at larger resolutions, it will simply shrink down the view of the render to 50% or so, I do it all the time with no problems. Hope this helps as a temporary workaround.

And nobody reads my "it is a reproducable issue that is passed on to the developper team and hopefully will be fixed soon?" Strange!