|
From: James W. W. <ja...@fr...> - 2006-07-18 20:35:32
|
Roger Holmes <rog...@mi...> wrote: >For our renderer we had a problem getting the initialisation called >when the Macho module gets loaded by Quesa and have patched >our version of Quesa so it now works. I am not sure whether >checking this in would be a good idea or not, I don't want to break >anything, but if it would be of benefit I am happy to do so. I'd like to hear more about this. I'm using the VRML reader plugin, and as far as I know it's working correctly. >Any other ideas? Either about Quesa and >Intel or ideas about Quesa in general. Do we have a wish >list? Or is that the 'to do' list, and is that up to date? Of course we have the bug and feature-request lists at SourceForge, but not really a simple prioritized list. A couple of wishes I've had more than once: 1. Hardware-accelerated offscreen rendering would be helpful e.g. for high-resolution printing. This could be done by tiling and pbuffer rendering. 2. A new OpenGL-based renderer that would pay less attention to compatibility with QD3D behavior and more attention to maximizing performance. For instance if we let OpenGL handle backface culling, it would be more practical to use vertex buffer objects. -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |