Does this crash Bryce 7.1 pro on your system. I tried it on Bryce 6.something also same prob.

I'm using Win 7 64 pro.

Try this: 1:click on Gold man to create a 2D PICTURE OBJECT Then load a picture and hit the checkmark to apply.

2:Repeat the process but use a different picture.

3:Repeat the process but use a another different picture. CRRRRAAASH Hitting the checkmark crashes my Bryce on both of my Win 7 64 Pro systems. So I cant load 3 different Pictures. Is this a known issue? Is there a work around?

Thanks

Followed your instructions and loaded 6 images one after the other with no problems at all. I use Bryce 7.1 Pro on Windows XP Home 32

I'd suggest the DAZ forum for this. I know there have been issues with the picture editor before. The people over there will also be able to report it if it is a bug.

I wonder what pics you are trying to load.

Quote - I wonder what pics you are trying to load.

Just some random pictures from my desktop.

I tried different pix incase it was something to do with a peticular picture file.

Same results no matter what pictures are used. They were all jpg from differnt sourses.

I went ahead and posted at Daz. I'll try to remember to post here if there's a solution.

Thanks Mysteral for tring on your XP system. glad to hear it does not crash on that.

Thanks all for trying to help and if someone here has a Win 7 pro 64 OS and can try it. let me know if your works or crashes.

Another question along the same lines. In materials editor, I will try to loag a jpg and I sometimes get a 'Generic Failure'. I will go and change the format of the pic, and can get it in. It just seems to happen randomly, it seems like size sometimes doesn't matter, wo, dejavu.

Any ideas?

Nope its a known bug issue for a fact, it was suppose to be resolved but never was. And yes its annoying as hel!

Just wanted to make sure it wan't me, I seem to be a magnet for stupid stuff. Thanks

I have exactly the same problem with Bryce 7.1 Pro I have found you can't import pictures in it without the colour being changed and then it crashes (pity Bryce 7.1 Pro has a Great new features but I have reverted back to 6.3 because the program crashes every 5 minutes.

I suggest you make something with a picture in Bryce 6.3 and then try making it a .obp file then import it to bryce 7 pro. another thing you might want to take into account if mac users get this message when Bryce crashs

Bad Process

KERN ERROR Invalid address

its a lot more said in it than that but what I suggest you do is move everything from the folder you have your work in to another folder and then delete the Old Folder and see if that helps it helped me out a lot.

Karl

Some people have problems when using the image man. try just loading 2d face and use the material editor to load the pic. I don't have thesese problems so I can't check this myself but others who have had the same problems over at the DAZ forum have used this method.

As a work around I was hoping to create the scene in B6.3 since I got finanlly somehow got it to work ok. Then I thought I would be able save the scene and import the scene into B7.1

But as it turns out if I use B 6.3 try the 2d face I can get the 3 pictures in there. But when I try to save the scene file it crashes.

I have not yet tried making 3 .obp files then import those into bryce 7.1 pro.

Dillon Hunt was right. It's never easy:/

Sometimes I think Bryce needs more exterminators than techs, no offense team Bryce.

I agree with you 100% on that mikedaddysmooth don't get me wrong Bryce is the easiest 3d program to learn IMHO and I love it when it works but you do get <censored) when it decides to throw a tantrum and lose a lot of the work you lose. Perticulary if you have worked on it for a long long time.

The trouble is it is a computer program and at the end of the day all computer programs have their flaws and glitchs.

ddaydreams there is one thing you might need to know once the bryce 6.3 file has been saved in Bryce 7. 1 Pro it will no longer work in Bryce 6.3

the invalid address issue in Mac OSX Snowleopard is a daz3d.com.apple.plist problem. Some people on Daz forums say to delete the .plist but I suggest you only do that if you know it won't keep causing these problems because now I can't even find the files the computer keeps babbling about my theory it is that certain bryce file gone corrupted. Another Thing if you ever decide to buy a new mac to put Bryce on wait and see if Mac OSX Mountain Lion has good reviews and is Bryce Compatible Because you can't revert back to snowleopard with a new mac OSX lion because the components rely on that specific operating system.

Thanks

Karl

Quote - ddaydreams there is one thing you might need to know once the bryce 6.3 file has been saved in Bryce 7. 1 Pro it will no longer work in Bryce 6.3

Thanks Karl

Thanks for mentioning that. I had assumed that once a 6.3 has been saved in 7.1 it would not open in 6.3 again unless I save it from 7.1 as a .br6, but I just looked and I and saving as br6 is not a choice in 7.1

Thats ok ddaydreams

its ashame it doesn't save in either .br6 or .br7 I discovered this problem when I wanted to import a version of my analytical engine from bryce 7 to bryce 6 (at that time Bryce 7 was PLE and restricted my work to uncommercial I got bryce 6 from an magazine called 3d world it is a great mag lots of free software with it.) I had to remake the engine in Bryce 6.3.

Cheers

Karl

I crash on the following.

-Every use of the Instance Lab crashes my system within seconds of trying to manipulate the different instances. 

-Use of the spray render about 50% of the time, or at least locking up the program forcing me to close out and re-enter.

-The Tree Lab if I change certain functions.

So, I'm crashing about every 15 minutes or less.

Then again, I have very low ram on my system (256mb).  Was fine for Bryce 5, but Bryce 7 kills it like a plate in a shooting gallery.

So far, I'm very disappointed.  I can't get a single scene done because it crashes before I can save it.

Hi mbouncher

The recommend Ram for Bryce is at least 1 Gigabyte maybe you can add more ram to your motherboard that may make it faster but I can't say if its because of the ram because I had the same amount of problems with it and I have an Mac OSX Snow Leopard running at 3 Gigabytes of ram. I know a diagram for motherboards can help but judging by what you have said your computer is an older generation.

