|
From: James W. <ja...@fr...> - 2007-05-30 23:15:57
|
Jose' Cruanyes wrote: >> It is not intended to work with orthographic cameras. > > in that case, it fails or just is ignored? To tell the truth, I didn't test it. It probably fails. >> One case where it fails is the Windows software renderer. > > So it's not suitable for printing... or there is a way to render on > the GPU for printing? There is an option I recently added to render offscreen contexts using framebuffer objects, when the GPU supports FBOs. See kQ3DrawContextPropertyAcceleratedOffscreen. I have not yet used that on Windows, so I cannot swear it is bug-free. >> Warnings >> >> The algorithm sets the "yon" value of your camera range to >> infinity. To >> prevent surprises, it would be a good idea to set "yon" to infinity >> yourself. While it is true that you get the best depth resolution when >> hither is as large as possible and yon is as small as possible, it is >> much more important to make hither as large as possible. > > doesn't it restore the yon after the loop? so I've to restore it when > switching renderers... one of mine works better with an small range... OK, I just added code to restore yon at the end of the frame. -- James W. Walker, Innoventive Software LLC <http://www.frameforge3d.com/> |