Here is a report I've just sent to e-on, minus all the memory and other addresses: report 3 As someone reported on the Renderosity forum, if I try to save a picture rendered at preview level in the main view, I get the 'you are rendering at preview level would you like to...' message. If I try to go ahead and save, Vue crashes just like on the import objects problem (four view windows vanish). This is the IPF report: VUE4 caused an invalid page fault in module MSVCRT.DLL at 0177:7800d710. THEN: VUE4 caused an invalid page fault in module MSVCRT.DLL at 0177:7800d32d. Registers: -------------------------- I said I would check on the 'file' button in the vob object browser window. If I click this I get the following crash: VUE4 caused an invalid page fault in module MSVCRT.DLL at 0177:7800d376. Registers: In all of these crashes involving dialogue boxes (save picture, open/import object), the mouse slows down a lot before the crash appearing a few seconds later. ----------------------------- I've hammered the point light and spot light controls, loads of operations and can find no fault. I was going to report the obvious and major bug that when 'no shadows' was selected, point lights still cast shadows, before I remembered that there was a sun in the sky... ------------------------------- in the atmosphere editor, worked for ages with no problem, until I clicked on the 'save atmosphere' button, then I got: VUE4 caused a stack fault in module KERNEL32.DLL at 0177:bff724c1. Registers: ------------------------------- Can't save a vue file either, clicking on save makes it behave just like other file handling dialogue box problems, except this time it didn't crash out completely - the four views and a few other bits vanished, but I could still open new files and existing files - its just that when they had loaded there was nothing there! ---------------------

Thanks for the tip Audity. Unfortunately when I loaded the Vue up again, my scene went back to having no branches. Is beta2 coming real soon now? - n8

Steve, I could - but it is all files - including the samples that came on the 4.04 CD. This is under OS X of course. Btw, sounds like you need more computers :-) - n8

Steve, When do you expect 4.05 to be out of beta?

Here's the Dordogne sample rendered in 4.05 beta 1 under OS X 10.1.2. No branches. Some minor things: - Save picture dialog blanks out the filename when click a folder. So even though Dordogne.jpg was there to start, once I got to the folder I wanted it in, I had to type the filename in. (4.04 too) - Did I mention that it's annoying having to navigate to my user pictures folder all the time? Standard save dialogs provide a way to get to the "home" folder and other favorites. - Would be nice if view settings saved, so I can just leave the othogonal views set to wireframe and not have to reset them on each launch. - n8

Another problem in beta1 for OS X - sometimes the file save menu isn't letting me type! (a filename) Cmd-S to save and cursor sits there blinking, but takes no input. Seems to straighten out eventually though.

Steve, what you got out of my sample file looks great. The problem is that you have done it in Beta 05 and as I told you, I cannot use it, because my Vue AND my computer freezes when I do so. I think I have to wait for the full 05 version. I would like to upload my computer here so you could try by yourself :-) Thanks. Guitta

Steve, some (few) users seems not having a problem with Beta 05, maybe this is due to the OS. I use Windows 98 first edition. Guitta

Steve..if we help with the BUM files...is there any way that we can avoid the 4.05beta or losing all of our current config and program usability? I dont mind helping if all we are working on is the BUM file issue..but Im worried about losing the current setup due to other fixes e-on may be trying to fix at the same time. (I hope that makes sense...it doesnt sound right) but I think u know what I mean.

Ok Steve I have copied the plant files over from my distribution discs. This has not affected the problem at all. (I copied the whole direcotry full of plants, not just the prv files - just realised this) However, after the copy, my vegetation bundle plants have vanished from the plant browser, but not from my HD plant directory. I presume this is a consequence of the copying of the files from the cd plants dierectory., and I won't bother trying to re-install the veg bundle extras unless you need me too until 4.05 is finished.

Steve, 1st, there can be NO discussion of sharing files here that are not publicly available free and freely redistributable, at all. That includes any potential confirmation of having requested and/or received files. You asked my about OS, and I hadn't noticed: Windows 98SE Sacred, make a copy of your Environments folder and put it somewhere else. That's where all your presets are and after copying/pasting the Back folder after patching, put the environments folder you saved back in to the Vue 4 root. I think it only specifically needs the Vue4.env file though.

