|
From: Jose' C. <cru...@ce...> - 2007-07-02 14:27:15
|
Il giorno 02/lug/07, alle ore 15:42, Roger Holmes ha scritto: > > On 2 Jul, 2007, at 12:23, Jose' Cruanyes wrote: > >> Since Rayshade supports spherical lights, it could be a good addition >> to Quesa >> >> it's just a point lighi with a diameter, and it creates a blurred >> shadow (really nice) >> >> I can derive it from point light (or the other way around, since the >> point light is an especial case of spherical light) >> or create a completely new type >> >> what is better? > > > If it needs an extra data field, your spherical light should inherit > from point light. Can we make it so that renderers which do not > support them see the base class instead, and just give crisper =20 > shadows. I've not still decided, but the better (IMHO) will be to extend the =20 point light, call it spherical, and let access it fron the old API as =20= point light, when the radius data will be ignored the problem will be the metafile I/O, in reading old files there's no =20= problem, the problem is in reading new files with old code... the =20 lights will be lost, since it will be saved as spherical, and the old =20= code expects point lights, unless we don't save the lights with =20 radius 0.0 as point lights... I'll update the Quesa renderers to use it as point light, for the Microspot, you can just add a case label and treat it as =20 point light, > > Hate to curb your enthusiasm for new stuff, but any news on the > caching problem in RayShade? > I've no problem, but probably I'm using it very differently than you please trace RS_UpdateAttributes in the RS_Update.cpp file to see how =20= the specular control value changes Pax et Bonum # Dott. Jos=E9 Cruanyes Aguilar - C.E. Soft srl # Pzza. Firenze,4 MILANO - XX Settembre 10, CREMONA # 02,3923101 0372,460602 |