#Radiosity
3 messages in this thread
I suppose that if the camera FOV never changed that an .IXP could do the job
(one that does something similar to the "Map to Sphere" effects in
CorelPHOTO-PAINT or PhotoShop etc. with mild settings), or perhaps the current
camera FOV value could be output to the same file that FLARE.IXP uses to track
object bounding boxes so that such an .IXP could adjust for animated FOV
effects. I hadn't thought of that, but it just might work.
I'm hoping, though, that _all_ aspects of 3DSr"5" will be fully opened up to
plug-in programmers. At present, there is no such thing as, for instance, a
.CXP for camera plugins, an .LXP for lighting plugins, .RXP for rendering
engine plugins, etc.
>>RXP for rendering engine plugins
I'm with you on that one!
And hopefully get access to _everything_, so we can get away from just phong
(and metal) calculations (one of the things, IMHO, that I think is keeping
"photorealism" a little bit harder to get than it could be).
I think the brain can detect the similarity in a scene, even when many
variations of a phong surface are being used, that's not enough variation for a
real world view (though I've found masking to help quite a bit, to get a bit
more variety).
– Ron
>>I'm hoping, though, that _all_ aspects of 3DSr"5" will be fully opened up to
plug-in programmers. At present, there is no such thing as, for instance, a
.CXP for camera plugins, an .LXP for lighting plugins, .RXP for rendering
engine plugins, etc.
I would love it: Lights with unique luminence curves and color variations,
cameras that can 'distort' the viewport for special POV and viewing conditions,
renderers implementing alternate styles like contour line drawing with
crosshatching. I would rather plug into one 3D creation environment than
import/export from/to other programs with elaborate compositing schemes and
still not quite get there.
Hoping for the best -Paul