Nathany: now that is weird... Is there anybody else out there having the same problem on Mac?

Sacred Rose: I would recommend that you create a second installation of Vue 4 on your HD and apply the test versions to that installation. You'd be fine doing it as MikeJ explained, but for greater certainty, it's probably better to have a separate copy of Vue altogether. Just remember to always launch and quit that copy at least once before running the update - to be sure that this is the one being updated.
So... are you game?

Zoon: chances are they will appear next time you launch Vue. If not, you could try deleting the file plants.prv in the Plants folder, and then restarting Vue.

Now, I posted a long note with a render of Guitta's file between messages 53 and 54, but I can't see it any more? Where did it go???

Steve.

Here is the message you posted Steve Site glitch, I suppose... Joerg and Audity: We strive to make updates that work for all languages at the same time, so that nobody feels left aside; but it is true that we have problems with users who have modified the default language of their Vue. It's a problem with the design of Vue, and you'll be pleased to hear that it has been addressed from Vue 4.04 onwards. So this is possibly the last time you have endure it! MikeJ and Zoon: all the crashes are being caused by a missing file for the new selector (4.03 only, it works with 4.04). It will be fixed in beta 2. Re/ the plant .prv files not loading: can you try copying all the files from the Plants folder on the CD back to the same folder on your HD to see if this fixes the problem? Nathany: can we get a copy of the scene that has missing branches? You should expect beta 2 sometime next week. Anybody out there having the BUM file problem and who would care to help us fix it? We can't do that alone, I'm afraid, because it works fine on all our computers. Thanks to all for your great help in sorting this update out. Steve.

I can install a second copy of it on my win98 partition..I have enough room there... It will leave my w2k installation untouched ;] sure Im game. Let me know when u want to start.

Hey Beck just remmember that it will be the most recent location of Vue that has been opened that will get patched when you run the patch...

Oh I might add I had the same experience as Zoon did, but I also made the same mistake of copying it all and not just the .prv files. Will try that again soon.

Thanks Mike..thats why I said I would install a copy on my w98 partition...that way if something goes wrong....i still have a real copy when I boot into w2k :) Thanks for warning me hugs

Hopefully I wont be running this patch? but working on a BUM file patch..... ::: closes eyes and prays:::

A BUM file patch, eh? Now THERE'S wishful thinking. Might as well ask for a perfect LWO import as was implied in the manual ;) Hugs back at ya sweetie... smooooch :)

I am still holding my breath for LWS imports. No reason why they can't modify the existing LWO import to include the scene files. Oh well, I can dream...

Well, the current version will do .lwo OK, as long as it's no more recent than LWO version 5.6, which has alot of limitations, most notably in material/object groupings. But, Vue 4 will not import .lws (LightWave scene files) at all. Funny, but even the "lowly" 3D Exploration can import/export .LWO files as recent as versin 6.0, but still, the 2001 version of Vue 4 can't import the 1999 version of LWO? In spite of the hoopla in the manual regarding LWO import? Hmmmm.....

Ok, I restarted Vue several times, but the plants still don't work. I don't have a file called plants.prv anywhere in my installation (or my backup 4.03 installation) - do you mean vegetation.prv? Let me know and I'll try deleting it if this is the file you mean.

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12368&Form.ShowMessage=542862

Not to change the subject, but I want to make sure you see this, Steve, at the link. Could it be the Poser .BUM thing is tied to a shared .dll?

Zoon: Yes, sorry, that's vegetation.prv...

Sacred Rose: Fantastic! Thanks for stepping forward. We'll try not to cause too much harm to your computer =8o|
I'll contact you directly to work out the details.

Nathany: we've identified the problem with plants on Mac.

Thanks to all of you for your help.

Steve.

Sorry Steve, I deleted this file, and Vue re-created it upon re-start, but the program still reports that it cannot read the prv files.

Yep, same here. I tried it earlier.