Check out the attachment, it shows my problem. After installing the 4.05 full update from the 4.03, I start getting frequent invalid page faults involving at least 5 files, and I get this particular error which simply means I CANNOT save rendered pictures. The attachment shows the error ocurring after I selected to save a rendered image. I get as far as the "Save as" dialog box, choosing a name, file type and location, but then goes white and the error pops up. It's happened everytime I have tried using the 4.05 update :( (Not a big deal seeing my pics are so crap anyway *lol*) Anyone else had this? I've sent details to Steve Bell of e-onsoftware but I doubt I'll hear from him for a while. Later JoeBlack BTW: That "What the hell are ya all talkin about?" post is NOT an attack on Vue4, rather that she was questioning why people seemed to write Vue4 off because of one bad magazine review ;)

Attached Link: http://www.hardcopy.de/hardcopy/english/

While waiting for a solution to your problem, get Hardcopy in your language for free. Render to screen, use hardcopy and save your image. :-)Guitta

Thnx but I haven't got a clue how to use it. So I'm guessing no-one else has encountered my problem? Terrific, it must be my pathetic, useless, puny litte computer thats at fault :( JoeBlack, pissed off with software in general

Hardcopy is easy. Click with the left mouse button on its icon, it captures your screen, then rightclick on it and it will open with your screenshoot. Then save your image aftre having cut out exacly your image:-)

Joe, nope haven't heard about anyone else with this problem yet, but there's undoubtably a reason for it happening, and since it began with the 4.05 install and it's only happening in Vue, that narrows it down to Vue being the culprit behind it, not your system. Guitta's suggestion will help you save your rendered images in the meanwhile as this problem is still occuring for you. The screen capture will, of course, only work for "render to screen" images. I'm not sure if it will capture images that are larger than the screen resolution or not. Also, you can use the contents of your Back folder to revert to your 4.03 installation. Give E-on time to respond; they will. And hopefully they'll have a solution for it. :)

Ive had the same problem, but just with no GPF or crash. The program just refuses to save. Sometimes it will, sometimes it won't. I use update 4.02. 4.03 and later was so buggy, I didn't want to try any others. I've found it generally won't save when I've imported Voluptuous Vickie as a Pz3. The reply I got from E-on was less than inspiring: (Paraphrase)- "We're confused. This has never happened before. Don't know what to tell you." I resolve this by doing a screen capture. Not the best, but it does work. MN

Since posting this I have re-downloaded and reinstalled both the "incremental" AND "full" 4.05 update, and both times they created errors. I'm now back to Vue4 4.00.01 from the application CD, and I daren't download/install the 4.03 patch I was using before all this happened. I've subsequently rendered/saved pictures with this without errors. thank god Steve replied the same day, and just told me to try reinstalling the 4.05 patch, but like I said that didn't work. He said it could be a corrupt file, or one that was withdrawn from the site cos it produced problems on some systems. But I saw nothing to suggest that on the Update download page. There were no warnings or notes about the files. BTW: I can't find the "Back" folder anywhere in the "e-onsoftwarevue d'esprit 4" folder, or anywhere on my drive. How do I use the "Back" folder contents to revert to previous patch? JoeBlack

When I installed 4.05 full update I couldn't render at all Vue would quit responding and I would have to ctrl/alt/delete. I went back to 4.03 and all works fine. Marge

Hey Marge, long time no see! Joe, the Back folder (or Backup?) is created when you install a patch. So it should've been present when you were at 4.05, but now that you've returned to 4, there won't be one there. MN, did your interface also turn white as Joe described or did it just refuse to save the rendering?

I too am back to 4.03, and so far everything is ok. I found the backup folder btw lol Maybe I'm stupid but I thought update patches were supposed to sort out bugs..I've told Steve quite a few others, like Marge above, have also had problems with the 4.05 patch. I guess it has a problem with some systems. When are we gonna get software that you can use without thinking about whether or not it's gonna crash or produce the blue screen of death?? JoeBlack

Do you have other sofwares running at the same time ? Maybe an antivirus or something else doesn't like your 4.05 patch ? Yves

I once did ctrl+alt+del and closed everything in the background except Systray and Explorer. It still produced the error. I might try that experiment again tho Thanks JoeBlack

Yesterday, I had a problem with Crossroad software : it caused a protection fault (or something like that). I disabled all the programs in the background, now Crossroad is working ! OK that's not related with Vue 4.05 update, but that's a thing we have to keep in mind. Yves

Yea I know, I didn't really think about that possibility. Sometimes internet software has to be disabled before you use ordinary desktop software. Errors CAN be the result if you don't. However, in this case I didn't disable everything WHILE installing the patch, only after, so I might try that next. Cheers JoeBlack

Varian, No, My interface didn't go white. It just refused to bring up the dialogue box to allow the pic to be saved. It did it again last night after I sucessfully rendered and saved three versions of the same scene (with minor tweaks). MN

When I first installed the 405 patch, I got GP faults when moving the camera around. Updating my video card drivers seemed to help that problem out, but I have had vue crash much more often than it did before (with the 403 patch) It is more reminiscent of the trial version available at e-ons web site, which almost scared me away from purchasing it (it crashed very frequently). My biggest problem seems to involve materials. Does anyone else have weird crashes on certain materials? I also just had it lock up after adding a second terrain. All I had was a single terrain and a water plain. Adding the second terrain locked me out. (these weren't even big, 256x256). Oh well, I just blame MS. They seem to have enough bugs to go around. With the OS being so unstable, it's hard to know when it is software, and when it is the OS. (I can't reliably delete files, thanks to win ME. I gotta do that in linux, unless I want to wait for hours to get them all cleaned up). I would reinstall windows, but I would probably go back to 98 if I did. eric

PS, I would guess the white screen is a repaint issue. Any MS window that is covered up by another window, but is not responding (as would the case be with GP faults) will not get re-painted. That is generally up the software to do, and if it is hung up, it isn't likely to be successful. eric

Eric, true...but Vue shouldn't be hanging when asked to save a render that just finished. Sounds like it's happening too frequently for MN to write it off as an OS issue...but he(?) is using 4.02. Possibly something like that could be cleared up with 4.05, but I'm just taking guesses in the dark here. :/

I do agree with you on that one varian. Actually most of these weird problems are probably bad code at E-on's side, they just don't behave the same on the different platforms. I write software for a living, and it is amazing the things you discover when you move from one platform to another. Just going from NT to 2000 showed all sorts of problems (really weird one's, too) with the program I was hired to work on. They all turned out to be really obvious (if you were looking for them) mistakes, but NT worked in such a manner that they never caused any problems. A recent port from Sun to Linux yeilded very similar results (some of the mistakes that the sun OS let by were astounding) As for Vue, there are tons of layers, different video drivers with various layers of support for Open GL; probably development is done on Windows 2000 machines, so they are not seeing how things react in windows 9x except during a short test period, etc. Just my thoughts, Eric

I think you're probably right, Eric, that the testing on other systems was very brief. Vue 4 was clearly released too soon. Most of it is working well for most users, but when it comes to the odd parts, there doesn't seem to be much rhyme or reason to a lot of them. E-on definitely has their hands full trying to pull this together.