A few things that seem to be NECESSARY for bryce to remain competitive: - plugin capability for those who would like to expand features - updated file import protocols -16 bit grayscale support (import/export) - more robust global lighting tools (skysettings, light diffusion, scattering, etc) - multiple interface presets to fti a wide vartiety of users ("bryce classic," minimalist (only basic controls are on screen), expert (no tools on screen other than crete tools, everything else is controlled by shortcuts and r-click menus), interface clone (mimics the interface of another program), and custom/new interface, where the user can drag and add-delete features. This seems to be included in every 3D app nowadays, regardless of the niche it caters to. - user-defined keyboard shortcuts - scripting (step based, so you tell it what do do first, then second, then third, etc. Could create a cube made up spheres, other boolean shapes and complex primitives, or lighting rigs without having to load them from presets) - entirely new tree/vegetation lab with emphasis on scene integration/naturalism - some sort of ocean tool with animation capability (sure beats my 8x8 grid of 2048 terrains!!!) Some features that would be cool, but are not completely necessary: - some sort of basic modeling tool other than using lattices. Perhaps a pottery tool? - use proposed sound tools to export cubic/spherical QTVR panoramas with directional sound embedded - HDRI lighting support/manipulation (Scene exposure control!!!) - "After the render" effects like simulated DOF, motion blur, and glow that does not need be calculated during the actualy render,t hus saving huge amounts of time. - true to life volumetric atmospherics - imperfections tool to add various defects to materials without spending a lot of time in the DTE - ability in any objects attributes to turn it to "meta," where anything could become a meta-object -a pipe/tube tool - a gear tool I'd really like to see a new set of tools that is unlike anything I;ve ever seen in terms of being involved with the scene. For example, I want to be able to "paint" the path of the water in the river and define where I want pipes to be and connect them interactively. All the ideas above require no R&D and i personally would know what is involved in implementing them.