Well good. However, there is a big difference between the compressed br6 file size on disc and the actual memory footprint when the file is open and running. Bryce 6.1 compresses saved files in a way previous versions did not. The only way to know how much memory is actually being used is to look at the task manager. I usually keep it quickly accessible. You would be surprised likely at just how quickly a few detailed trees can push you to the limit.

There are also crashes caused by using the cut/paste and replicate duplicate commands. This is because Bryce 6.1 has a problem in the memory buffer, which can cause major crashes due to a memory leak.

Best wishes.

Oh and lastly, what kind of system do you run where a simple radio caused the crash? This does not sound like a normal situation. If you are using a computer with multiple processors or even threads, this should not be a problem. The best way to set priority is within Bryce itself, not within the task manager. If you alter the setting in the task manager itself to high you can expect major problems when running other apps. Set priority high in Bryce and leave it normal in the task manager for maximum system stability. I am running a xeon system with 8 cores so I have tested a million different priority settings for the fastest most stable arrangement.