 | | Re: automated rendering??? (was "Re: New White Tiger Mecha")
|
|
Lars, Speaking of rendering many files, is there a way you could edit L3P so that the output files wouldn't include color definitions. I like to use my own (well, actually, Anton Raves') colors, so I always have to delete the color definitions from (...) (25 years ago, 7-Mar-00, to lugnet.cad.ray)
|
| |
| | Re: automated rendering??? (was "Re: New White Tiger Mecha")
|
|
Bram Lambrecht wrote... (...) OK. Maybe some sort of "#if not defined(Color0)" (if that's possible) around L3P's colors would suffice. /Lars (25 years ago, 8-Mar-00, to lugnet.cad.ray)
|
| |
| | Re: New White Tiger Mecha")
|
|
(...) That'd be great (seems like L3P files just keeping getting bigger, though :) Lars, have you discussed anything with Lutz about using LGEO? --Bram Bram Lambrecht / o o \ BramL@juno.com ---...---oooo-----(_...o---...--- WWW: (URL) (25 years ago, 8-Mar-00, to lugnet.cad.ray)
|
| |
| | Re: automated rendering??? (was "Re: New White Tiger Mecha")
|
|
(...) Thanks for wrapping the color defs like this -- but how do I take advantage of them? For example, if I were to use Anton's color definitions, how would I tell the L3P output file to do so? Cheers, - jsproat (24 years ago, 17-Aug-00, to lugnet.cad.ray)
|
| |
| | Re: automated rendering??? (was "Re: New White Tiger Mecha")
|
|
(...) I guess I should note that I'm using POVRay v3.1, L3P v1.2 20000616, and Anton's library v415. I'm mainly having trouble wrapping my head around the texture changes from POVRay 3.0 to 3.1 (needs a major version number change, IMO), and how I (...) (24 years ago, 17-Aug-00, to lugnet.cad.ray)
|