If you suspect it is the ram there may be a way to speed it up you computer.

For Windows

go to start and type in the search msconfig and then click on it and choose start up untick everything except your online security that will speed it up a bit. You can now buy netbooks with 1 gig of ram for about £299.99p or less but you want to go for something thats going to last more than 5 mins so maybe go for a samsung or toshiba netbook.

Sorry I can't really suggest anything more helpful I would stick to Bryce 5 or maybe Bryce 6.3 (if you have it)

Good Luck

Karl

Quote - I crash on the following.

-Every use of the Instance Lab crashes my system within seconds of trying to manipulate the different instances. 

-Use of the spray render about 50% of the time, or at least locking up the program forcing me to close out and re-enter.

-The Tree Lab if I change certain functions.

So, I'm crashing about every 15 minutes or less.

Then again, I have very low ram on my system (256mb).  Was fine for Bryce 5, but Bryce 7 kills it like a plate in a shooting gallery.

So far, I'm very disappointed.  I can't get a single scene done because it crashes before I can save it.

I have made sense of the IL. I was on the committee that helped Daz3D to build Bryce 7, so I've seen how this works under the hood. I will help you out with this if you are still interested.

Admittedly, 256mb is very little ram. It is not surprising you are having some issues. But do not despair. So long as there is sufficient space on your hard drive Bryce will still access 2gb of ram, but it will be very slow because it will write everything above 256mb to the hard drive which recovers memory slower than ram. Still, you should be able to see files much larger than 256mb. There are several reasons why you might be getting crashes. I will explain them and give some ideas to help you out.

Before I get into specifics let me cover some general stuff.

Bryce remains a 32 bit application limiting file sizes to less than 2gb. This can be changed with LAA (Large Address Aware) which will allow usage to go as high as 3.6gb. Further, Bryce still does not have multiprocessor support for any functions other than rendering. All Lab navigation and implementation of modifcations during a session are ported through only a single processor.

When working with lots of instances several problems arise due to the lack of multiprocessor support.

The "virtual" polygons comprising an instance are not as virtual as one might think and must be counted as real in some cases. Back when Bryce was first designed there were only but so many polygons one could cram into a single scenario, now with instancing that number has increased 10000 fold. Therefore, it is natural that scene navigation becomes super slooooooow. It can sometimes take minutes for even simple modifications to be applied to a complex scene, at which point one might think the software has crashed but alas it is still working. It can take half an hour to save a scene that is loaded with instances. Keep all of this in mind so you know the difference between a true crash and a slow working situation.

Always keep the Task Manager open whenever you are running Bryce, this is the only way to avoid crashes due to memory. Files larger than 1.7gb probably will not save properly (unless using LAA) so save before that point. Also, it is important to note that files larger than 1.7gb will not reopen (Again, assuming there is no LAA)

I have found that when instances are first painted the ram usage associated with the new instaces is not fully reported in the Task Manager. If you paint 100mb worth of trees during a session, when you close then reopen the file you will see the memory usage is actually 500mb. If you paint 500mb worth of instances into a scene, it will reopen at nearly 2gb or possibly more, leading to a crash.

I should state that the undo buffer in Bryce is very primitive. The ONLY way to clear the buffer is to close then re-open Bryce. The buffer tries to remember the last 15 modifications. no matter how massive. Creating a layer of instances counts as a single but extremely large modification, thus the memory keeps it stored for 14 susequent modifications in case the user decides to undo it. This grows memory quickly if we delete the layer and go painting another right away. Try to avoid using the undo button whenever possible. Better to close and reopen

Now lets talk about the Instance Lab itself. There are two screens, the Brush Editor and the Painter. One big mistake people make is jumping directly into painting. You must first assign the Brush as the object you plan to paint. Assign rotation, scaling, all of that. After you get your pie chart adjusted, now you can start painting.

In the Painting screen, try NEVER to paint continual strokes, instead use dabs. If you apply continuous strokes you will find the resulting instances will appear to be aligned and not randomly placed no matter how high a randomness setting is used in the IL. To get a nice natural look, you need to use brushes of many various sizes and what not. Dabs not strokes! Strokes also causes us to paint more instances than we intend, leading even faster to an out of memory crash.

Important Note: You can paint along the Normals of the object by pressing ALT while painting. This is how you'd paint onto a sphere for example.

Lastly, when instances are first born they are grouped as Unnamed. This group is linked to the target object. Often the target object will be a terrain. I have found that it is best to ungroup the instances and regroup them once they are born. This is because if you let them remain linked to the terrain, if you make any changes to the terrain geometry it undermines the logic of the attached instances and causes a crash. The vertices of the terrian move around beneath the innocent instances causing confusion within the application. So long as there are no instances linked to the terrain, no problems will arise if you make further changes to the terrain.

Grouped objects do not rotate as they should. There is a workaround but I dont want to overwhelm you with too much today.

Objects high in polygons cost more to instance than objects low in polygons. Imported meshes require more memory than primitives as we all know. So plan ahead, keep in mind the memory usage during the session and the expected usage upon re-opening. Consider how slooooow the wireframe navigation will become when the scene is loaded with virtual polygons. LAstly, almost forgot to add, it is best to use "Show as Box" in the Attributes of your grouped Instances, this will take a lot of strain off the screen updating, speeding up navigation.

Hmm, that was a lot so go ahead and digest what I gave you and let me know if more questions arise. Best of luck. To give you an idea who I am My gallery is located here: http://www.renderosity.com/mod/gallery/browse.php?user_id=496780