10-14-2018, 07:39 AM
Thanks, once more, Ofnuts.
Yes, I'd noticed the 'single light source only' when I got the function header up on the console lookup.
I wondered if it reran the code for each light source, but I can see a heap of difficulties with that approach.
About the only thing I've found so far that might get done on a bug fix report is changing the documentation to say you can't, in fact, pass a zero if you don't want to specify an environment map (took me a while to figure that one out, being brand new to Python).
Don't you just love legacy code?
Thanks for diving into the source, I really appreciate it. Back in the day, I went straight from backroom coding to front line support with a phone on one ear and the codebase on the screen in front of me, because documentation was non-existent. I've been a firm believer in highly descriptive commenting of code (and good supporting docs) since.
All the best,
thanks again,
QuinB
Yes, I'd noticed the 'single light source only' when I got the function header up on the console lookup.
I wondered if it reran the code for each light source, but I can see a heap of difficulties with that approach.
About the only thing I've found so far that might get done on a bug fix report is changing the documentation to say you can't, in fact, pass a zero if you don't want to specify an environment map (took me a while to figure that one out, being brand new to Python).
Don't you just love legacy code?
Thanks for diving into the source, I really appreciate it. Back in the day, I went straight from backroom coding to front line support with a phone on one ear and the codebase on the screen in front of me, because documentation was non-existent. I've been a firm believer in highly descriptive commenting of code (and good supporting docs) since.
All the best,
thanks again,
QuinB