First this occured once or twice (didnt happen at all in the last picture when i used 1.3gigs of ram) and now my file wont open at all without generating it. Wondering if anyone has run into this error and got a fix. At present im backing files of importance off my c drive in preparation for a full reinstall of the system. Seems drastic but ive felt this is install was 'weird' anyways. That being said, has anyone run into this issue and solved it? Ive already reinstalled bryce including deleting the original folders. Added the patch to no effect either.

Well I've had the message a couple of times and most annoying it is when you've just about got something right...but haven't managed to solve it..will keep an eye on this.

I just lost two files in Bryce 5 .. The message I get is that Bryce5 has caused an error in Bryce5.E.X.E. grrrrrrrrrrr .. the first time I had not backed the image up .. the second time I had saved the main structures separate but still will have to spend an hour or so rebuilding .. resetting lights and so on . I do save every 20 minutes or so but this time I had made the first part of the image saved it and was now working on a second part that would merge in .. when I went to open the first file is when I find out it will not open and then Bryce shuts down .. I am going back to Bryce 4 were this never happened and render times were livable .. the few new things in Bryce 5 is not worth the trouble .. I did reinstall Bryce 5 but what a pain .. had to move all my libraries and so on and this did not fix the file .. I also did a defrag and a scan .. no luck :-( .. working with Windows ME.

I'm getting the same error message on files I've put a lot of work into. I've tried copying each object to a new file and still get the GPF on Bryce on the new file. VERY!!! frustrating. I use Windows 98. I don't have Bryce 4 to fall back on either. So if anybody out there can help I for one would be grateful! Reinstalls don't fix the problem and I can't pinpoint any one thing that could cause the problem. Help!

hehe, not 20 mins after i posted that msg, i did the impulse thing and fdisked my c drive. Reinstalling win2k from stratch. Then went to bed after updating the service pack. Will check again after reinstalling bryce after work today. Dont really think it will help but this install of the OS was doing little things that annoyed me so no great loss. Also helps to have 3 harddrive, i keep everything of importance on the drives other then the physical one containing my C drive. If it makes any difference ill let you know. btw, dont blink im my direction strange, may have been only 3 weeks since i fdisked but its far from a record. hehe, ive no problem fdisking again but not until theres a issue.

nope, no effect, same errors when opening file. Guess im back to the one i know to work, though its 3 days older.

So, does this mean I can save some cash and not update to B5? Honestly, other than the tree lab and DOF, I haven't heard any great reasons to upgrade. (Guess that leaves me out of this months contest unless I get really creative with bools...)

Well I will get yelled at by Bryce 5 diehards I am sure ;-) ... but here is how I see it : Bryce 5 has a lot of great ideas and additions .. very few of which are practical.. in my experience anyway .. First off I am on a AMD Processor 1.2 with 512 of ram and Windows ME operating system. The tree lab has possibilities I think but have not dug in too deep so I will reframe from commenting on this feature . Same with the meatballs. (love that name ;-) The new light lab I find has great options .. almost none of which I can apply with out turning a render into a week long marathon .. the soft shadows add so much render time onto my image that as nice as this feature would be it is totally impractical. The new render options? Again great ideas but the additional render times make the new features useless to me. Perhaps a gutsier putter would allow me to use these new features with more ease.. BUT I bought what I could afford at the time (last Aug).. my putter may not be the fastest on the block but I think it is about middle of the road and more or less the equivalent of what most folks have . Add onto this my files corrupting along with the program crashing at the most inopportune moments and I am not a happy camper. Mind you might get a rosier report from someone who had not just lost 3 days worth of work ;-).

Cant say ive ever used the treelab myself. I bought Xfrog for making trees. At $200 for the lite version, its a bargain. Prob is ive not been using it for plants at all, it makes a very nice procedural modeler for abstract models. I will mention that this is the first file to really corrupt for me, other then ones where i messed up and exited while they were still being saved. My concern is that this one im working on is the first in 12 pictures to actually cause real trouble.

The only time i ever saw this was after doing a 50 tree multi-replicate, doing a distribute/size, not liking what i had, deleteing, repeat twice and - viola! The message. I had saved immediately before trying this though so was not too stung. I now, when getting into very large (my def is 65Mb or bigger models) save on a more frequent basis. To date I have not had this happen again. I run a P4 1.8 with 512 Mb RAMBUS using W98SE.

Laurie S Like Incarnadine I have a P4 but am running 2 512 meg sticks of Rambus PC800 My render times are quarter of what they were in Bryce 4 even using soft shadows anf volumetric textures. Unfortunately I happened to get a bad mobo and am currently down till I can decide on a good replacement. It is an Abit TH7 Raid. If Incarnadine has any advice in that department I would appreciate it.

I am using an ASUS P4T, but Abit is a good name from what I hear. No particular leanings but I have never had an ASUS mobo screw up in all my machines incarnations (I have had 6 since I started upgrading my 286 and most have been overclocked by about 1 or 2 steps in speed)

Thanks I have also used asus prev but got a good price on the mobo cpu combo. Hopefully replacing this will solve my problem.